Closed cokesme closed 9 years ago
I suggest we setup a login system for our local CTF challenges where each user account keeps track of flag submissions. I would keep local flag submissions separate from actual CTF solves, but track them both. We could even display a scoreboard of people's weekly flags.
On Sep 26, 2014, at 1:04 PM, Cody M notifications@github.com wrote:
We want to start tracking involvement at CTF practices and eventually track participation in real ctf's. How should we design a system that can keep track of things beyond just flag submission? Should we start with just that?
— Reply to this email directly or view it on GitHub.
Discussed this with ditmar over IRC. Here's a tentative feature list:
probably shouldn't require a reason/justification for solves.
also definitely:
gauged interest via IRC on what lang/framework:
17:15 < gadams> Django, Flask, Drupal, NodeJS, ASP.NET MVC4
17:15 < connerb> angular + node
17:15 < TinFoil> I would actually contribute to a Django or Flask project
17:24 < cokesme> 1. nodejs+angular 2. Django or Flask ~3. rails
17:20 < dwn> also my list in pref order is: nodejs+angular, ruby+sinatra, flask, php+codeigniter or other
17:27 < digitalcold> I would personally say pure PHP and SQL.
pure PHP + MySQL I think would be the best
Has CTFing taught you nothing about PHP/MySQL? Pls no lol
On Oct 22, 2014, at 7:32 PM, Connection notifications@github.com wrote:
pure PHP + MySQL I think would be the best
— Reply to this email directly or view it on GitHub.
https://github.com/HackUCF/internal-scoreboard
The race is on
We want to start tracking involvement at CTF practices and eventually track participation in real ctf's. How should we design a system that can keep track of things beyond just flag submission? Should we start with just that?