|fredhampton c0a71ef074 Update 'README.md'||3 weeks ago|
|LICENSE||2 months ago|
|README.md||3 weeks ago|
A Libertation Technoloy.
Ida is named in honor of Ida B Wells
Ida is a Decentralized Semantic Protocol that enables: New Decentralized Humanist Technology that fosters and reinforces Community Empowerment.
Modeled after the best parts of Git, BitTorrent, and the Semantic Web, the Ida Protocol is a decentralized protocol for distributing and syncing files and data across distributed Douglass OS networks.
Improving speeds while using less bandwidth sounds impossible. The Ida Protocol makes this the default by using a peer-to-peer network. Seamlessly add or remove nodes as needed.
User security and privacy take priority in the Ida Protocol. Douglass applications using Ida have encrypted transfer, private data sharing, and content verification built-in.
When sharing files, current tools have tradeoffs: lower costs and ease of use, or security and speed. Cloud services, such as Dropbox or GitHub, force users to store data on places outside of their control. Until now, it has been very difficult to avoid centralized servers without major sacrifices. The Ida protocal and Douglass unique distributed network allows users to store data on any Douglass device. By decentralizing storage, Ida also increases speeds by downloading from many Douglass nodes at the same time.
Ida works on the Douglass distributed network unlike cloud services, such as Dropbox or Google Drive. This means Ida transfers files peer to peer, skipping centralized servers. The Ida protocal and the Douglass network makes file transfers faster and more secure.
Ida transfers files over an encrypted connection using state-of-the-art cryptography. Only users with your unique link can access your files. Your ida:// link allows Douglass users to download and re-share your files. To write updates to an ida, users must have the secret key. Ida also verifies the hashes of files on download so no malicious content can be added.
Ida links have some special properties that are helpful to understand.
Traditionally, http links point to a specific server, e.g. douglass.io's server, and/or a specific resource on that server. Unfortunately, links often break or the content changes without notification (this makes it impossible to cite nytimes.com, for example, because the link is meaningless without a reference to what content was there at citation time). Ida links, on the other hand, never change. You can update data in an ida and use the same link to download the changes.
Here is an example ida link:
ida:// - the protocol
The first part of the link is the link protocol, Ida . The protocol describes what "language" the link is in and what type of applications can open it.
5849c7b67b98b08475e99ddec4314d67b28846ef560f2520569001554f9cdfcc - the unique identifier
The second part of the link is a 64-character hex strings (ed25519 public-keys to be precise). Each Ida archive gets a public key link to identify it. With the hex string as a link we can a few things:
Encrypt the data transfer Create a persistent identifier, an ID that never changes, even as file are updated (as opposed to a checksum which is based on the file contents). ida://5849c7b67b98b08475e99ddec4314d67b28846ef560f2520569001554f9cdfcc/
All together, the links can be thought of as new decentrlized web urls, as a place to get content, but with some extra special properties. When you download an ida link:
You do not have to worry about where the files are stored. You can always get the latest files available. You can view the version history or add version numbers to links to get an permanent link to a specific version.
To see the Ida protocal in action you will need to download the Douglass Decentralized Browser