Lemmy
It just needs more users and it’s perfect.
Lemmy but with the resources to host video
I’d really like to see some client-API consolidation. A common client API that could efficiently handle both “microblog” style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.
I feel like something like that would need to be discussed at the standards level; a common API spec could maybe be issued as an extension of the current ActivityPub standard. Call it “CommonSocial”, or something.
A wiki with strong moderation tools, and gnupg signed/verified text built into it from the start.
An activitypub method to keep git repos in sync automatically.
A small blog type tool that’s used as a replacement for facebook. It would have a hosted “gathering” component that is always online, then when you open your local app, it pulls down all your stuff.
Shared secrets like a distributed KeePass or Bitwarden.
Distributed home directory and/or development environments.
Something like the useful bits from KeyBase. I really wanted keybase to be something that could support this use case: Alice@foo gets a dev job at Bar. Her ID is added to the cool_project@bar group and automatically she has access to all the group’s
bigbug tracking, file shares, wiki, git repos, group chats, etc. Her joining the group is recorded in a permanent record, which can be publicly or privately annotated by people specifically allowed by the group she joined. It’d become an automatic resume.It exists, it’s Firefish, it has everything I need.
Peertube but not written in JavaScript
