k9delight

Would be good if we can have material design support as well as bootstrap support.

Perhaps we can ask a tech writer to also go over it to, to ensure it's suitably understandable as well.

With https://github.com/google/ctfscoreboard/pull/75 merged, it introduces a "feature" where users who change teams now are in possession of cookies that have team_tid for both teams (before/after cookie). There was some discussion...

- Using JSON isn't ideal, should ideally by based using database structure. - Time release system should be handled by a dependency system. - Challenges should have an indicator saying...

We should be able to use HTTP Etags for API resources to reduce bandwidth. Taking an etag from the client and comparing memcache.get(resource_type_md5) gives us the ability to quickly identify...

/api/categories appears to do a N+1 based on team count

2

Debug statements: ``` 2016-06-09 09:10:59,794 INFO sqlalchemy.engine.base.Engine SELECT count(*) AS count_1 FROM (SELECT answer.challenge_cid AS answer_challenge_cid, answer.team_tid AS answer_team_tid, answer.timestamp AS answer_timestamp, answer.answer_hash AS answer_answer_hash, answer.submit_ip AS answer_submit_ip, answer.first_blood AS...

Allow team names to be changed

1

The player who registered a team (lowest ID belonging to that team) should be able to change the team name. This will cut back on the occasional support request to...

strip leading and trailing whitespace, flatten to lowercase, etc.

Allows people playing afterwards to continue without the fame and glory

Rotating cookie secret shouldn't break team codes