Labs/Weave/Developer: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
= Mozilla Services: Developer Home =
= Weave Services: Developer Home =


Mozilla Services are server-based, always-on services to enhance Firefox users' experience of the web. Our goal is to enable a consistent user experience of the web, whenever our users use the web, while protecting user privacy and choice.  
Weave Services are server-based, always-on services to enhance Firefox users' experience of the web. Our goal is to enable a consistent user experience of the web, whenever our users use the web, while protecting user privacy and choice.  


Mozilla has launched these services to Firefox users through the [http://mozillalabs.com/weave Weave addon].  We encourage the developer community to write new applications that work with these services to bring better experiences to their users!
Mozilla Labs has launched these services to Firefox users through the [http://mozillalabs.com/weave Weave addon].  We encourage the developer community to write new applications that work with these services to bring better experiences to their users!


Our services are open-source and have open APIs. Developers are welcome to integrate their software with our services, and anyone is welcome to download the source code for the server software and run their own services if they wish.
Our services are open-source and have open APIs. Developers are welcome to integrate their software with our services, and anyone is welcome to download the source code for the server software and run their own services if they wish.
Line 9: Line 9:
= Available Services =
= Available Services =


* The Weave Identity service maintains an account for users that acts as an identifier for the other Mozilla services. [[Labs/Weave/Developer/Identity|Read more about Weave Identity]].
* The Weave Identity service maintains an account for users that acts as an identifier for the other Weave services. [[Labs/Weave/Developer/Identity|Read more about Weave Identity]].


* The Weave Sync service maintains an indexed, encrypted data store that provides server storage for history, passwords, bookmarks, form history, preferences, and tabs exported from a web browser. Add-on developers can use a browser-level API to synchronize add-on data between browser instances. By using the Sync Server API, developers can write client software to access the sync data on any platform. [[Labs/Weave/Developer/Sync|Read more about Weave Sync]].
* The Weave Sync service maintains an indexed, encrypted data store that provides server storage for history, passwords, bookmarks, form history, preferences, and tabs exported from a web browser. Add-on developers can use a browser-level API to synchronize add-on data between browser instances. By using the Sync Server API, developers can write client software to access the sync data on any platform. [[Labs/Weave/Developer/Sync|Read more about Weave Sync]].
Line 31: Line 31:
Developers should not write applications that erode this privacy guarantee lightly. In particular, we believe that the users' password and passphrase, and the cryptographic resources accessed through those values, should never leave their personal computer or device. This means that you shouldn't write a server that stores these values and accesses the user's personal data from another server.
Developers should not write applications that erode this privacy guarantee lightly. In particular, we believe that the users' password and passphrase, and the cryptographic resources accessed through those values, should never leave their personal computer or device. This means that you shouldn't write a server that stores these values and accesses the user's personal data from another server.


Also, the Mozilla Services web services are designed to support a relatively small amount of high-value user data. Users are restricted to a fairly small data quota. Applications should respect this restriction by using the Mozilla Services web services for relatively small amounts of data (in the neighborhood of tens of kilobytes).
Also, the Weave Services web services are designed to support a relatively small amount of high-value user data. Users are restricted to a fairly small data quota. Applications should respect this restriction by using the Mozilla Services web services for relatively small amounts of data (in the neighborhood of tens of kilobytes).


<b>What are the platform features you are planning to offer in the future?</b>
<b>What are the platform features you are planning to offer in the future?</b>
Line 43: Line 43:
<b>Can I write commercial applications or closed-source software that uses these services?</b>
<b>Can I write commercial applications or closed-source software that uses these services?</b>


Yes, you may. You must make certain that your terms of service and privacy policy are compatible with the [http://mozillalabs.com/projects-2/weave10/tos/ Weave Terms of Service] and [http://mozillalabs.com/weave/weave-privacy-policy/ Weave Privacy Policy]. Note that crawling or otherwise attempting to bulk-extract data from the services is explicitly forbidden, as is trading or reselling any of the Mozilla Services.  The terms of service also have some restrictions on trademarks, which mean that you'll need to name your service in a way that respects those restrictions.
Yes, you may. You must make certain that your terms of service and privacy policy are compatible with the [http://mozillalabs.com/projects-2/weave10/tos/ Weave Terms of Service] and [http://mozillalabs.com/weave/weave-privacy-policy/ Weave Privacy Policy]. Note that crawling or otherwise attempting to bulk-extract data from the services is explicitly forbidden, as is trading or reselling any of the Weave Services.  The terms of service also have some restrictions on trademarks, which mean that you'll need to name your service in a way that respects those restrictions.


= Documentation =
= Documentation =
348

edits

Navigation menu