Steps forward for robocop-ng and its many forks #82
Description
Background: danny is stepping down as maintainer of discord.py, and everyone he trusts to pass over maintainership to has also refused to take over the project. I understand, respect and agree with their reasoning.
My personal approach in most cases would be "fuck this, fuck discord, let the bot die", but robocop-ng and its many forks are moderation bots, I can't quite do that without risking letting harmful content into the communities.
I will do another rewrite of robocop-ng, possibly starting in a month or so to let the dust settle. Perhaps discord will revert some changes, perhaps good forks of discord.py will arise, and perhaps neither of those will happen and I'll need to undergo a much more significant rewrite, but in the end, we'll see ™.
It isn't strictly necessary to quickly rewrite robocop-ng, especially as its supposed to be used in a single server and can use the message content intent without verification (for now), but discord.py no longer being maintained means that we'll miss out on important features (and stop working once the API version we use shuts down), and indeed, even right now we do not support threads and such (and this will only get worse).
If anyone has any recommendations for forks, libraries etc for me to look at etc, let me know.