New anti-bot rules
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Feb 2026
250 points (92.2% liked)
Comic Strips
22318 readers
2073 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- AI-generated comics aren't allowed.
- Limit of two posts per person per day.
- Bots aren't allowed.
- Banned users will have their posts removed.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 2 years ago
MODERATORS
It's fairly easy for a bot to post at random times. However it's possible to create a bot to check for bot behavior.
I made a few tests with bot moderation and quickly reached Lemmy.world instance limits (because the bot needs to read the posts consecutively and also get the user's public data).
When the account reaches the limit, it can't log in for a period. I don't want my account to be banned, so I will not continue trying to create moderation bots for Lemmy instances.
feel free to get in touch with us if you have issues with api limits. we can't change them for individual users but we may be able to give you advice on more efficient usage.
your bot shouldn't be logging in every time it checks what is going on; it's best to persist the JWT you get from logging in and keep using it. the signup/login rate limit (which for whatever reason has the same counter) is relatively low to limit abuse, but the other endpoints should be more relaxed. you'd also have to hit pretty high request counts for us to even look at it. i recommend using a separate bot account (see bot rules).
Hi @MrKaplan. I will continue my efforts to improve my moderation bot by following all your recommendations, such as implementing persistent sessions and creating a different account for the bot, also adhering to the bot rules of the instance. Additionally, I will slow down consecutive calls to the API. Let's see how it goes. Thank you.
What are the limits? I don't think it needs to run constantly. Something that checks every few minutes would be a strong enough deterrent imo.
The bigger problem is that the user can just make his account ahead of time.