It's already open source, and a draft implementation is available on github. (https://github.com/OGC-IoT/ogc-iot-api)

Arguments against the Internet of Things seem to be based on the idea that you'll lose privacy and only big money / governments will reap the rewards from your privacy loss. However, if you look at it from a different perspective, that is, not implementing the Internet of things as household items but as automated sensors for safety and analytics in the workplace, then many of the complaints no longer exist. I think the Internet of things as a buzzword has been stretched top far, but I don't outright oppose adding sensing capabilities and easier information exchange to some machines and devices.

So... I didn't read all of the references in TFA, but this instruction set is written in LISP right? It certainly seems like the only sane language to use to develop something like this.

Then it seems like we don't have too much to worry about in regards to viruses, since few people understand LISP worth a damn. :-) I kid, but I definitely would be interested in knowing more details, since TFA was sparse on its own.

Don't forget, eventually the patricians will become the Eloi and the Plebians the Morlocks, and the Eloi will slowly start to fade out of existance.

This is clearly a driver's ed. student. They're probably some dumb teenager, you can't expect them to expect answers appropriate to the topic or subject matter.
They don't know anything about the world!!!

Sounds like you may want to check out hosting your stuff over a VPS, maybe with Hawkhost (http://www.hawkhost.com/vps-hosting) or some similar provider?

I guess the general idea is that you'd want to install / set up your own OpenStack (cloud) solution, and then scall VPS coverage if you need it, without having to install / clone over multiple machines. Check out Openstack and Java integration. As far as I know there's an SDK available: https://github.com/woorea/openstack-java-sdk, but I'm not sure how complete it is, what features it offers, or even how you would go about setting up your project, considering how vague you were in TFA.

In any case, this may be a good starting point for you to look. Alternatively you could host everything out of your own house on your own servers, but that scales terribly if you need to buy 50 more servers, so I wouldn't recommend it.

I wasn't aware that you could exchange monopoly money for Bitcoins. Apparently I'm going to be super rich really soon.

Is this an incentive or a threat? A bug or a feature? I can never tell anymore.

One would think we might as well just load them all on a ship and send them off to another planet then.

No doubt telling them we'll all be right along after them will ensure they go quietly.

Double dip? I've been burgled 8 times now this past year and not once has a burglar come for a return trip!

I don't know if you were just listing from TFA about the installer candidate, but I noticed you left out "Proper multi arch support" from the list of wheezy features. This is actually a big deal for users interested in Debian, since the ia32libs package was a goddamn monster.

Aside from that, there a few small nuances, such as the mtpfs package disappearing from the repos (try mounting Android on Debian now, sucker!), but the things listed from the article plus multi arch are probably the biggest.

But what if they're triplets? It'll just be the same escalation!

3g/HSPA+/4G sucks more out of your phone than Wifi. Access Point scanning is trivial to your battery life, so if you're always at home or near an access point you can use, you would save battery life by keeping wifi on.

Also, GPS doesn't turn on unless requested by a process (not service). So leaving GPS on all the time does not affect your battery whatsoever, unless you like to open Maps all day with GPS off.

Doesn't know shit about economics. The world is a several billion year old depreciated asset. A simple replacement analysis will show you that the most economic thing to do is use everything for what it's worth and replace it sometime in the next decade.

Seriously, it's like you guys don't want to be part of the 1%.

Correlation != Causation.

Get with it. This is a rookie mistake.

I would take a shot in the dark and say it's a problem of marketing, not feature set.