Well yeah, people are changing frontends and warned others that Tesseract has that kind of blocklist and they don’t support it. If people that used the tool didn’t find out until now, it’s mostly a communication issue from the dev. And to the user that knows none the wiser, opinions that they would’ve accessed if not for using Tesseract are essentialy not available. The option to turn it off is essentially hidden, and the user can’t find out that information is being blocked (as seen by the reaction it caused in the threadiverse). It’s censorship by omission of information. Even if they had good intentions, the way they went about it failed to communicate what the blocklist was about, and that information was being blocked in the first place.
It’s also just kind of a silly thing to implement in a client. That’s the perspective the memes are coming from. Usually, blocklists should be left to the instance administrators or users. The client should only easily allow such a list to be available.
I don’t really know if I was blocked nor do I really care. I’m just explaning why people were upset/making memes about it. It’s shocking once one finds out about the blocklist, but kind of funny in retrospect.
That’s not the issue. Admins running the UI and other users didn’t know this was in it.
truly impressive how some people are always the victim even on open platforms they literally can own for free
Well yeah, people are changing frontends and warned others that Tesseract has that kind of blocklist and they don’t support it. If people that used the tool didn’t find out until now, it’s mostly a communication issue from the dev. And to the user that knows none the wiser, opinions that they would’ve accessed if not for using Tesseract are essentialy not available. The option to turn it off is essentially hidden, and the user can’t find out that information is being blocked (as seen by the reaction it caused in the threadiverse). It’s censorship by omission of information. Even if they had good intentions, the way they went about it failed to communicate what the blocklist was about, and that information was being blocked in the first place.
It’s also just kind of a silly thing to implement in a client. That’s the perspective the memes are coming from. Usually, blocklists should be left to the instance administrators or users. The client should only easily allow such a list to be available.
I’m sorry you were blocked but this behavior isn’t likely to change that
I don’t really know if I was blocked nor do I really care. I’m just explaning why people were upset/making memes about it. It’s shocking once one finds out about the blocklist, but kind of funny in retrospect.
it does not shock me at all that someone would make an effort to fix lemmys biggest problem
Yeah, if only someone could make a hidden block list so people like you can’t interact with anyone. :(
uhhhh you’re literally allowed to do that lmao
I think we all appreciate @db0@lemmy.dbzer0.com effort to address administrative and developer abuse, lemmy’s biggest problem.
lol
literally 1984 i literally cant even omg