Wow! I actually love the idea of being able to interact with websites via a standard API rather being forced to use web-based UI they provide. It opens up a whole lot of possibles for things like alternate clients, standard UIs for interacting across multiple sites, etc. Also eliminates the possibility of sites engaging in annoying or abusive behavior by putting users in full control of the client rather than the sit…
> I actually love the idea of being able to interact with websites via a standard API rather being forced to use web-based UI they provide. For a while, people were pitching this as Web 2.0. It's also what RSS and podcasts still are. Unfortunately, most of the websites we visit are revenue-generating and want to control their presentation.
This project seems designed to work even without the cooperation of the sites you're interacting with; all the site-specific modules are maintained by the community. Adversarial interoperability at its finest.
In extreme cases, one could imagine a module running a full headless browser on the back-end, pretending to be a user scrolling around and clicking stuff, while presenting the actual user with a clean front-end.