wookie184

Thinking about this a bit more, it would probably make more sense to remove the current scheduler completely and add another check that they've been in the pool long enough...

> This may seem like an innocent thing to add, but how do you propose to actually track user activity. Doesn't that also get into privacy issues? By user activity...

I'm going to work on a slightly simplified version of this.

Is this still necessary? I think the issue was fixed in https://github.com/python-discord/bot/commit/2b2dc95f2aa2ac6606b51be183861f2663be3b3e

Since it's a bit more robust to have the check in the same place that the role is applied I think we could do this anyway. I'll take this over...

should probably remove the `ctx.send` as well as `apply_ban` will already send a more specific reason

> I can take on this issue if needed Sorry for not getting back to you, that would be appreciated, yes!

I'm not sure exactly what message you're referring to there. The general form for `!mute`, `!ban`, etc is > Applied \ to \ until \ (\) e.g  This issue...

This tag feels like it's trying to *compare* generators and iterators, which I don't think makes sense. Since a generator (function) returns an iterator, this feels a bit like comparing...

There are two issues here. Firstly, the reason the request fails is that the command fetches a random page up to the total number of pages https://github.com/python-discord/sir-lancebot/blob/6609ceab1600ae5d08c2614f5a0f994b86f8ba5e/bot/exts/fun/movie.py#L88-L89 However the page...