1372
Tesseract dev injects malicious code into browser to illegally DDOS the dbzer0 instance (thelemmy.club)
submitted 1 month ago by to c/fediverse@lemmy.world
487 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 month ago (1 child)

And every user that uses that software for whatever reason, superior features, easier on the eyes, more popular it's what everyone recommended will get their curation from that one dev.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 1 month ago (1 child)

    Which is why it’s ultimately the decision of the admin. Don’t like what the admin of your instance is doing. Go make your own. That’s the beauty of the fediverse. It’s choice all the way down. It’s not like Reddit where you’d be stuck.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 1 month ago (1 child)

    Huh?? It's not up to the admin, that's my point, the list is implemented by the dev and every instance that ran tesseract ran the same blocklist. My point is that it should be up to the admins of an instance, not the dev of software that gets deployed on multiple instances...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 month ago (1 child)

    Okay. I see where the disconnect is. We’re both saying the same thing. In my earlier comment I said “as long as the Dev is open about it and it’s configurable by the admin”. What the tesseract dev did was wrong, what I was saying though is that a dev creating and managing a list is fine as long as those other conditions are met.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 month ago* (last edited 1 month ago)

    But then the admin isn't managing the list the dev is! You have one guy managing a list across multiple instances, that circumvents the public modlog, where users do not know how they got on, or how they could get off, and the power to shadowban across multiple instances is concentrated in the hands of just one guy!

  • permalink
  • fedilink
  • source
  • parent