Great work. It doesn’t matter who the target is this time (pretty sure I blocked them every time they popped up with a new account). This kind of shit should not be tolerated at all.
this post was submitted on 08 Apr 2025
1 points (66.7% liked)
[Closed] Moved to !fedigrow@lemmy.zip
1584 readers
1 users here now
This community has moved to !fedigrow@lemmy.zip
Original sidebar info
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- !fedibridge@lemmy.dbzer0.com to organize overall fediverse growth
- !reddit@lemmy.world to keep tabs on where new users might come from :)
- !newcommunities@lemmy.world
- !communitypromo@lemmy.ca
Megathreads:
- How (and when) to consolidate communities? (A guide)
- Where to request inactive or unmoderated communities? (A list)
Rules:
- Be respectful
- No bigotry
founded 1 year ago
MODERATORS
This highlights one of the things that I saw as a benefit when I started on kbin: being able to see who the downvote fairies were. I know the discussion has been done to death on the Lemmy side, but as a user I found it interesting to be able to see this kind of info. For example, instead of just block/reporting the spammer, I could block their sock puppets that upvoted as well. (And did kbin.social have a lot of that towards the end. Oof.)
Thanks for digging into this.
Lemmy currently allows mods to see downvotes, so they can fight brigading on top of admins
You mean admins, right? I cannot see downvotes on the community I mod.
Use https://tesseract.dubvee.org/
What it does look like (there were no downvotes here, but they would appear as well)
How do I use this for different instances? I'm thinking of starting an instance. Is tesseract good for any instance or just dubvee?
The attacker is the admin of these two instances. Both instances have their registrations closed.
When I look, both have open registrations and don't even have a captcha? You see registrations as closed?
It could be that Fediseer is outdated. I looked at the instance's fediseer page.
https://gui.fediseer.com/instances/detail/chinese.lol
https://gui.fediseer.com/instances/detail/lemmy.doesnotexist.club
Edit: Their registrations are indeed open. Perhaps they opened it just now?
Though it is also suspicious why the owner leaves the registrations open, requires no captcha, no approval nor any email confirmation, and the admin of lemmy.doesnotexist.club has been inactive since their account creation. Seems suspicious to me.
They have both had open registrations for at least several hours. I think perhaps there's something wrong with Fediseer's detection?
Given the issues, I'm guessing these instances have been open for some time. lemmy.doesnotexist.club has definitely had a few "Nicole" accounts and some trolls.
I checked the web archive. The registrations have been open since 2023. I think it's safe to assume that the admin is indeed the one behind this and possibly also behind the nicole spam. And it has been a year since these bot accounts were created and they are still being created, the admin does nothing, does not interact with anyone, but still hosts the instance.
https://web.archive.org/web/20230809200352/https://lemmy.doesnotexist.club
We desperately need some system to fight against these type of attacks. It is still not much of a problem. Creating bot accounts and then spamming the entire Fediverse isn't hard but defending against it will be in the future.
Why do you assume the admin is behind it? If you have an instance that has open registrations and no captcha, then bots will take advantage of that. It doesn't mean the admin is the one doing the attacks.
In fact, such instances are more common than they should be since open registrations with no captcha is the default configuration, last I checked 😑