Comment on Discussion: Long-term need for automation tools for moderation

<- View Parent
asudox@lemmy.asudox.dev ⁨1⁩ ⁨week⁩ ago

Yep. I did use those endpoints with the ModeratorView (The bot doesn’t need posts or comments from communities it doesn’t moderate) on my first attempt. I went with the federation approach at last because of future scalability issues. Though that is probably an exaggeration. If the default rate limit is 180 requests per minute, that would be more than enough, honestly. The scale at which the scalability issues I mentioned appear at about more than 4500 comments/posts per minute. If I am being realistic here, we’ll probably never reach that in the near future. So actually the rate limiting issue is practically not an issue in the foreseeable future.

The plugin system would work. The fetching problem would also disappear.

Though I don’t think the federation code would be huge. I am not trying to make it compatible with all platforms. For example I’ll write the required ActivityPub structs to send moderation related activities and actors. The Group’s instance would handle distributing the activities, so even though this project might not federate with Piefed for example, it would still receive the activities the bot sends to the Group’s inbox through the instance’s software, Lemmy.

If someone wanted to get the bot to work on another Ap platform that supports groups, they would have to write the necessary Ap actors, activities, and a bit of glue code, and that would be it… or at least that’s how I’m planning it.

I guess I’ll try to work with the plugin system if I can’t achieve what I want and keep it simple. It would at least be a learning experience, if nothing else. Thank you for the info.

source
Sort:hotnewtop