Protocols and Implementations
Autonomous Data is only an architecture. In order to develop Autonomous Data applications, a protocol that supports this architecture must be used. There are basically two things that these protocols need to support: authentication/authorization and data formats.
These are the protocols I have used to develop Autonomous Data applications:
Solid is a protocol based on Semantic Web technologies. It's being defined as a W3C standard and its philosophy and message is very aligned with Autonomous Data. If you want to try an app using this protocol, check out Media Kraken (I made it!).
Kinko is the implementation that I started working on with the incubation of Autonomous Data. Its development is currently paused, but it can serve as a good example of how to embrace the architecture with different technologies.
These are some protocols suggested by the community. Not all of them completely adhere to the Autonomous Data principles (some don't mention authentication, or the data format is lacking semantics). But they are still worth looking into if you're interested in data ownership:
Fission has been mentioned as one of the up and coming protocols, although I haven't used it myself.
Kinto is the per-user storage protocol that was used by Firefox OS and is still used for several Mozilla prducts.
remoteStorage is the per-user storage protocol that came out of the Unhosted project.
Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers in real time, safely protected from prying eyes.
If there is anything else you think should be added to this list, let me know.
Related ideas
Zero Data App is another project very close in vision to Autonomous Data. You will also find a directory of apps that adhere to this paradigm.