"Rally, it is a piece of the old "everyone will have a server" dream. Except, instead of having to define as new protocol for evry service, you just use JSON over http."
The key point isn't HTTP, it's synchronization. Rsync, git, and content-addressable storage in general are going to be the next big thing in the web.
One of the exciting things about the "everyone has a server" idea (http://wiki.debian.org/FreedomBox are working on it) is actually the move away from shitty one-way NATed HTTP and onto IPv6 and a full spectrum of two-way protocols.
The other exciting thing is the wider deployment of encrypted traffic (although that's more the fault of Firesheep), and public-key cryptography (how else are you going to build distributed social apps?).
"much can be made of a publicly available everywhere filesystme."
The key point isn't HTTP, it's synchronization. Rsync, git, and content-addressable storage in general are going to be the next big thing in the web.
One of the exciting things about the "everyone has a server" idea (http://wiki.debian.org/FreedomBox are working on it) is actually the move away from shitty one-way NATed HTTP and onto IPv6 and a full spectrum of two-way protocols.
The other exciting thing is the wider deployment of encrypted traffic (although that's more the fault of Firesheep), and public-key cryptography (how else are you going to build distributed social apps?).
"much can be made of a publicly available everywhere filesystme."
This is what HTTP already does.