Hello,
This mailing list will be used for regular technical updates on MapCTF development. The plan is to send one message per week with a concise summary of what changed in the repository, what was built, what was refactored, what was tested, and what technical direction the project is taking.
MapCTF started from a simple idea: continue the kind of work that Facebook CTF helped push forward roughly 10 years ago, but do it with a more modern architecture and a stronger technical foundation. The goal is not to recreate an old platform line by line. It is to preserve the parts that were worth carrying forward, then modernize the implementation so the platform is easier to operate, easier to extend, and more robust under real use.
What landed
Team visibility toggles in the gameboard
Server-driven team retrieval in the gameboard UI
Expanded admin controls
Why it matters
These emails are meant to stay technical and concrete. Instead of vague status notes, they will point to actual work that landed in the repository. The idea is to make each update useful both as a progress report and as a lightweight technical changelog.
Because this list is starting after development is already underway, the next emails will also cover earlier work that already happened in the repository. Those updates will be written in the same weekly format as if they had been sent at the time, so the archive reads like a consistent engineering timeline rather than beginning halfway through the project.
In practice, that means upcoming emails will describe past development in chronological order until the list catches up with the present. Once that happens, the list will continue on a normal weekly cadence.
Referenced commits
Follow along
Telegram channel: t.me/mapctf
Best regards,
MapCTF Development Updates