874
edits
Changes
origination
== Introduction ==
As per the [http://www.toolness.com/wp/?p=326 first Ubiquity planning meeting], our goals for 0.2 are to:
# make Ubiquity easier for experimental new UIs to leverage, and
# make Ubiquity more secure.
The implementation of (1) will involve providing a well-documented API for external UIs to plug into. The implementation of (2) will involve providing a "feed plugin" mechanism through which new types of Ubiquity feeds can be created that use entirely different security models than Ubiquity's default.
Both of these solutions invite community members to create and implement new ideas to further the conversation about using the browser to connect web services together in a safe, humane way.
Before reading the rest of this document, it may be helpful to understand the [[Labs/Ubiquity/Ubiquity_0.1.3_Architecture|Ubiquity 0.1.3 Architecture]].
== UI Extensibility ==
== Security Extensibility ==
As per the [http://www.toolness.com/wp/?p=326 first Ubiquity planning meeting], our goals for 0.2 are to:
# make Ubiquity easier for experimental new UIs to leverage, and
# make Ubiquity more secure.
The implementation of (1) will involve providing a well-documented API for external UIs to plug into. The implementation of (2) will involve providing a "feed plugin" mechanism through which new types of Ubiquity feeds can be created that use entirely different security models than Ubiquity's default.
Both of these solutions invite community members to create and implement new ideas to further the conversation about using the browser to connect web services together in a safe, humane way.
Before reading the rest of this document, it may be helpful to understand the [[Labs/Ubiquity/Ubiquity_0.1.3_Architecture|Ubiquity 0.1.3 Architecture]].
== UI Extensibility ==
== Security Extensibility ==
