Predictable and self inflicted. You don’t bring Reddit style tactics to a group that largely fled them and not face blowback.
It’s just shocking that they’d create a front end that filters out a bunch of stuff without telling the user. To me, that’s not the job of a front end client program. If they want to add additional filtering over the backend, it needs to be directed by the user or at least specifically approved by the user.
Yes if this had been opt-in. Something that the user had to explicitly enable it. And was thoroughly explained. The worst anyone would have to say about them is that they were overly opinionated. But no one would care beyond that. The reason it’s a big thing. It is the way it was hidden and enabled by default. It 100% is a mess of their own making.
Man this drama ended before I could figure out what it was about lmao
I too am searching for what happened
Reply to me when you find out
tl;dr (also didn’t really see an explanation I’m the linked comments):
Tesseract dev hid a blocklist (compressed + base64 encoded iirc) of users and communities that should never be shown, sneakily inserted in an otherwise irrelevant commit.
There were a lot of communities/people on that list that didn’t make a whole lot of sense, but the main issue is that it was a static list you (as the person hosting the front-end) have to opt out of.
db0 figured this out when he updated tesseract and suddenly no local posts appeared (the db0 instance is on the list).
Actually it was saying our instance was incompatible
