Seven facts about Unhosted

Unhosted is finally the project I’ve been waiting for, that stands a chance of decentralising the web.

Unhosted logoIt separates application writing from hosting your data. Encryption magic means that neither the writer of the application nor the storer of your data can access your data.

This will empower users, create more competition and boost open source web applications.

I’m sufficiently excited about Unhosted that I decided to tweet once a day about it for a week. Here’s what I said:

  • [ @unhosted fact #1/7 ] There’s a busy and technical mailing list e.g. discussion about protocol extensions
  • [ @unhosted fact #2/7 ] early stages, but 4 unhosted apps have been made already – vote for the best
  • [ @unhosted fact #3/7 ] Architecture: browser grabs webapp javascript from X, encrypts data, writes to any store Y (at home), Z (an ISP)…
  • [ @unhosted fact #4/7 ] Used to: buy desktop apps from one company, store data elsewhere – we control. Unhosted brings that to web.
  • [ @unhosted fact #5/7 ] Three unhosted storage node implementations. Bet one makes a packet on the decentralised web.
  • [ @unhosted fact #6/7 ] Browser-based javascript crypto is controverisal – – @unhosted is a reason for it.
  • [ @unhosted fact #7/7 ] Cunningly, unhosted itself is decentralised – a protocol and a cloud of miniprojects.

If you’re not a coder then Unhosted isn’t much use to you yet.

But if you are one, particularly if you’re interested in developing standards (and I think this will be a very important standard), now’s the time to get involved.

Join in on their mailing list. Be the first to write an Unhosted app for auctions, book selling or office documents. Code up that commercial Unhosted node storage service before someone else still agile like Dropbox beats you to it.

Leave a Reply

Your email address will not be published. Required fields are marked *