Nice! I'm also planning to add more platforms if users show interest, but for now I'm focused on twitter for a long time.

I have a process to always follow my followers (and unfollow unfollowers) so I can DM them.

Regarding the checks, the initial free plan (just following my bot) comes with weekly checks. That means I'll fetch your followers once a week and compare with last week's, find out who is missing and sending you a DM with the list of all unfollowers. So you'll basically a weekly DM with unfollowers.

Daily, hourly and realtime plans work in the same way but with a higher frequency, but without any kind of digest, just one DM with the list of unfollowers in the time window.

I hope I never receive any message from this service, but good idea anyway :)

Author here. I build this to learn and ship something with Elixir. I know it's not a new idea, there are plenty of alternatives to track unfollowers, but couldn't find any that works inside twitter. I got the idea recently reading some political tweets about a situation in my region (Catalonia, Spain). I usually follow tech people and this days they're tweeting political stuff and I wondered how many people unfollow them after those tweets.

I'd appreciate any feedback :)

http://userstyles.org/styles/37035 does

Being a bit paranoid, how do I know you won't login as any of my users without their permission? Or in other words, if your systems get compromised, how can I be sure that my system won't get unauthorised logins?

Interesting. IMHO it seems useful for playing around with different languages, but not for using it more seriously. Anyway, it looks fun, good job :)

Thanks! And you're right - it is not intended as a production tool.

If there's nothing queued it starts almost immediately. In some cases while testing the job finished right after queuing it and showed as completed right away. Right now it uses rabbitmq for the queue but even if I replace it I want to keep it like that.

Yup, I know that building a docker image for every job can add a lot of friction to the project, but it adds lots of flexibility to the users.

Thank you. Regarding your needs, I assume you'll also need access to the DB and so on. I'll have to figure out how to run the jobs as close as posible to the customer database.