If anything, it’s getting too little attention. Someone effectively snuck malware into several large instances and then separately, and maliciously, attempted to DDOS the instance that blew the whistle. That is massive.
As a security and community building risk, it’s genuinely a pretty big issue. One that will cause people to scrutinize the contributions of others more closely. Trust broken etc…
I won’t disagree with the gossip note. Though I genuinely can’t differentiate between water cooler and old folks home gossip. The only difference is the name of the drugs.
Also, it’s having the negative effective of a fracturing and lots of instances blocking each other. Which is crazy anyone can be on the side of a someone who literally set up a DDoS, which is a fucking crime in a lot of places.
Right? Sure, fine “I wanted to make things less toxic blah blah blah.” I can follow you there, motivation-wise. Actively weaponizing unsuspecting lemmy users, many against their own instance, in your attack on an instance that solely sought to disentangle themselves from choices you silently foisted upon them?
How do you not see the line and its extremely dramatic crossing? I guess I shouldn’t be too surprised, considering the stamets situation and how it resolved.
Stamets used to be on a broad Startrek instance mod team with Kirk, where Kirk would go on long tirades about how people were bullying and threatening him and how he should have singular say over their communities. How they aren’t doing enough to curb rudeness and dissent. Then he way overstepped, somehow. Maybe started banning en masse for silly reasons? I can’t recall specifically.
Rather than doing anything about the mentally unstable goober, startrek’s head admin, a friend of Kirk, washed their hands of the situation and stamets left their mod teams to create separate communities on other instances, which are the Star Trek meme communities we see today. And Kirk took all of this as a personal attack, and stated something about death threats, but no one was listening at this point.
Long story short, Kirk’s always been a dictatorial weirdo. Only recently have they become a real, tangible nuisance.
Super short version. Tesseract is a lemmy theme that users can choose to use. However, it also surreptitiously blocks some instances and many users from view for “toxicity.” Because it’s lemmy, the blocks were overwhelmingly anti-left and anti-trans. Whether this is exclusively demographics is up to you, but that is my perception. All of this 100% undisclosed. They intentionally, quietly broke some sites for a long time.
When they were found out, they posted a manifesto on their own instance and included a DDOS script in their html, causing users to call the db0 api hundreds of times per visit. This didn’t bring down db0, but did piss everyone off even more and cause the theme dev’s site to be taken down by their hosting company for illegal activity. Now we’re here, discussing it on the day after.
If anything, it’s getting too little attention. Someone effectively snuck malware into several large instances and then separately, and maliciously, attempted to DDOS the instance that blew the whistle. That is massive.
lol. It’s really not massive.
It’s like watching old women gossip.
As a security and community building risk, it’s genuinely a pretty big issue. One that will cause people to scrutinize the contributions of others more closely. Trust broken etc…
I won’t disagree with the gossip note. Though I genuinely can’t differentiate between water cooler and old folks home gossip. The only difference is the name of the drugs.
Also, it’s having the negative effective of a fracturing and lots of instances blocking each other. Which is crazy anyone can be on the side of a someone who literally set up a DDoS, which is a fucking crime in a lot of places.
you’ll have to ask the startrek.website admins; they decided to defederate citing reasons that they refuse to exemplify.
fwiw it atleast makes sense since the tesseract developer used to be a member of their team.
Right? Sure, fine “I wanted to make things less toxic blah blah blah.” I can follow you there, motivation-wise. Actively weaponizing unsuspecting lemmy users, many against their own instance, in your attack on an instance that solely sought to disentangle themselves from choices you silently foisted upon them?
How do you not see the line and its extremely dramatic crossing? I guess I shouldn’t be too surprised, considering the stamets situation and how it resolved.
what’s the stamets situation?
Stamets used to be on a broad Startrek instance mod team with Kirk, where Kirk would go on long tirades about how people were bullying and threatening him and how he should have singular say over their communities. How they aren’t doing enough to curb rudeness and dissent. Then he way overstepped, somehow. Maybe started banning en masse for silly reasons? I can’t recall specifically.
Rather than doing anything about the mentally unstable goober, startrek’s head admin, a friend of Kirk, washed their hands of the situation and stamets left their mod teams to create separate communities on other instances, which are the Star Trek meme communities we see today. And Kirk took all of this as a personal attack, and stated something about death threats, but no one was listening at this point.
Long story short, Kirk’s always been a dictatorial weirdo. Only recently have they become a real, tangible nuisance.
DDoS? Malware? What, where
Super short version. Tesseract is a lemmy theme that users can choose to use. However, it also surreptitiously blocks some instances and many users from view for “toxicity.” Because it’s lemmy, the blocks were overwhelmingly anti-left and anti-trans. Whether this is exclusively demographics is up to you, but that is my perception. All of this 100% undisclosed. They intentionally, quietly broke some sites for a long time.
When they were found out, they posted a manifesto on their own instance and included a DDOS script in their html, causing users to call the db0 api hundreds of times per visit. This didn’t bring down db0, but did piss everyone off even more and cause the theme dev’s site to be taken down by their hosting company for illegal activity. Now we’re here, discussing it on the day after.
Thanks, I was so out of the loop
fixed it for you.
See, they tried for 2k but coded their randomizer poorly. Technically, it could go up to 2k, but in practice, it likely never went above 1k