Tyler Bloom
## Unmet Need: The Squire model for communication between clients and the backend requires that tournament operations be entirely deterministic. While there has been a good deal of effort put...
## Unmet Need: Currently, there is no endpoint for creating a Squire account. We need an endpoint for folks to create an account with. This should take their to-be-created account...
## Unmet Need: Currently, a round's timer starts when it is created. However, most TOs want match times to start when they say and it should be uniform. ## Solution:...
## Unmet Need: When a user submits a sync request for a tournament, we must verify that the changes that they are submitting for that tournament are allowed to be...
## Unmet Need: Currently, the types used in tournament sync, namely `OpSlice`, hold vectors of operations. This makes sense since they could, at any point, run into a sync issue...
The SquireCore server needs to be selective with who can see deck information. Most tournaments that require deck reg are closed decklist tournaments. Tournaments should store if they are open...
### Description The SquireCore server should expose APIs for pairing folks without needing to run the tournament through Squire. This would be a rough wrapper around the pairing algorithm functions....
Oh my God, why haven't I done this yet?
Decks are a common thing in larger tournaments. `SquireLib` should support some method of tracking and recommending deck checks.
It would be cool to have an actual application that you can run in a terminal in order to interact with the blog. The visual design would be identical to...