Felix Dreissig
Felix Dreissig
Spin-off from #56: Improve the performance of Service History rendering, e.g. using IntersectionObserver.
The current Checker libraries (Python as well as Go) use a hardcoded number (5) of past ticks to check the flags for. We should be using the number of valid...
Display the first team to exploit a service ("first blood") on the scoreboard, kind of like ENOWARS did: 
Writing checker scripts is currently heavily Python-specific, though there's no reason why it has to be like that. I'd wish for more language options. Languages that come to my mind:...
Doing scoring thorugh a Materialized View is nice from a DB point of view, however it causes some problems in practice: * Nobody besides @siccegge really understands the SQL, let...
In some cases, scores that are 0 do not cause the score value ("0") to get rendered on the web scoreboard. This is some combination of no total points for...
There is a "bonus" field in the "scoring_flag" table, which somehow gets incorporated into scoring but (hopefully) is never actually used. I don't know what the semantics of that are...
Important announcements during the CTF could be shown above the scoreboard, which a lot of people are looking at all the time.
In addition to #32 and #33 we might want to support launching Docker containers for checker scripts. This would make testing and deployment of checker dependencies easier. One container per...
I'm not sure if data from the "GameControl", especially regarding timing, is currently processed by all components in an optimal way. Questions include: * What happens when the Controller does...