There’s a lot of features I wanted to implement for a long time, and that people would actually want to see here. For example, it would be nice to have a proper configuration script instead of “fuck around and find out” with loose documentation. Another one is reposting of favorites, which may be impossible without constantly polling updates from an instance (not good!). Another one, and really important: edits and deletes propagation. Basically, I would need to connect a database to it somehow, but I can’t even decide on which one. I could use sqlite, but it’s not async-friendly, and my project is kinda asynchronous in mind. I don’t want to get rid of that, but at the same time adding bulk of “proper” database is too much for such a small project. I could add configuration option so you can use external database, but this way I would have to support multiple database drivers, or use ORM.

You can look at issues tab on its github page: https://github.com/hatkidchan/mastoposter/issues

@hkc
Between 5 and 10.

By the way these bots exists are not because of "lack of moderation".
You can't moderate something you can't see until users reported it to you. And most of the bots were sending a SMALL batch of DM's until going offline. It's not that one account was sending thousands of messages and nobody took care of that.

Also mastodon doesn't have very good anti-spam measures. So blaming moderation team of any instance (even mastodon.social) for that is quite shortsighted.