autonome

We're all in the crucible of free speech and public safety right now. The content-addressed approach of IPFS means that you can trust that the data you requested has not been tampered with. This is a step towards trust that the web today doesn't have. Regarding content controls - right now we cede those decisions to corporations like Twitter, Facebook and others, which isn't serving the needs of most people. Tools for individuals to control their experience online are key to reducing harassment and abuse. While peer-to-peer networking can help keep data available, node operators are also subject to the laws created in the societies they live in, just like any other method of publishing online.

1. As a node operator you are responsible for content you host under the laws of the country you're operating the node in, the same as running any kind of server.
2. The IPFS protocol itself gives the node operator the control over what content to host or block - already a big difference from participating in networks that individuals do not control when and where they're faced with harmful content. Content moderation right now is decided by corporations. Legislation and good tools for individual control of content are both key to creating spaces online which balance free speech with public safety.

The IPFS blog of course: ipns://blog.ipfs.io/

• Wikipedia: ipns://en.wikipedia-on-ipfs.org/wiki/

• I love finding cool presentation experiments like this art book: ipfs://bafybeidp2vzltxyqdivfuaqcwya2yjklonub2isqdrgqxap3guf4my5esy/Proveloop/SPL01_111.html#p=1

• TiddlyWiki on IPFS! ipns://bluelightav.eth/

• Vault74 is an amazing and beautifully designed collaboration space: ipfs://bafybeic53mvs3qwvyrf77qtfnhntekrk3jgunzgbmv4e7r326bkltin6x4/

• My favorite: ipfs://bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi/

One of the challenges of the dweb thus far is that until now there hasn't a way to easily access content - at least as easy as a modern web browser. So lots of IPFS content is behind or embedded in other systems. Now that native IPFS content is accessible directly in a major browser, I think we're going to see a lot more content and apps publishing to with the web browser as a target, instead of native apps, etc.

With IPFS, data is addressed at the block level, not just at the file level. For example, with bittorrent you have to choose whether to zip up those 10,000 files into one huge torrent, or in smaller groups by category or individually. With IPFS, you can link all those files and share addresses for all or parts in different ways. The swarming network behavior is similar, but in IPFS things like metadata and chunks do not need to be contained in a separate manifest like Bittorrent.

I love containers. I would love to see them in Brave. Extension APIs for containers in Firefox are really what turbo that feature though. Turns into a swiss army knife for browser contexts.