This is in regard to Lemmy.world blocking piracy communities from other instances. This post is not about whether you agree with the decision. It's about how the admins informed their users.

A week ago Lemmy.world announced their Discord server. This wasn't very well received (about 25% downvotes, which is rather bad compared to other announcements). The comments on that post were turned off, presumably to avoid backlash.

Before that, announcements about the instance used to be posted to !lemmyworld@lemmy.world. This time, the information was posted on the Discord server instead.

I don't agree with this. Having to use a proprietary platform to participate in an open-source one goes against the very purpose for me, especially when the new solution isn't really an improvement (as before the information about the platform was closer to it).

Edit: Corrected the announcements community name.

Update: Lemmy.world finally released an announcement and promised they would inform about similar actions and gather feedback in advance in future.

you are viewing a single comment's thread
view the rest of the comments

[–] vlad76@lemmy.sdf.org 1 points 1 year ago* (last edited 1 year ago) (1 children)

This is my understanding:

Every instance is like an email server and every account is like an email address. I'm NAME@lemmy.sdf.org and you're NAME@lemmy.world. I think where people (and I used to) get confused is with how Communities play into this. Both of our instances have a "cats" community. And we both can see and post to each others "cats" communities. Our community could have a rule that also allows dogs, and your community could prohibit dogs. So, when you post you have to follow the rules of the community that you're on, and those rules could be influenced by the instance admins themselves. So, kind of like how subreddits operate. So, the instance and the community moderators can control the content that is hosted on their own instance. So, you can have an instance that moderates only what's happening on their own server, and that's it.

Now, if lemmy.world decides to de-federate from lemmy.sdf.org, then as far as you can see, the other "cats" community doesn't exist, I don't exist, I can't communicate with you, and you can't with me. And the only reason you would do this is to make the moderating job easier. If you want, you can disconnect from from every other lemmy instance and then you don't have to worry about outside people coming in and having to also moderate what they say on your forum, but then it changes from being an open forum to just being a "friend group".

Also, I think the problem of "reddit supermods" is repeating. Lemmy.ml and lemmy.world are the two largest instances and at this point if they choose to de-federate from a smaller instance, it can basically kill that instance. And it can also be used to control the narrative. There are a few people making choices for many.

You can block users and communities yourself. Go sort by "All" and start blocking everything you don't want to see again. After a short time your feed will be cleared up.

[–] joe@lemmy.world 1 points 1 year ago (1 children)

I thought we were discussing defederation. You cannot block entire instances on lemmy, that I know of.

Blocking a community does not block the users of the instance. The type of people that would naturally gravitate to, for example, a far right instance of lemmy.

[–] vlad76@lemmy.sdf.org 2 points 1 year ago

I know you can't block an instance as a user. I understand why you would want to. It would make things easier for us and I think it would be a good feature to add on the user side. Or perhaps an "opt in" to a block list that is kept by your instance.

In my opinion, blocking the individual users and instance communities is good enough for now. If a problematic member of another instance starts causing trouble in a community on your instance, then I believe it's the job of the moderators to block them if they're breaking the community rules, and outside of that it's my own job to block individuals I don't like.