348
edits
Labs/Weave/Developer: Difference between revisions
no edit summary
No edit summary |
|||
| Line 27: | Line 27: | ||
Mozilla has made a strong effort to provide a user data storage system that protects our users' privacy. The current system does not store any decrypted data about the user on the server, besides the minimal set of data we need to log the user in and contact them if they lose their password. | Mozilla has made a strong effort to provide a user data storage system that protects our users' privacy. The current system does not store any decrypted data about the user on the server, besides the minimal set of data we need to log the user in and contact them if they lose their password. | ||
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. 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). | |||
* What are the platform features you are planning to offer in the future? | |||
Add-on and search engine sync is under development now. | |||
We have a plan to support [[Labs/Weave/Developer/SecureDataSharing|Secure Data Sharing]] that empowers both users and service developers. Your input is welcome! | |||
We are enhancing the Weave Identity service, to be a full-featured OpenID provider and to support profile-exchange and service-discovery features. | |||
* Can I write commercial applications or closed-source software that uses these services? | * Can I write commercial applications or closed-source software that uses these services? | ||
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. | 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. | ||
= Documentation = | = Documentation = | ||