In my thinking about things IndieWeb and user-supported cloud infrastructure, I’ve had a couple of notions bouncing around in my head that might help clarify some “products” I’d like to build if and when I have time. I guess this would be good to blog about, so maybe someone else can steal my ideas (if they’re any good). Because, after all, much of this is sourced from material I’ve stolen from guys like Dave Winer.
The first notion is “areostats on the web” – and by that I mean little servers that you own & run out in the cloud, like communication satellites. They’re positioned on the high ground, in view of lots of clients behind firewalls that can’t see each other.
An aerostat provides rendezvous, repeaters, store-and-forward inboxes, and general all-around persistent resources accessible by mobile and sometimes-online devices.
Aerostats don’t necessarily include web servers intended for general content publishing: Many of these coordination and communication services involve a web server, but in my mind an aerostat isn’t where you stick your blog. It might be the thing that fires off update pings when you post to your blog, though. The blog itself could be hosted on Amazon S3 – because they do paid scalable content hosting very well. (And, just visualize how easy it would be for a mob to pull down an aerostat.)
I don’t really have any aerostats built, yet. I want to, though. I’ve got ideas for many pieces, but have yet to assemble them in a meaningful way.
The second notion is “base stations on the web” – and by that I mean little servers that you own & run at home, like the base station for old-school cordless phones.
A base station could be your NAS or Time Machine, and it’s where your constellation of laptops and mobile devices can sync up when you’re on the couch. If you’re lucky, you have a stable IP on the public net from your ISP and can open a port in your router’s firewall – that way, your devices can get to the base station while you’re out and about.
Base stations include things such as backup services; a Firefox Sync server; a storage API for mobile apps. In my mind, a base station is largely private, maybe shared with a single household or immediate family. A base station isn’t where you host your blog, but it could be the thing that fetches updates from others’ blogs and hosts a news reader.
I have a base station at home, right now. It’s a Synology DS210j NAS, and it comes with much of the above out of the box. I’ve added a Firefox Sync server, though that needs some work on my end. I’m also able to open a port on my router. That’s allowed me to enjoy my own music collection from a 1TB hard drive in my basement, using my smartphone on wifi while at 10,000 feet over Utah. Who needs to upload tracks to Google or Amazon?
(Well, you might, if you don’t want to bother with maintaining a music collection at home – but I like it.)
Now, there’s nothing keeping aerostats or base stations from being things provided entirely in the cloud. In fact, most of these things are available out there right now. But, it’s fairly hard to host these things yourself if you wanted to, and common APIs are lacking.
Some of the cloud services are for-pay and some are for free, but the stability of many are questionable. So, self-hostability and common APIs would at least make it easier (or at least possible) for you to jump off a burning platform if or when the company goes under or a giant like Facebook or Google buys them and the dev team gets retasked.
Really, the point here is that you should be able to pay a vendor to run these services, or you should be able to buy your own hardware and run them yourself. Or, I guess you can subject yourself to ads and behavioral analysis to get a free ride – but, you get what you pay for.
Nerds-only, for now
Another thing to note is that, at least in my mind, the terms aerostat and base station invoke thoughts of amateur radio. That’s on purpose: Like usual, I think the next phase of this stuff is and will be lovable only by the nerds – just like the blogosphere in the last decade. So, I might as well embrace that at first and visualize ham operators on the web.
Maybe this stuff can eventually be productized in a more generally usable way – yet preserves qualities of freedom, privacy, usability, and reliability.