Extensions Design

Oddysseus does not and will not support browser extensions. They have a tendancy to clutter the chrome of any browsers that support them.

What Oddysseus is open to is allowing resources online to alter it's behaviour in certain ways without adding any additional chrome. For example these might include search engines, content blockers, and user scripts.

Users would enable these by clicking an icon on the right hand side of the addressbar which would change style to indicate whether it's enabled. RSS and page security info would similarly be placed here. They should later be able to manage these as bookmarks.

After an extension is installed a toast will show to say so, and possibly include a "Purchase" button.

Implementation

OpenSearch already specifies discovery for search engines, and it is trivial to list all user-script/style URIs on the current page.

As for WebKit content blockers, Apple has been relying on their existing distribution channels thus leaving me in the cold. So (taking cues from Better on desirable features) I'd define an RDFa ontology for pages to link to their content blocker offerings along with URI templates for their information on first- and third- party URIs.

Oddysseus will extract rel="payment" links once an extension is installed, and make it prominant.