ChandlerSwift
commented
3 years ago One potential way that this could be managed is simply by logging every request every person makes. It is likely that winds up with a total of a few thousand records (or fewer) for a competition of ~25 students. (n=3 gave 15, 15, and 42 page loads, though that's a bit on the small sample size side, unfortunately.)
This could be a "last logged in" timestamp that shows up in the admin panel, or could be us keeping track of attacks submitted/
git pushes/similar, though that may have problems if one person is contributing in ways that don't involve them actually submitting attacks/code (e.g. analyzing others' programs, pair programming, ...)