348
edits
No edit summary |
|||
Line 17: | Line 17: | ||
= Services Developer FAQ = | = Services Developer FAQ = | ||
<b>What sort of applications can I build with Mozilla Services?</b> | |||
As an add-on developer, you can use the Weave Identity and Sync services to create a consistent experience for your users. Read about [[Labs/Weave/Developer/HowToWriteSyncAddonPrefs|how to synchronize add-on preferences here.]] | As an add-on developer, you can use the Weave Identity and Sync services to create a consistent experience for your users. Read about [[Labs/Weave/Developer/HowToWriteSyncAddonPrefs|how to synchronize add-on preferences here.]] | ||
Line 23: | Line 23: | ||
As a client software developer, you can use the Weave Identity and Sync services to access users' web experience data to create a consistent user experience between your software and Firefox. Read about [[Labs/Weave/Developer/HowToWriteClient|how to access browser data in client software here]]. | As a client software developer, you can use the Weave Identity and Sync services to access users' web experience data to create a consistent user experience between your software and Firefox. Read about [[Labs/Weave/Developer/HowToWriteClient|how to access browser data in client software here]]. | ||
<b>What sort of applications shouldn't I build with these services?</b> | |||
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. | ||
Line 31: | Line 31: | ||
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 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). | ||
<b>What are the platform features you are planning to offer in the future?</b> | |||
Add-on and search engine sync is under development now. | Add-on and search engine sync is under development now. | ||
Line 39: | Line 39: | ||
We are enhancing the Weave Identity service, to be a full-featured OpenID provider and to support profile-exchange and service-discovery features. | We are enhancing the Weave Identity service, to be a full-featured OpenID provider and to support profile-exchange and service-discovery features. | ||
<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 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. |
edits