To be honest, your tech, while interesting, is a step or two above the typical Internet of Things device, and the problems that will creep in there. The chips I

To be honest, your tech, while interesting, is a step or two above the typical Internet of Things device, and the problems that will creep in there. The chips I'm working on for my projects that I'd like to have Internet access have at most a luxurious 32 kilobytes of RAM available to them, with some of them having 256 bytes; the closest they're going to get to a kernel is a set of utility functions. The problem isn't the sparsity of space -- explicitly defining variable sizes becomes second nature pretty quickly -- what is is a lack of well-defined, tiny protocols for sending data up and down to the devices. By the time that the device has even gotten to the uPnP stack, it's already been encapsulated and scrambled in some proprietary format because the developers have pretty much no other choice. The part of the stack you're focusing on already has lots of real smart people working on it, we need more people working on the front lines, building good open protocols designed around sharing so that one's sprinkler can talk to one's weather station so that it knows not to run while it's pouring rain, regardless of who makes it. Until we have those, all the TOR in the world isn't going to protect the huge corpus of data that is going to spring forth into the world.