search

Study-Together-Org / time_counter

12 stars 5 forks source link

Excessive hour detection? #34

Open Arianthell opened 3 years ago

Arianthell commented 3 years ago

This is to prevent over 24h+ issues like "swossboss" today when its caused by discord error (discord didnt send his voice leave info to the bots, now he has 400h+) , but also could work for people doing excessive hours on purpose:

Can the system detect the people who stayed in the call for 20h in the past 24h and didnt leave the call for at least 30m/1h etc during that 20h (meaning they didnt take any long break during that 20h), and send a notification to staff server with username or ID?

So that we can check if they are still in call when the notification came. If they are not in call, we can trigger a leave notification to the bots manually via a command (or simply notify Zack/Nadir) . If they're still in call, then the bot checks again after 6h or so, if they didn't take a long break/still in call, the bot sends us another notification.

So if a user is doing extreme hours with little to no break for longer than a week or so, the bot will keep sending us their name/ID. If someone's name appears 20+ times = excessive use. This way we can detect the cheaters too.

Zackhardtoname commented 3 years ago

Seems like some feature like this will be inevitable What do you think @nadir7379

nadir7379 commented 3 years ago

Seems like some feature like this will be inevitable What do you think @nadir7379

Excuse the very late reaction but this is indeed something that was planned on the long-term.

People with excessive hours are inevitable - people always find ways to cheat the system (for whatever reason).

Those people need to be filtered away, to make it fair for the people that are actually studying (and thus not just farming hours).

In general I agree with Arianthe's idea. The key point is: The system should be able to detect longer-term excessive hours (in other words: one all-nighter should not filter you away).

I'll be more responsive in the future to these threads. Feel free to reply.