this post was submitted on 04 Jul 2023
72 points (95.0% liked)
Fediverse
28291 readers
1541 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, it would be changing how federation works and I would actually oppose a change that says a "user instance" and "content instance" can't be the same server. It's a perfectly normal architecture though to have a management, worker, and database service use any combination of 1, 2, or 3 servers. This just seems like a decoupling from a monolith into microservices.
I agree with you.
The future is going to be different than one monolithic website and I think ultimately everyone just needs to relax for 6 months or a year and just get a feel for how all of this settles over time.
Part of the federated future is that we are going to lose content from time to time. Maybe someday someone solves that but this is what a link aggregation ecosystem with no central leadership looks like, and that's ok.
yeah I wouldn't be in favour of making that change to the software itself.. I think the features are good the way they are. I'm just thinking in terms of organising services, and the best way to do it - it's lots of servers run by volunteers and the structure is hazy so I think it's good to have these conversations.