What you call “fragmentation” is perhaps better described as “multiple moderation philosophies applied to the same topic” and is actually a fundamental aspect of the ActivityPub protocol, which was designed above all else to create platforms that resist centralization.

I’m not saying you’re wrong to dislike it, but it is definitionally impossible to have both decentralization and centralization at the same time.

Allowing /c/anti_thing to direct all of their users to posts in /c/thing is a bad idea.

Personally I have never viewed the “separation problem” as a problem, but the single largest benefit of federation/decentralization.

Hi, one of startrek.website’s admins here:

If I’m understanding this “feature” correctly, it feels antithetical to what I view as a fundamental aspect of the fediverse, which is diversity of moderation via decentralization. We came to the fediverse with the explicit purpose of escaping the tyranny of the majority that Reddit forces upon mod teams. This feels like a large step on the path to remaking reddit “with extra steps” and would probably be a deal breaker (for me personally at least).

I think a better way to implement a similar feature, is to give mods an ability to “boost” posts into their communities (with consent from the other mod team to prevent brigading). That maintains the separation while still allowing mods to make exceptions and consolidate comment threads where they deem appropriate.

You know, if Spock were here, he’d say that you were an irrational, illogical human being by taking on a mission like this.

…Sounds like fun!

Let’s just say there’s a reason we moved to the place where defederation is an option…

After all, any instance can pickup some of those and isn’t representative of the instance as a whole.

I think I speak for the whole admin team that we actually do hold instance owners responsible for the communities they host, the same way we hold Reddit (the company) responsible for the communities they choose to host. That said, we made the decision that (for now) the best practice for handling large general purpose instances like .world or .ml is to take a scalpel approach until such a time comes that the Threadiverse is more resilient.

While ostensibly a “general purpose” instance, users on Hexbear had a tendency to come to our hosted communities and aggressively push propaganda, unfairly burdening our mods, so it was a much easier decision to de-federate. We actually did announce that one because of their size.

(Also FYI in case you’re not aware you are posting form lemmy.world so just to be clear none of these policies apply to your current account!)

EDIT: I also think it might be useful to highlight that we never take actions against other instances, we take actions for our users/communities.

Big oof.

How much effort would it be for them to create a new one and do it again?

Minimal, but it is the domain that gets blocked so the attacker would still need to purchase a new domain.

Would you like the admins to permaban them?

Looking into this, btw

It’s been a long road, but this issue is finally resolved.

We’re not opposed to hosting non-Star Trek communities as long as they adhere to instance guidelines, but before you move you should know that the federation gap with .world is closing and should be finally caught up before the end of the week.

Time for startrek.website/c/theymightbegiants?

No worries at all, we want to make sure we’re providing a fast and reliable (well, as fast and reliable as is possible with beta software at least!) experience. Like I said I don’t notice .world missing very much but that doesn’t mean we don’t realize the value their communities provide to the overall ecosystem.

What was the community/post? It’s possible we removed it on our side (Also we are up to 4 days behind now, progress!).

Personally I don’t prefer the .world versions of most communities so I haven’t noticed much difference.

Hey just want to update you on this, we made some changes that appear to be working. We’ve gone from 1.47 weeks behind to 1.42. You can see the recent change here.

Oh, very nice! And yes, the blue was chosen because it matches with the default Lemmy upvote color.

Startrek.website has banned the user and blocked/purged the communities.