874
edits
Labs/Ubiquity/0.2 Design: UI and Security Extensibility: Difference between revisions
Jump to navigation
Jump to search
Labs/Ubiquity/0.2 Design: UI and Security Extensibility (view source)
Revision as of 22:35, 16 December 2008
, 16 December 2008replaced "limited" w/ "restricted" to tie-in example w/ diagram
(Added more info on feed plugins) |
(replaced "limited" w/ "restricted" to tie-in example w/ diagram) |
||
| Line 74: | Line 74: | ||
Possibilities for Feed Plugins include: | Possibilities for Feed Plugins include: | ||
* Plugins that execute code in a sandbox with a | * Plugins that execute code in a sandbox with a restricted codebase principal and mediate the exchange of data between it and the rest of Firefox to minimize the adverse effects of a malicious feed. See [http://www.toolness.com/wp/?p=356 A Security Model for Ubiquity] for more details. | ||
* Plugins that unify Ubiquity's UI with other pre-existing forms of web extensibility, like Bookmarklets and Greasemonkey scripts. | * Plugins that unify Ubiquity's UI with other pre-existing forms of web extensibility, like Bookmarklets and Greasemonkey scripts. | ||
* It should also be possible for one Feed Plugin to wrap another, creating possibilities for middleware. For instance, a social web-of-trust style model could be layered on top of an object capabilities model, thus providing multiple layers of protection for end-users. | * It should also be possible for one Feed Plugin to wrap another, creating possibilities for middleware. For instance, a social web-of-trust style model could be layered on top of an object capabilities model, thus providing multiple layers of protection for end-users. | ||