Goal: FuzzJudge as a Spec

[sunsetkookaburra]

FuzzJudge should really allow for many alternative implementations, around a core (simple) protocol and ideas.

Principles (no particular order yet)

1. Front-matter in Markdown should only be for concepts that cannot be conveyed in the document itself. Hence,
   • Title, Icon and Brief can be derived from the text
2. The server side should allow for any program to run
   • Any theoretical overhead with spinning up binaries can be optimised away with tiny binaries communicating with an execution server; or,
   • The server itself can intelligently parse the exec string and preload executable code
3. The client should still be able to interact with the server, even if using the most basic means possible
   • API listing pages should exist, and be human interactive (HTML or plain text)
   • A user should be able to use the site (in theory) with a telnet-like client.

Goals

1. ProgSoc can host a variety of different backend implementations, and a variety of front-end implementations for users to try and improve upon - as a part of society project work,
2. The software can continue to be useful for programming competitions for many years.

Analogies

1. FuzzJudge should provide a basic interface like GitWeb is to Git, and be the protocol and file structure too much like Git.

[sebasptsch]

I think that fuzzjudge has diverged away from this a bit with moving to a more documented API layer but at the same time by moving to graphql it's easier than ever to create a new client.