Idea: if you mod a community on a lemmy.somewhere you should be able to migrate it to lemmy.elsewhere which would include all post & comment links being forwarded and subbed users having their subscription updated to reflect the new location.

I’m aware this would be a way down the road as user account migration alone is still not great but it would be a great feature for the fediverse to have to avoid centralisation and mod/server admin wars.

32 points

But that also makes it incredibly easy for communities on defederated servers to set up shop elsewhere.

And those communities may be the sole reason that the server was defederated in the first place.

I think a possible outcome is that the larger instances would have to put a stop to open creation of new communities, to prevent toxic groups from setting up shop and moving all their objectionable content and users into the space.

permalink
report
reply
3 points

Meh. I think if users focused more on blocking what they don’t want to see instead of defederating, then this wouldn’t be an issue.

This is only a problem if you’re one of the children who thinks: “I don’t want to see something, so neither should anyone else.”

permalink
report
parent
reply
9 points

Yeah exactly, defederation should be limited to instances with incompetent or malicious admins, not with crap communities.

permalink
report
parent
reply
5 points

The feature to allow a user to block a server not just a community should help with that.

permalink
report
parent
reply
4 points

What if an instance were able to block specific communities on other instances without defederating?

permalink
report
parent
reply
7 points

Users can already do so, what would instance-level block bring?

permalink
report
parent
reply
3 points

Allow the admins of the instance to enforce their rules?

Say you have an instance with a “no-NSFW” rule, for people who don’t want to randomly come across NSFW communities. Their admins could take care of the curating of rule-breaking NSFW communities without having to resort to defederating from the entire instance. This doesn’t have to be an outright block but just a filter that could prevent the community to show up in “All”.

permalink
report
parent
reply
19 points

I think it can be solved with a two step process. First, the mods of the community and only them can make a request to move from instance A to instance B, and second, the admins or mods of instance B approve the request, importing only the posts and comments from federated users.

permalink
report
parent
reply
4 points

A good community leaving a bad server can maybe work if the server doesn’t just turn that off.

A bad community that was hosted on a bad server can continue to be blocked on a server level.

A good server tolerating a somewhat bad community will let users continue to block communities.

Two good communities on one server might grow large and want to split servers.

permalink
report
parent
reply
11 points

Let instance admins approve or deny the requests then

permalink
report
parent
reply
39 points

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?

permalink
report
reply
-4 points

🥱

permalink
report
parent
reply
0 points

Bro, this kind of comment is exactly why I left digg back in the day.

permalink
report
parent
reply
25 points

To the first, rollback.

To the second, is that a problem?

permalink
report
parent
reply
8 points
*

To the first, rollback.

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

To the second, is that a problem?

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

permalink
report
parent
reply
11 points

server gets defederated, server moves to new server, defederation bypassed.

permalink
report
reply
3 points

This is part of why it’s better to have users block servers instead of servers block servers.

permalink
report
parent
reply
1 point

That would be a great feature.

permalink
report
reply
89 points
*
Deleted by creator
permalink
report
reply

Fediverse

!fediverse@lemmy.world

Create post

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

Community stats

  • 5.6K

    Monthly active users

  • 1.8K

    Posts

  • 65K

    Comments