The name clash with the CPU architecture[1] is by accident?

[1] - https://en.wikipedia.org/wiki/Mill_CPU_Architecture

i'd only buy them 2nd hand now. Outcry and blog posts don't help with such an attitude. Vote with your money.

You can check the papers on the non-code repo [1] but an update to the whitepaper (4th draft) is in the works.

not sure what you mean by http interface discovery, thou. Each local node opens a readonly http interface (localhost:8080 by default) and a json api interface for cli and webui (localhost:5000 by default). gateway.ipfs.io simply a node that exposes it's readonly http interface.

The binary 'wire' protocol happens on 4000 by default. The discovery of other nodes happens by connecting to a bunch of known/configured nodes to bootstrap and asking them for other nodes.

[1] - https://github.com/jbenet/ipfs

so nobody sees your page because of a feature you're not sure you want to have anyway...?

I started a small package for golang here: https://github.com/cryptix/gohn

I'd like to see some more details/post mortem.. I guess it's some form of cache/index poisoning.

yeah, if your device wasn't supervisioned before it would clean install - i guess but i haven't tried and/or checked otherwise if you can than reapply your backup.

I found a way: you can apply the restriction to a non-supervised device, which simplifies the process. You don't need to re-install or wipe.

Just create a profile with the restrictions, then follow the instructions at: http://support.apple.com/kb/HT5833

(Edit to add: It's actually unclear if the non-pairing restriction gets applied when using this method, it doesn't seem to get listed in the profile details once on the device)

It does not. The Allow pairing with non-Configurator hosts requires that the device be supervised.

very interesting. i wonder if they have access to the gpios already. would love to try to connect it to my logipi fpga board and shell out complex computations to that.