Distributed Web vs IndieWeb was a session at IndieWebCamp Berlin 2019.
Notes archived from: https://etherpad.indieweb.org/dweb
IndieWebCamp Berlin 2019
Session: Distributed Web vs IndieWeb
When: 2019-05-04 13:40
- Add yourself here… (see this for more details)
- Beaker Browser Beaker
- Hash Base
- Share a file secretly with Dat with Beaker Browser website
- dat://fritter.hashbase.io Fritter - A peer-to-peer social feed app. (proof of concept)
- Fritter GitHub Repoi
SSB Secure Scuttlebutt
- https://www.scuttlebutt.nz/applications (Patchwork and more...!)]
- https://www.manyver.se/ Manyvers For Android]
- identity is tied to a key with stuff
- An example of starting with web
There is interactivity
- Dat Shopping List
You can also do chat, entirely serverless! https://cabal-club.github.io/
- We can publish okay, but we still end up relying on twitter for reading content, because RSS was effectively killed off
- Indieweb is essentially based on governance at the DNS level then?
Difference Between DAT and DNS Approaches
- One of the motivations behind the distributed web is security: having your identity tied to a key instead of the DNS system or an account on someone else's server.
- Some of the people building these alternative tools to the internet, seem to assume it won't be there in 20 years. However, notice that a lot of people are in it, in very remote regions.
- The indie web is built on top of existing technology. dat:// websites need a specific app to access, and other distributed solutions have the same condition.
Tor is an even lower level transport, like ssb for sample - you can run an indie web site without a domain name.
So like the web, things like Dat were designed for academic sharing, so governance - does the same thing of a
-> webby, and tied to DNS