In light of the dev silently blacklisting blahaj.zone, many of its users and several other instances, we have removed tesseract from the available lemmy front ends we offer.

top 50 comments

sorted by: hot top controversial new old

Still linked to in instance sidebar. Please remove

  • source
  • [–] 142 points 2 months ago (10 children)

    This controversy over tesseract finally got me to do a bit more reading to understand how federation actually works and what a frontend does. Now I understand why everyone is so pissed.

    The email metaphor has been the most useful to me in understanding how this works. Someone tell me if I've got this right. Basically, you have your lemmy account, which belongs to the instance you created it on, like how a gmail account belongs to Google. You can use whatever frontend you like to view your feed, just like you could use Outlook to view your Gmail account. Tesseract is a frontend, kinda like Outlook in the metaphor. In theory, a frontend should deliver to you everything that would appear on your lemmy instance no matter where you access it from, but now the tesseract frontend is basically making content filtering decisions about what users, topics, and instances you have access to. It would be like if your Outlook app suddenly decided "ew, you shouldn't be using your Gmail to talk to any of those yahoo mail people, and also it's now forbidden to use Outlook to discuss seahorses."

    So all the posts, users, and instances are still there, it's just that the dev of your frontend decided that you shouldn't interact with those users or discuss those topics anymore. Worse still, they surreptitiously tried to hide all of this new filtering among other features that are needed for spam and whatnot, leading people to think something was actually broken.

    Do I have that right?

  • source
  • hideshow 10 child comments
  • load more comments (3 replies)
    [–] 123 points 2 months ago* (last edited 2 months ago) (34 children)

    I just read about this and it's kind of insane. Thank you for all your efforts!

    I honestly didn't catch that this server was one of the blacklisted ones. Seriously fucking wild.

    Those db0 kids are chill.

    EDIT: Just looked at the JSON.

    What the fuck they blocked YOU, @ada@lemmy.blahaj.zone ? Seriously what the flying fuck.

  • source
  • hideshow 34 child comments
  • [–] 80 points 2 months ago (25 children)

    They got my piefed account too!

  • source
  • parent
  • hideshow 25 child comments
  • [–] 66 points 2 months ago* (9 children)

    It really roils me because you seem to be one of the most level-headed people in the Fediverse. I love running across your comments in random threads because you always have something of value to add, and you write well, to boot.

    As you said yourself, it's not the blocklist that's the issue it's that it's not documented, seems somewhat intentionally hidden (including the apps claim that blocked sites are "incompatible"), and so the people deploying it aren't even aware it's there and don't have the option to disable or change it to suit their needs. It's very, very sketchy behavior on the part of the developer.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 33 points 2 months ago (7 children)

    I was peeking around on db0's post about it, and somebody mentioned that it's really bad code structure, too. Which is true, hard-coding lists is atrociously hostile to convention and clean habits. It would be like if a chef never washed their hands because they thought it added flavor.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 12 points 2 months ago (4 children)

    Hard coded lists are sometimes ok… but not for something that will change frequently like a ban list of websites

  • source
  • parent
  • hideshow 4 child comments
  • load more comments (2 replies)
  • load more comments (1 reply)
  • load more comments (15 replies)
  • [–] 24 points 2 months ago (1 child)

    Those db0 kids are chill.

    Yeah, looking at the commit history from before db0 was officially blocked is interesting. It started with a content warning system. It was designed to give users a “be cautious when interacting with this instance, they encourage violence against people they disagree with” warning. Conveniently omitting that the “people db0 disagrees with” are typically straight up neo-Nazis and supes. Apparently the dev takes issue with “punching Nazis is okay” types of comments. And then a later update silently added the blocklist instead of a content warning.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (6 replies)
    [–] 67 points 2 months ago* (last edited 2 months ago) (1 child)

    The fuck?? Why in the world is a front end blacklisting people or instances??

    ETA: This is literally the first thing I see after coming back from a break. Also, I'm so sorry you have to deal with this Ada, the dev sounds like a jackass

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 55 points 2 months ago* (last edited 2 months ago) (14 children)

    Poking through both /src/lib/blacklists.ts and the double-secret policy file that gets pulled on load (see snot flickerman's comment on how to look at it), I'm having a hard time wrapping my head around the end goal of blocking this specific set of keywords, fediverse peers, communities, users, etc.

    You've got radical right stuff in here with radical left stuff, lots of lie-peddling news outlets and state-backed propaganda sources as well. Lots of focus on Russian-sourced content, and some attention paid to American MAGA crap. It's quite strange to find blahaj hostnames and users among them.

    My best guess is that this is a hammy attempt to make Tesseract a more bland beige version of fediverse content with the pointy jagged parts filed off. But porn is a-ok.

    Really weird choices.

    UPDATE: The Tesseract project author made a public post addressing the obscured ban list: https://lemmy.world/post/49817942

    There’s some clarity provided, most interestingly recontextualizing the hidden ban list as a “toxic mode” setting that can be turned on and off by the instance admin. So sure, that’s nice and all, but it still groups our entire instance, and our admin, in with the literal worst of the internet, making us banned by default. That’s the moral assessment this person has made of us, with no justification or receipts to back it up.

    Just…

    "These are all rough edges of the threadiverse which I am attempting to round off so we might actually be able to retain some level headed people instead of scraping the bottom of the barrel by being a dumping ground for people rejected by civil society."

    That’s pretty warped, but I don’t want to call it unforgivable. I just want the author to introspect and say more about why they feel this way.

  • source
  • hideshow 14 child comments
  • [–] 59 points 2 months ago* (last edited 2 months ago) (5 children)

    EDIT: I was right. This is from their angry defensive screed.

    To be blunt: Tesseract is designed to attract and retain normies.


    There's certainly a subset on the Fedi who seem to desperately want it to become a massively popular thing that persists through the ages instead of small but deep and worthwhile community growth among those who do choose to participate. Will it last forever? Probably not, most things don't. Friendster died before MySpace and people forget it even existed (I mean, it was legitimately terrible)

    It makes me wonder if this person thinks that they're making the Fedi more palatable for "normies" or something.

    Because popularity always brings a marginalization of already marginalized communities. This comic sums it up pretty well.

    Honestly, I think as long as we stay small and have our own community existing under the radar so to speak we have less likelihood of being invaded by even more numerous asshats than we already do. Lemmy or Piefed becoming massively popular could actually be a detriment, especially in terms of hosting costs, since most instances are funded via donations or the admins own personal income.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 23 points 2 months ago

    I’ve been a part of online communities for a long time. The ones I value most in retrospect were relatively small, niche and disconnected from grand global everything-platforms.

    The fediverse is a step towards an internet of a million weird micro communities, finding ways to talk to each other.

  • source
  • parent
  • load more comments (4 replies)
  • load more comments (3 replies)
    [–] 47 points 2 months ago (2 children)

    Why are some people so batshit insane ???

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [+] 40 points 2 months ago* (1 child)
  • [–] 39 points 2 months ago (11 children)

    Whelp that explains why I'm experiencing login-loop at the blahaj.lemmy.zone landing page... I liked the UI & UX of Tes. Oh well.

  • source
  • hideshow 11 child comments
  • [–] [S] 29 points 2 months ago (6 children)

    Same. It was my default lemmy UI.

  • source
  • parent
  • hideshow 6 child comments
  • load more comments (4 replies)
    [–] 36 points 2 months ago (7 children)

    This one is just getting wilder and wilder the more the code is analysed

  • source
  • hideshow 7 child comments
  • [–] 34 points 2 months ago (3 children)

    Good. I support this decision.

  • source
  • hideshow 3 child comments
  • [–] 30 points 2 months ago (15 children)

    What's the deal with this Tesseract developer? Did they just block everyone that has ever looked at them funny? I looked at the blocklist and saw all kinds of people: trans-oriented, piracy-oriented, and lots of tankie-oriented instances. And a lot of users I'd never heard of.

    Now they've taken their whole site offline, presumably so they won't have to answer any questions.

  • source
  • hideshow 15 child comments
  • [–] 31 points 2 months ago* (last edited 2 months ago) (14 children)

    Now they’ve taken their whole site offline, presumably so they won’t have to answer any questions.

    Tea is just all over the damn floor at this point.

    ...but like... what did they think was gonna happen? Did they think they were so clever that no one could figure it out? Even when it effectively broke functionality on sites that used it but were blocked? Like they couldn't add in code to disable specific parts of it if it was deployed on one of those sites so they could keep the whole thing secret? Like just another little regex search string to ignore any users and sites that match the site domain as its rolling out, so they would keep using it and be none the wiser because it would work for them but continue to have its blocklist maintained and secret because it wouldn't cause any problems.

    I hate that it takes me like zero effort to conceptualize a better way to have done this shady shit, but on the other hand I guess I'm just glad they weren't that clever.

    EDIT: Upon reflection, I do wonder if this was at least partially vibe coded, because LLMs don't have forethought and can't plan ahead for contingencies like that. Because it also seems like a no-brainer that it would lead to configuration failures if deployed on one of the sites that is blocked.

  • source
  • parent
  • hideshow 14 child comments
  • [–] 15 points 2 months ago* (13 children)

    EDIT: Upon reflection, I do wonder if this was at least partially vibe coded, because LLMs don't have forethought and can't plan ahead for contingencies like that. Because it also seems like a no-brainer that it would lead to configuration failures if deployed on one of the sites that is blocked.

    The dev was quite vocal about being against LLM usage. Most notably, I remember their April Fool's Day post about an update that adds a bunch of AI features. The post was obviously just a big joke, full of disparaging comments about LLMs. With that said, that was April (maybe even 2025, I can't remember). It's possible that their opinion had changed in the time since. But I doubt it, personally.

    EDIT: It was 2025.

    Canonical link: https://dubvee.org/post/3069664

    Mirror: https://lemmy.world/post/27634335

  • source
  • parent
  • hideshow 13 child comments
  • load more comments (13 replies)
  • [–] 30 points 2 months ago (10 children)

    I used to use that frontend, and I am in that block list. What irony!

  • source
  • hideshow 10 child comments
  • [–] 27 points 2 months ago

    took me a while to realize that tesseract is also the name of a lemmy frontend. because there's also tesseract-ocr which is used for optical character recognition. (i started using tesseract-ocr yesterday to scan all my meme images for text to make them easily searchable).

  • source
  • [–] 25 points 2 months ago

    seems like a good move, thanks Ada!

  • source
  • [+] 20 points 2 months ago (12 children)
    load more comments (12 replies)
    [–] 19 points 2 months ago (3 children)

    Looks like it's now been removed from GitHub too... That chode went from 9 to 8 repos.

  • source
  • hideshow 3 child comments
  • load more comments (3 replies)
    [–] 16 points 2 months ago (2 children)

    What a sad loser. May his days be short. 👍

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] 16 points 2 months ago (8 children)

    After the Rimu fiasco I tried returning to Lemmy and found Tesseract to be my favorite frontend primarily because of the ability to create community lists w/o subscribing to them (the closest thing I found to Piefed Feeds).

    And then this happens...

    I'm going back to Reddit

  • source
  • hideshow 8 child comments
  • load more comments (8 replies)
    [–] 14 points 2 months ago

    It never ends. I'm sorry and thank you for everything you do for us. We value your labor on our behalf. 💖

  • source
  • load more comments
    view more: next ›