674
YSK the Tesseract dev made a blacklist of Lemmy users that get filtered from their Frontend
(copyparty.adrian.place)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jul 2026
674 points (98.6% liked)
You Should Know
46837 readers
54 users here now
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason WHY YSK:
In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Rule 11- Posts must actually be true:
Disinformation, trolling, and being misleading will not be tolerated. Repeated or egregious attempts will earn you a ban. This also applies to filing reports: If you continually file false reports YOU WILL BE BANNED! We can see who reports what, and shenanigans will not be tolerated. We are not here to ban people who said something you don't like.
Rule 12- Linking directly to a video as a source is not acceptable.
Video only posts are responsible for an outsized portion of rules violations. Your post must contain text and meet the requirements of the previous rules.
Rule 13- If you file a report, include what specific rule is being violated and how.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!
founded 3 years ago
MODERATORS
It’s really just a custom ui/frontend that admins can run for their lemmy/(piefed too?) instances.
Well, I quickly read through that list and I'll say this: considering the insane amount of stuff that gets silently filtered out, whoever views Lemmy through that thing must think it's pretty quiet 🙂
And that’s a large part of the issue. The frontend doesn’t actually disclose this blocklist at all. In fact, it actively takes steps to obfuscate things and make it appear as if the blocklist doesn’t exist at all.
For example, attempting to view a blocked instance shows a generic network error, rather than a “this instance is being blocked by your frontend” error. And blocked users aren’t simply flagged and/or collapsed. They’re entirely hidden, as if they don’t exist at all. So someone using this as their primary frontend wouldn’t even know that they’re missing entire posts and/or comment chains, because anything from the blocked users is simply gone.
Additionally, the blocklist is downloaded (in plaintext, over http) when the frontend is booted, so it’s not a file that gets updated with the git version updates. Meaning the dev can silently update it even if users haven’t pulled new versions. Simply rebooting your frontend would be enough to pull an updated blocklist. This gives the dev an extreme amount of censorship power, because they can effectively change users’ configs without any action on the users’ part.
It was only originally discovered because the admin for db0 used the frontend. And notably, db0 is on the block list. They were previously using an old version of the frontend that didn’t include the hidden blocklist yet. They updated their Lemmy stack a little while ago, and suddenly their entire frontend was broken (the entire feed was completely empty) and showing a generic version incompatibility error.
After lots of troubleshooting, the db0 admin eventually discovered that the frontend was downloading a hidden blocklist and automatically blocking the instance that it was running on. Because when they updated their stack, the new version of Tesseract included the secret blocklist. So it downloaded the blocklist when it booted up, found that db0 was on the list, and silently hid every single post because they were all from a blocked instance. This resulted in a completely empty feed.
Oh that's mental. I didn't realize it was that bad. Something new to worry about scanning for when using open source!
Considering the amount of effort put into the blocklist by the Tesseract dev to keep it hidden, you would think they would have included an exception if it was running on a blocked instance to help keep it hidden.
Don’t give them ideas, it’ll be harder to find the next one.
I guess the lesson here is “compile from the source repo and code review before you install a new frontend”
Yup, and this is just speculation, but I guess it’s supposed to be an anti-spam thing, but it targets a lot of people/communities/instances that post actually good content
Oh my God, I swear some people will just never get it.
No dude, this isn't just someone trying to block spam, this is ideologically targeted to silently remove specific viewpoints from people who use the stylesheet without disclosing that they're doing that.
This obviously has nothing to do with spam. Keep giving people like this the benefit of the doubt, and see where it leads us.
Edit: I just saw your pfp... Were you aware that this blocked the entirety of Blahaj? The de facto trans instance?
Try justifying that as anti-spam.
Oh, whoa, I did not see that. From what I had seen I could have sworn that it had general political blocking. That’s my bad!
Truth nuke
It’s not anti spam at this point. No one obfuscates something that much for antispam.
It's also a weird place for anti-spam, to have it be client side. That should be done on the server, rather than the various clients handling it.
True! Idk, that part is just speculation, hence why I said I guess, not I know. Either way, they did a shitty job that should be shunned.
I'm on the list and I've never even posted anything. I do comment a decent amount, though, but I wouldn't consider any of it to be spam.
Did you ever talk shit about billionaires or crypto? Make any anti-AI posts?
Yeah, I'm pretty unabashedly anti-capitalist, so I'm not surprised I ruffled some feathers. I was just pointing out that the idea that this was just a spam filter taken too far doesn't really hold up.
I comment exclusively, and I'm on it.
I don’t think it’s anti-spam. It looks pretty much like a personal blocklist, it blocks a lot of users that have political views that the tess dev doesn’t agree with. It blocks political keywords often used by certain ideologies that I guess the dev doesn’t agree with, for example, no ones blocking “neoliberal” as a keyword because of spam.
This looks entirely like a personal blocklist which is completely fine, but secretly adding it to the frontend is v dubious…
It’s a shame I think the dev is a good person from the convos I’ve had with them, but this crosses a bit of a line…