Unifying the Fediverse
Why are there so many separate platforms in the Fediverse like Mastodon, Lemmy, PixelFed, and PeerTube? It feels like they could all be part of one unified platform.
Posts
Text, images, and videos could just be treated as posts, all with comments enabled.
- Servers that don’t want to host videos could just have a setting to turn off video uploads.
- That would let PeerTube function like Mastodon when video support isn’t needed.
Lemmy + Mastodon + PixelFed
They all do basically the same thing — let people post stuff. So why split them up?
Forums can still work like Lemmy. If you want your post in a forum, cool. If not, that’s fine too.
Matrix + Posts
- As for messaging, I think Matrix could benefit from Signal-style encryption. Each message should be encrypted with a unique key, just like Signal does.
- Add a button like “See recent posts by this user” on profiles.
- This would make it easier for people to switch over from Instagram or Facebook.
plugin-based development
I also think the Fediverse could grow faster if it were plugin-based, kind of like how Obsidian handles plugins. Development would be more modular and flexible.
- Servers could choose which plugins to enable.
- Devs could collaborate instead of reinventing the wheel across platforms like Mastodon, Lemmy, PixelFed, PeerTube, etc.
- This would create a richer, more customizable ecosystem that evolves together.
Questions
Also, just a question from someone who’s not a coder:
Why not just copy Signal’s encryption model?
Summarize
Each user can create posts (with or without a forum), follow forums, follow other users, have private chats, and join encrypted rooms.
This is just some personal rambling, so feel free to ignore it. But if any of it sounds useful, please share it with other people, especially the developers.
You right on most things. But I still have some question.
Do you think there is a “best” most efficient programming language for building the program?
What I was thinking is to implement the karma system but leave the option of enabling it to servers and users. So this one is on lemmy.
If I’m talking sense, based on my previous opinions, I think adding a “plugin” to lemmy is a better option than building something entire new.
I don’t think it would be a problem if the project is open source?
I think that depends on how important performance is for large instances, which I don’t really know. Python has a huge advantage due to being notoriously easy to get into, even for non-programmers. This means it can find contributors much more easily, leading to faster bugfixing and feature development. But Python is also slow, which might be an issue for large instances that have a lot of work to do.
In general, barrier of entry and performance act as trade-offs to each others. If you use a language with a lower barrier of entry, it tends too come with lower performance, and vice versa. So whether there’s an ideal language depends on whether performance matters and how much it does.