They’re trying really hard to make their AI-plagiarized slop “news” site happen. You’ll see posts linking to primestories24 [dot] com but they’re AI slop regurgitating likely legit news articles. Every “reporter” has some generic profile that is most likely the system prompt used for everything they “write”.
If you see a post to that domain, report it as spam. The accounts all look similar to this:
- @Bellar36@beehaw.org
- @Belinda42@lemmy.wtf
- @tatyana43@piefed.ca
- @Graham43@sopuli.xyz
- @Belinda43@fedia.io
- @belinda35@piefed.social
- @PrimeStories247@lemmy.ca (First ban-evasion alt)
- @PrimeStories24@sh.itjust.works (Original account)
This list isn’t comprehensive.
Update: They are now using sockpuppet alts to vote/boost their posts. Just found @Babrah28@ttrpg.network that way and, surprise surprise, it was registered the same time as the latest batch.
Note: Technically the above is violating rule 7 if you consider spambots to be members. I don’t, but if this is a problem, let me know, and I’ll remove that part.
The domain was registered in May of 2026 and is roughly when these accounts started popping up.
Domain Name: PRIMESTORIES24.COM
Registry Domain ID: 3105727536_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.web4africa.net
Registrar URL: http://hostafrica.com/
Updated Date: 2026-06-19T10:01:29Z
Creation Date: 2026-05-31T12:16:00Z
Registry Expiry Date: 2027-05-31T12:16:00Z
Registrar: Host Africa (Pty.) Ltd.
Registrar IANA ID: 664
Registrar Abuse Contact Email: abuse@web4africa.net
Registrar Abuse Contact Phone: +1.6465850088
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DAN1.HOST-WW.NET
Name Server: DAN2.HOST-WW.NET
DNSSEC: unsigned
Admins, I’m aware Lemmy is severely lacking in moderation capability, but one thing it does have is domain blocking. That prevents posting to those domains and it now seems to prevent links to those domains from federating in.
Can Lemmy ban outgoing link URLs? Given the spread of slop websites, that seems like useful functionality… Could even combine it with an AI slop URL blacklist…
There were various Reddit automod bots that went after these, but then you had people trying to evade them by using one of the zillions of link shortener sites out there, so then you also have to ban link shorteners or try to resolve all the links (which may be a good idea as well, but saying that it’s a more-complicated problem than initially meets the eye).
Also, I was banned in a few communities by an automod bot on the Threadiverse, and given that it happened when I posted some comment linking to a number of sites, I assume that one of the URLs must have tripped some automod list, so I’m a little irritable about bots running permabans on blacklisted sites, as users can inadvertently link to them.
URLS, no, but it can disallow specific domains. So it could work against specific spam domains but not against a bunch of accounts spamming, say, a Github repo, unless you want to block links to all of Github which isn’t ideal.
There’s a list of disallowed domains that can be configured in the admin area. Until relatively recently, it would only prevent users of that instance from posting to them, but somewhat recently it now prevents inbound federation of anything linking to those. If something links to a blocked URL (post, comment, user with that in their bio, etc), Lemmy will reject it.
I don’t know why more admins don’t look at the spam that gets modded and add the domain to their URL block list other than it being tedious work lol.
It does work on URLs. The https part gets stipped out because of how the regex is built internally, but you can absolutely block a Github repo. I have a Discord invite link in the feddit.uk one.
It always worked on federated content? It was added in response to a Mastodon spam wave (source: I added it).
Seems like scripting that wouldn’t be a super heavy lift.