1) make unhosted.org a webpage with resources, point to actual applications, and let people get started.
2) as proposed above, yet have a /blog page that's fine, but also syndicate other people's entries. At the moment it seems the "unhosted.org" movement got shanghaied by a person who made it "his blog" ;-) No offence intended.2b) the blog is fine and nice read, but it more seems to be one mans journey to bootstrap his own unhosted adventure than a 2 year project of a community.
3) I see you're maybe using nodejs, show how to install your own remoteStorage server and how to run it, that's the purpose of the whole idea, right? This requires the remotestorage server code to be shared.
4) it's becoming clearer to me now that it seems the application is being seen as different from data, I'm wondering why the applications aren't stored as my data in the remoteStorage? If I get to a new computer, how do I bootstrap my universe to interact with my data and my apps? Is the idea to only run them from the browser url/cache, or local filesystem, or your own running webserver? (or I guess github which btw,then is hosted...,ahum)
5) have some actual apps that shows the concepts, and running example codes instead of code snippets that does nothing.
6) some kind of "app directory" is needed.
7) in the remoteStorage it talks about that your data is copied, replicated etc, but I don't see this really being part of the protocol?
Happy new year!