- Show the source (repository) of a real webapp built with Statebus. Citing Linus, "Talk is cheap. Show me the code." Make sure it includes examples of all the advantages cited, like "accessing another site's state".
- Compare your solution with similar alternatives (e.g. my first thought was Meteor).
- Add a public way of asking questions, like a forum or a subreddit. I'm more inclined to ask questions if the responses are public, and it might help you build a body of knowledge to spur the interest of visitors (and even improve your SEO).
As an aside, the svg is not rendering well on my machine (FF 58 on Ubuntu 16.04): http://sufi.andreparames.com/screen_statebus.png
Standards committees spent ages retrofitting measures to prevent this, since it's so easily abused to steal data and logins by wrapping one site in another in various ways.
I think this solves much of the difficulty in building the decentralized web vision described in this article. I'd love to get critique and feedback.
https://stateb.us