+2

Federated Networks.md

reviewed

··· 9 9 - To set the rules which govern users of their instance. 10 10 - To set the rules which govern who they federate with. 11 11 - It encourages fractal [[governance]] (e.g: communist at family level, liberal at state level, ...) 12 12 + - Users can choose servers based on trust, privacy policies, and community standards, which can enhance security and user control over data. 13 13 + - [The network needs a way to preserve content when a node goes down (probably using content-addressed storage)](https://dustycloud.org/blog/how-decentralized-is-bluesky/).

+5 -3

IPFS.md

reviewed

··· 4 4 - Files are automatically deduplicated. 5 5 - [It chunks, hashes and organizes blobs in a smart way](https://docs.google.com/presentation/d/1Gx8vSqrWZ7X-3SCgITXqQdinZQeXIAA7ITqL25SsPN8/edit#slide=id.g741b4d76cd_0_13). 6 6 - Once something is added, it can't be changed anymore. 7 7 - - IPFS supports versioning using commits. 8 8 - - Keeping files available is a challenge. If the nodes storing a file go down, it'll disappear from the network. Filecoin can help with this adding incentives to the equation. 9 9 - - IPFS makes some nice properties the default. E.g: content addressing. 7 7 + - At the heart of everything, is the concept of content identifiers (CIDs). 8 8 + - A CID isn't just a hash of a file—it's a combination of the hash, metadata about how the content is hashed, details about encoding, and instructions for interpreting the data. 9 9 + - They provide Portability and Openness. 10 10 + - Keeping files available is a challenge. If the nodes storing a file go down, it'll disappear from the network. 11 11 + - Filecoin idea was to help with this adding incentives to the equation. 10 12 11 13 ## [IPLD](https://ipld.io/) 12 14