As part of the devs farewell message on their site, they have included malicious code to make each visitor sends 2,000 requests to the dbzer0 servers in an attempt to DDOS and take the instance offline.

  • BluescreenOfDeath@lemmy.worldEnglish
    16·
    23 hours ago

    Basically, yes.

    Tesseract was downloading at runtime an obfuscated blocklist of users and instances. One that the dev didn’t tell anyone about, and didn’t give an option to disable/modify.

    db0 was trying to update Tesseract and was unaware that the whole dbzer0 instance was blocked in this way. And because the Tesseract dev is a spherical bastard, rather than saying “this is blocked”, it said there was an API mismatch, which sent db0 down a troubleshooting rabbit hole that ended with him blowing the whistle on the whole thing.

    And you can see how mature and wise the developer is for how he responded.

    • JackbyDev@programming.devEnglish
      1·
      10 hours ago

      Small point of order, there was an option to disable it, but it was extremely hidden and buried in the advanced settings area and called “enabling toxic mode”. Also, this only disabled the runtime policy. There was no way for end users to disable the instance list that was in the source code itself.

        • zarkanian@sh.itjust.worksEnglish
          1·
          15 hours ago

          If you fork it, the fork doesn’t belong to them. You can do what you want with it.

          Besides, if they don’t want to maintain it, why don’t they stop maintaining it right now? What does Lemmy 1.0 have to do with it?

          • GreenKnight23@lemmy.worldEnglish
            3·
            14 hours ago

            just because we found two things he did doesn’t mean there aren’t other surprises.

            for all we know at this point, he’s implemented a backdoor into instances that use it.

            if you’re an instance admin using tesseract and you’re reading this right now, you should probably drop it asap.