Some instances (like mine and lemmings.world) have automated bots to clean up these spam posts everywhere. I think lemmy world has an automod as well, but maybe it's not working as well if you keep seeing these spam posts?
Them turning it up would be good. Also shouldn't there be a duplicate post check built into the platform?
They're not exact replicas. Enough a difference to fool the algorithm.
Interesting, any info somewhere on how to set up some of those auto mod bots?
I mean if we use the same filters these spams are easily recognised.
Interesting, any info somewhere on how to set up some of those auto mod bots?
I mean if we use the same filters these spams are easily recognised.
My bot has a readme with instructions and we're working on a docker image too: https://github.com/db0/threativore
Thank you!
Interesting, any info somewhere on how to set up some of those auto mod bots?
I mean if we use the same filters these spams are easily recognised.
Because lemmy is like a public restroom:
Anyone can, as soon as they feel the need,...
Some instances don't have any checks or barriers for signing up, so the bots can just get accounts from these kind of instances and keep spamming.
It was already discussed in a post here, lrt me see if I can find it
Hate to break your illusion that Selfhosted is specifically targeted. I've not made notes of the spam accounts I've reported/blocked but there were several in OpenSource and others, too.
There was a post earlier today with an explainer on who is doing it: https://lemmy.ca/post/15935073
I'm not sure why this particular instance was chosen, but from what I can tell the spammers are doing it for the memes anyways.
The best you can do for now is to keep reporting them. What you can also do is see if there's a pattern, such as one instance popping up more often than others. Chances are that instance has open signups or something, and lemmy.world (and everyone else) should defederate
My guess is they get @'s from the federated timelines. If so it takes a follow or mention from the vulnerable attacked instance for the spamming bot to add it to the mentions they do. I don't think they just decided to go against this community.
You are not the first one to ask this. We dont know, my guess would be, because Selfhost is so popular it federated almost everywhere, and spammers probably saw that and attacked through that.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!