this post was submitted on 15 Jul 2023
528 points (97.1% liked)
Fediverse
28518 readers
400 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Risky. Some hacker exploits a vulnerability, takes over the community and migrates it to some other server.... then what?
Also, if a community leaves a specific server, what stops anyone else from re-creating it in the original server?
To the first, rollback.
To the second, is that a problem?
for the first, you still have everyone subbed to the newly created community made by the attacker and all the links are still updated
if instead of migrating everything right away, you have the original server of the community give redirects for each request, then that won't help if the original server is closing down, but it's probably the only right way to do it, I guess you could also have an angry instance admin disable the redirect to keep the community on their own server
migrating and then recreating the original is actually an issue that Github has when you rename a repo, Github will give redirects for the links to the old name of the repo, but if you create another repo with the old name then the redirects are no longer served and if someone clicks on an old link then they end up at the repo that stole the name instead of the repo that was renamed
so if let's say there was an official linus_tech_tips community on beehaw and they moved to lemmy.world, some random person could create the community again on beehaw after the migration to appear official and hijack all the old links out on the internet
you fix that by keeping the old name reserved after migration, I don't really think that's a big problem in this case
I actually liked @Neato@kbin.social's idea, instead of "migrating", you just copy the community and then send a message to every subscriber, close the original community, and put a pinned post at the top, maybe a message in the sidebar too
🥱
Bro, this kind of comment is exactly why I left digg back in the day.