348
edits
| 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 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 | 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 Weave 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> | ||
edits