- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Tesseract is a web client for Lemmy that was found to be secretly and arbitrarily blocking users, communities and even entire instances. You can see if you’re one of the kool kidz by running
curl -s https://tesseract.dubvee.org/tesseract/api/system/policy | base64 -d | gunzip > policy.json
and grepping your name / instance. Further details can be found in this post.
The poem above is adapted from Bertolt Brecht’s The Burning of the Books, which can be read here. If you would rather read it in the original German, go here.
Get yar medals here!
For the lucky ones indirectly blocked by Tesseract (instance ban / regex):
For the elite few who pissed them off enough to be banned by full name:
IMO first and second class should be reversed because being banned by regex implies the guy cared enough to make sure he got all your alts.
I don’t think that’s the case. I haven’t made any alts and still am regex blocked.
I know I’m banned but how would I know which one?
The list has been mirrored at https://file.garden/amIRhTctI0qld2r5/policy.json
You aren’t banned by name, only by regex :-(
Ty!
Most of the regex bans are for those with user accounts on multiple instances under the same name. Extreme example: https://lemmy.ml/search?type=Users&q=cm0002
JSON isn’t especially greppable, which is why I often pipe them through gron.
so essentially the only real blocks are the ones in the user list?
Both lists are blocklists, it’s just that one is processed as literal matches and the other as regular expression matches.
Did that user even make the list like on piefed.