- cross-posted to:
- fediverse@lemmy.ml
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.ml
- fediverse@lemmy.world
cross-posted from: https://programming.dev/post/8955176
I made a blog post on my biggest issue in Lemmy and the proposed solutions for it. Any thoughts on this would be appreciated.
I think a variation on the multi community might be a good idea but implemented differently.
Community’s could opt into a meta community (somethings that are the same name arn’t the same thing).
Then on the user client side when you subscribe you can choose to subscribe to the meta community. When your feed is constructed it doesn’t include degenerated etc. when you post it is via your instance to the meta community and a shortcut is posted to all the meta community members, and replies go to your meta post in your instance.
You people just need accept the fact, that it is not “THE xyz community on Lemmy” but just “one of the xyz communities using Lemmy”.
moves to Lemmy to avoid centralization
Y NO CENTRALIZATION?!
But it’s still kinda centralized. If the instance hosting your community goes down, you won’t get comments and posts from users from other instances, so the community dies.
Yeah, one instance going down doesn’t kill the entire network, but it mostly kills the community.