If they only downvote everything, I think they deserve a ban.
Lemmy version 1.1.0 will include the ability for mods to remove votes. Hopefully also logged to the modlog, because we know some mods will use it for some other purpose.
Miss stuff as in there might be changes to the post or comments users make within that interval, which the bot will never know of. I need the bot to be notified of any new content the moment it is federated to the bot's instance.
And polling for new content will increase the amount of API requests per time unit as the bot gets added to new communities. I'd rather have it be somewhat future-proof, because if Lemmy ever gets more popular than it is right now, there might be a new post made to a community every few minutes. It will especially become a big problem for new comments, as they are created more frequently than posts.
That is not an option as it has the chance to miss stuff and it's also too many API requests. Mentions would be the solution if the bot simply responded to commands, which is not the case.
That is why I considered either LemmyWebhooks or just directly querying the database. The best choice here seems to be querying the database.
I don't know about such a platform, but I'm making an automod for Lemmy that works by users writing their own plugins. So the users are pretty much responsible for making the bot work the way they want it to. That means you actually can pretty much make any bot that can only interact within the community you mod. I just haven't been able to progress much as I've been stuck thinking about how it would receive certain events such as new comments, new posts, etc.
Some instances enable the image proxy, which should prevent this.
@TomMonkeyMan@chinese.lol @yassinsiouda@lemmy.doesnotexist.club
Voting here doesn't influence your feed
It does when you use sorting algorithms that depend on it.
it might just default to saying 'closed' if it doesn't have the data.
Nope. Fediseer displays unknown fields as N/A
.
The admins can reasonably be blamed for setting up instances with open registrations and no protections and then forgetting about them
No, I don't think they forgot. Would you forget about something you regularly pay for?
Well yeah, there is no concrete evidence that it is the admin (or the admins). But the hints I found seem to be pointing that they are the one behind this. Of course there is a possibility that it is someone else, but it baffles me why anyone would leave the registrations open for 2 years, keep the instance running, but never interact with the fediverse through it themselves. And this isn't exactly like kbin.social, the admin eventually did respond and close down the instance (not to mention, the admin was still communicating with the people). This instance and its bots have been going on for over 2 years, with not even a single sign of activity from the admin(s).
Nevertheless, defederation is the right thing to do right now. Unless concrete evidence is found, we could put this aside.
The bots are from those two instances as you can see in the screenshot. Furthermore, lemmy.doesnotexist.club has had dozens of bots since at least 2023 (2 years after domain creation. found via the web archive). Since at least 2023, the admin hasn't been doing anything, or even interacting with anyone. That account seems pretty much dead. But they keep hosting the instance for some reason. It is also a possibility that someone else indeed is using these two instances because they are "abandoned", but it is highly likely that it is the admin. It is very suspicious that the registrations have been open unguarded against bots since at least 2023. These two instances have been invaded with bots long ago, so defederation is still the right thing to do.
I also don't want to jump to conclusions, but I think the chances are pretty high that it indeed is the admin. It might lead us to whoever is behind the recent nicole spam.
Is it deleted or removed?
Deleted means that the creator deleted it, which won't be logged to the modlog. Removed means a moderator or admin removed it, which will be logged to the modlog.
It could also be that the user was instance/community banned with the purge content option enabled. Which might confuse you, because the posts won't have a modlog entry regarding their removal. The purge content option's status is not logged along with their ban. So be sure to check if they are instance/community banned as well.