Setup an ActivityPub server to be used by the teams and people within the Protocol Labs Network. Add support for IPFS to the codebase, initially for media files, and then potentially have every post be statically stored on IPFS.
Who would want to use this and why?
The members of the PLN can have a local timeline and one stop shop for updated news, info, and fun across the PLN.
It can also be used for team updates, to run bots for various services and systems, and serve as a backbone of news and information across the PLN.
This should get split out into Wiki pages about these servers.
- Mastodon: Rails; largest codebase in use
- Pixelfed: PHP; focused on images / Instagram clone
- Pleroma: Elixir & PostgreSQL
- MissKey: NodeJS; has a media drive concept built in
Full list of ActivityPub servers: https://fediverse.party/
Pleroma / ActivityPub FAQ: The Big Pleroma and Fediverse FAQ Part 1 - Beginner Questions
Pleroma GitLab: Pleroma / pleroma · GitLab
Pleroma Clients: Pleroma / pleroma · GitLab
Add support for all media to be posted to IPFS. When posting an image / video / file, it is published to IPFS with Web3Storage and persisted to Filecoin, and links point to a configurable gateway.
This feature would also be contributed as a patch to the codebase so others could run this on their server.
This could in general be a larger initiative— perhaps to the FFDweb — to add IPFS support to multiple codebases.
There are varying levels of posting privacy. Ideally we would add encryption to direct messages so that instance admins can’t read it.
On an opt in basis, make it so that users can have the entire content of each message be posted to IPFS.