cross-posted from: https://lemmy.dbzer0.com/post/72685299
I discovered this after upgrading our instance yesterday, which also upgraded all frontends to their latest versions as well. After I did, our Tesseract frontend stopped working and I noticed immediately as it’s been my primary for a while. Initially I thought it was an API version mismatch, but no, it was much worse.
Someone pointed out that the developer of the frontend added an explicit hidden and unmodifiably blacklist which includes any and all instances to the left of Kissinger. There’s a commit which also explains their specious reasoning about our instance specifically, as it seems we’ve been on their shit list for a bit longer than that.
This instance and its admin staff encourages identity politics, groupthink, mob mentality, and extremist solutions to societal problems. Users who advocate violence are not moderated so long as the admins agree with the target. Caution and critical thinking are advised when interacting with this instance or its users.
When you use tesseract to connect to one blacklisted such instance , you just get a message informing you that Tesseract is “incompatible with that instance” which leads one to think of a technical issue, like an API mismatch, rather than the dev being an opinionated coward.
Isn’t it funny how all the software developed by turbolibs, like Piefed and Tesseract, end up with hidden control mechanisms from developers who think they know better than everyone else? That they don’t just think they deserve to tell you what you should think, but they should manipulate you to think it? Isn’t it funny how libs go on about how bad it is to support lemmy due to the ideology of the devs behind it, and yet lemmy has 0 opinions as a software? It does make one think…
Anyway, I forked - it as one does - and disabled the blacklist, but since this is a massively ideologically compromised software, I’ll doubt I’ll keep this frontend up after Lemmy 1.0. I think we’ll bring up mlmym again now that someone’s maintaining it again.
You can see the list, you focused on one shitty instance and ignored countless leftist and trans friendly ones in attempt to discredit the issue.
The fact that it’s on the list debunks your implication that it was an anti-leftist and anti-trans block.
I wasn’t ignoring anything. But you have a history of maliciously mislabelling people as anti-left and anti-trans, so worth pointing out that you’re doing it here too.
Sorry they blocked the maga instance you agree with about everything at all times in addition to the left trans instances you hate.
Huh?
I can’t make you smart enough to comprehend what I wrote.
Oh is that what it is?
It’s a crosspost, I didn’t make the post nor the title.
Make up all the excuses and deflections you want. There is zero reason for Blahaj.zone to be on this list except blatant transphobia.
Having a look, your mod log is pages long of bad faith and trolling. Seeing as you’re a single user instance and defending transphobia right now it’s probably best to just go ahead and not with bother with your nonsense any further.
It is amazing that you offered up a textbook example of what I accused you of right here.
Absolutely nowhere have I defended transphobia. It’s disgusting how often you try to discredit people using that tactic. It totally devalues real criticism of actual transphobia that hurts real people.
And if we’re comparing modlogs, apparently I’m in good company with a racist, violent troll.
You’re accusing them of telling the truth about you.
Am I though?
You’re making excuses for blacklisting trans people and the left.
I disagree. I read this whole comment chain and I think what started as a factual observation morphed into accusations of anti-trans sentiment, and candidly I’m not really sure why.
It’s the only lens they can use to analyse anything, unfortunately.
I’m not though.
Self awareness will help you understanding why you’re in the wrong here
Correction, *would help. You need to actually have it in order for it to help you.
Explain how blocking a single instance means someone is incapable of making a different block for transphobic reasons.
Why? I didn’t make any such claim.
I literally quoted you claiming you had debunked the claim the block was transphobic. All you did was show a MAGA instance had also been blocked. Explain.
An anti-Leftist and anti-trans blocklist would not include a pro-Trump instance.
A blocklist designed for a number of other reasons could.
If the evidence for the claim that it’s an anti-Left, anti-Trans blocklist is to look at the code and ignore the parts that don’t fit that narrative, we can safely dismiss that claim.
You don’t have to be a pedant. You can have all of a set inside another set. The title can clearly be read to mean that and the post seems pretty clear to me.
Sure, but just because you can doesn’t mean you do, and it makes the strong positive claim extremely flimsy.
Sure, but just because you can only have a blocklist of only leftist sites doesn’t mean that makes any sense at all
I see zero justification in the git commit for the addition of blahaj, and you have failed to offer any explanation other than ‘not transphobia’ on the basis that a MAGA instance is also on the list.
So? You not knowing the reason doesn’t make it anti-Left or anti-Trans.
Right, because I’m not out here making strong positive claims about the devs motivations. I’m specifically criticizing those who are.
Specifically Mia, who baselessly accused Rimu of this same thing fairly recently.
You’re only defending it because you know it’s both.
It’s so interesting that until someone writes ‘I’m doing this because I’m a transphobe’ in the commit file, then it’s wrong to suggest it was transphobic. Not at all suspect to silently hide the largest trans instance with zero comment! I’m sure it’s a secret, very good reason that isn’t transphobia that they just won’t reveal for some reason!