Blocking on Lemmy is really just muting, and it should be called that.
A real blocking feature would be nice (it exists on other fediverse platforms).
The devs have said that blocking wouldn’t do anything because everything is public, so the blocked user could still access the content they are blocked from but frankly that’s bs. If that were true, then there would be no point of banning either, right?
Devs want a monopoly on the power to block people they don’t like through the use of bans (and they claim to be all for the people).
Ehh. I don’t think that the underlying goal was to try to obtain some sort of “ban monopoly” on the Threadiverse. If they had, they had a ton of things that they could have done that they didn’t.
Don’t support federation in the first place.
Have lemmy.ml and friends simply disallow federation with other instances.
Break compatibility in new builds to make it harder for people to run other instances. Don’t open-source Lemmy in the first place.
Like, I think that it’s pretty lame that some of the official Lemmy software support stuff is communities on lemmy.ml, which has an admin situation that I don’t really like. But…that seems like an awfully weak lever to be pulling if someone’s goal is to try to exclude anyone else from having the ability to restrict users.
I’m more expressing frustration that they have been approached multiple times about fixing the broken blocking by either renaming it muting (what it actually is), or creating an actual blocking feature. The excuses they provide are nonsensical.
Blocking protects users. Why would a federated platform not want to protect users?
I’ve got a top-level comment about why I’d rather not have a feature of the form OP requested. Reddit’s block feature originally worked the way the Threadiverse’s block feature presently does. It was later changed, and that change introduced problems.
However, that being said, I do think that there may be a real UI issue if people think that they’re preventing responses, but aren’t actually doing so, and get frustrated. That’d be a legit UI issue.
considers
I don’t think I’d use “mute”. In IRC, “mute” refers to a moderation action more analogous to what OP wants. I think that that could still produce confusion.
Usenet uses “kill”, for “killfile”, in the sense of “automatically killing posts from a user”. Probably not a great choice either.
Maybe “ignore” would be better than “block”, though. I think that that would make it unambiguous what the operation is doing. I’m guessing that the Lemmy devs just chose “block” because Reddit happened to use it, didn’t put a whole lot of thought into it.
Related story: I once worked with a guy who had worked on Yahoo Maps, way back when. It was one of the first mapping services to provide navigation instructions. He told me that he was the one who had, at some point, suggested “bear” as a verb for the navigation decisions (e.g. “bear right”). It was a pretty off-the-cuff decision, but apparently it’s confusing to some people, since “bear” isn’t a terribly-commonly-used term and can potentially be confused with the animal of the same name. IIRC, Yahoo Maps ultimately changed it, years later, but I understand that not only did they use the term for quite some years, but some other services also copied it, so it had considerable inertia.
Blocking on Lemmy is really just muting, and it should be called that.
A real blocking feature would be nice (it exists on other fediverse platforms).
The devs have said that blocking wouldn’t do anything because everything is public, so the blocked user could still access the content they are blocked from but frankly that’s bs. If that were true, then there would be no point of banning either, right?
Devs want a monopoly on the power to block people they don’t like through the use of bans (and they claim to be all for the people).
Admins can ban on a per instance basis. Moderators can ban on a per community basis. But devs don’t have any particular banning power.
Well, the devs are also the major community moderators and admins on the ml instance, which was the largest for a long time.
They still treat it like their private walled garden.
I may be overreaching with my assumption about their motivations, but then again I may not.
Ehh. I don’t think that the underlying goal was to try to obtain some sort of “ban monopoly” on the Threadiverse. If they had, they had a ton of things that they could have done that they didn’t.
Don’t support federation in the first place.
Have lemmy.ml and friends simply disallow federation with other instances.
Break compatibility in new builds to make it harder for people to run other instances. Don’t open-source Lemmy in the first place.
Like, I think that it’s pretty lame that some of the official Lemmy software support stuff is communities on lemmy.ml, which has an admin situation that I don’t really like. But…that seems like an awfully weak lever to be pulling if someone’s goal is to try to exclude anyone else from having the ability to restrict users.
I’m more expressing frustration that they have been approached multiple times about fixing the broken blocking by either renaming it muting (what it actually is), or creating an actual blocking feature. The excuses they provide are nonsensical.
Blocking protects users. Why would a federated platform not want to protect users?
I’ve got a top-level comment about why I’d rather not have a feature of the form OP requested. Reddit’s block feature originally worked the way the Threadiverse’s block feature presently does. It was later changed, and that change introduced problems.
However, that being said, I do think that there may be a real UI issue if people think that they’re preventing responses, but aren’t actually doing so, and get frustrated. That’d be a legit UI issue.
considers
I don’t think I’d use “mute”. In IRC, “mute” refers to a moderation action more analogous to what OP wants. I think that that could still produce confusion.
Usenet uses “kill”, for “killfile”, in the sense of “automatically killing posts from a user”. Probably not a great choice either.
Maybe “ignore” would be better than “block”, though. I think that that would make it unambiguous what the operation is doing. I’m guessing that the Lemmy devs just chose “block” because Reddit happened to use it, didn’t put a whole lot of thought into it.
Related story: I once worked with a guy who had worked on Yahoo Maps, way back when. It was one of the first mapping services to provide navigation instructions. He told me that he was the one who had, at some point, suggested “bear” as a verb for the navigation decisions (e.g. “bear right”). It was a pretty off-the-cuff decision, but apparently it’s confusing to some people, since “bear” isn’t a terribly-commonly-used term and can potentially be confused with the animal of the same name. IIRC, Yahoo Maps ultimately changed it, years later, but I understand that not only did they use the term for quite some years, but some other services also copied it, so it had considerable inertia.
kagis
https://www.dailydot.com/unclick/kid-gps-instructions-bear-right/