Right! Except regardless of your wishes, “they” don’t seem to want for us to have that ability to block “them”. For a LONG time Lemmings begged, pleaded, and cajoled for the ability to make blocklists. The answer, as I see in the historical archives (hehe just older posts I mean:-), was always “just wait - we’ll implement this in 0.19”. Fast-forward to when that happened: it barely does anything at all.
A block of a “user”/account is iirc as full as it gets - I am not even certain that they can downvote you after that. A block of a “community” is likewise solid - those posts will not only not show up in your Subscribed feed, but even from your All one. However, a block of an “instance” merely blocks the communities from that instance, but the users themselves are still free to troll in other communities, free to reply to and ping you thus generating notifications, free to downvote you, and otherwise carry on almost as if you had done nothing at all wrt that particular instance. It is extremely weak.
Also I’m skipping over the details here but what little it used to do is steadily being rolled back so that it is even less effective than it was before (irt the generation of notifications). And since the developers of the Lemmy sourcecode are also the admins of Lemmy.ml, despite all the pitiable outcry from the users affected - there was one here just this week where an admin literally told someone to kill themselves, over a silly misunderstanding of something that happened inside of a video game - absolutely none of the largest instances will condone defederation from lemmy.ml.
And I get it: we are running their software. Abuse or no, we are the guests, and they are the masters of this Lemmy project. Yes it may be open-source, but if we want their future code releases, the boat cannot be rocked too awfully hard.
So, you can either block every user from that instance that you ever see, one by one, or… suck it up and take what “they” offer to you. Or find another solution.
But notably, I don’t want to just block users b/c of the moderation practices of the admins - it’s the users themselves that, trained within that echo chamber as to what they can get away with, troll people all across the entire Fediverse (unless they specifically defederate from that instance). From another comment I made elsewhere:
so e.g. I get to see Cowbee responding to people discussing tankie behavior with the “just trust me bro, no I refuse to share my references instead why don’t you hit me up in my DMs, hey why don’t you share YOUR references hrm, no I’ve never asked anyone to hit me up in my DMs in my life bro whutyoutalkinabout?”. As funny as it may be to watch, it does disturb me that “normies” as we are talking about in this post will be exposed to such, and have to learn first-hand what types of behaviors to expect from which servers that the admins of most instances will not defederate from.
Right! Except regardless of your wishes, “they” don’t seem to want for us to have that ability to block “them”. For a LONG time Lemmings begged, pleaded, and cajoled for the ability to make blocklists. The answer, as I see in the historical archives (hehe just older posts I mean:-), was always “just wait - we’ll implement this in 0.19”. Fast-forward to when that happened: it barely does anything at all.
A block of a “user”/account is iirc as full as it gets - I am not even certain that they can downvote you after that. A block of a “community” is likewise solid - those posts will not only not show up in your Subscribed feed, but even from your All one. However, a block of an “instance” merely blocks the communities from that instance, but the users themselves are still free to troll in other communities, free to reply to and ping you thus generating notifications, free to downvote you, and otherwise carry on almost as if you had done nothing at all wrt that particular instance. It is extremely weak.
Also I’m skipping over the details here but what little it used to do is steadily being rolled back so that it is even less effective than it was before (irt the generation of notifications). And since the developers of the Lemmy sourcecode are also the admins of Lemmy.ml, despite all the pitiable outcry from the users affected - there was one here just this week where an admin literally told someone to kill themselves, over a silly misunderstanding of something that happened inside of a video game - absolutely none of the largest instances will condone defederation from lemmy.ml.
And I get it: we are running their software. Abuse or no, we are the guests, and they are the masters of this Lemmy project. Yes it may be open-source, but if we want their future code releases, the boat cannot be rocked too awfully hard.
So, you can either block every user from that instance that you ever see, one by one, or… suck it up and take what “they” offer to you. Or find another solution.
But notably, I don’t want to just block users b/c of the moderation practices of the admins - it’s the users themselves that, trained within that echo chamber as to what they can get away with, troll people all across the entire Fediverse (unless they specifically defederate from that instance). From another comment I made elsewhere: