this post was submitted on 14 Jul 2025
27 points (96.6% liked)
Fedigrow
363 readers
3 users here now
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- !fedibridge@lemmy.dbzer0.com to organize overall fediverse growth
- !reddit@lemmy.world to keep tabs on where new users might come from :)
- !newcommunities@lemmy.world
- !communitypromo@lemmy.ca
- https://lemvotes.org/
Megathreads:
- How (and when) to consolidate communities? (A guide)
- Where to request inactive or unmoderated communities? (A list)
Rules:
- Be respectful
- No bigotry
founded 1 month ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The primary problem here is community mobility. If any community could be, with a few key presses, decoupled from an instance and essentially plopped onto another maintaining all of the posts, comments and subscribers - it wouldn't matter as much at all. Piefed has community migration, and I assume that is ultimately the end-goal. It just needs all the major instances to read and recognise such moves.
For all the whining Element gets when it comes to being buggy, etc. The matrix protocol has solved the room moving part very well. Any alias of the room has the same validity to be the main room because the content is being stored on all the servers where people joined the room and the room name is just that an alias and you can have many of them pointing to the same room.
I understand it's more difficult to do with the ActivityPub protocol, but something like that would solve this problem once and for all.
piefeed migration doesn't save the old non-federated content, and doesn't take over the old community name. It's more like a community clone tool. But yeah, its a good start.
Yeah, it's not where it should be. But I'm quite confident that such is the end-goal.
Instances will always come and go in many cases.