i strongly agree with these points.
let me add some more:
- decouple documents from the transport layer: many web vulnerabilities and complexity are due to the strong connection between http and html
- decouple documents from styling: every document should be legible with any stylsheet (bring back 'userstyle'), cut back css features which lead to nasty things like keylogging via css, transparenting elements for clickjacking, hide text to manipulate clipboard, etc.
> gemini, Urbit, IPFS
There could be a distributed blogging/wiki platform where the articles are all written in Gemini markup (or maybe Markdown) and hosted over IPFS.
Commenting on posts is something that Gemini enthusiasts are still figuring out. Currently people post Re: posts to their own gemlogs and then mail a link to the person who made the original post, but I think they are hoping to have a less effortful convention.
- Decoupling of data (articles, videos, ...) from platforms.
- Decoupling authorship claims from platforms
- Decoupling online identities from platforms.
- Decoupling of user networks from platforms.
- Distributed archiving, some years ago if you had an article/manifesto or whatever on Napster or any other P2P system it was trivial to find it again anytime you wanted, now dead blogs, videos disappearing from Youtube, or broken links to Twitter are the norm. You have to archive stuff yourself or hope somebody did it.
- Related to decoupling user networks from platforms, it would be nice to decouple comment sections from platforms and from the articles themselves too. People could comment the same article in different curated comment sections with different moderation policies using their own decoupled online identity.
- Create decentralized networked chains of trust (could help revitalize some scientific communities too).
Seems like very interesting things going on with projects like gemini, Urbit, IPFS, still on the early stages and only usable by power-users, but hopefully they will keep growing.