Tyler Bloom
## Unmet Need: Currently, a `Gathering` will live forever after it is spawned. This is not ideal as it will cause memory exhaustion. ## Solution: The `Gathering` actor is the...
## Unmet Need: The `SquireClient` should be able to track user session data, reauth as needed, login, etc without locking. ## Solution: This should be accomplished with an actor, similar...
## Unmet Need: As mentioned in #149 , we need the ability to broadcast session changes. This includes session expiry, deletion, and promotion. ## Solution: The sessions maintained by the...
## Unmet Need: Session promotion is an internal mechanism of the backend. When a guest authenticates as a user, they should be able to continue to use their session. The...
## Unmet Need: Currently, there is no way to reauthenticate guest sessions or track expired guest sessions. Guest sessions have the same set of features as user sessions.
## Unmet Need: In order to display the amount of time left in the round to a whole room, we should have a pop-out tab that counts down the amount...
## Unmet Need: Currently, there are only "simple" tournament tabs in the web frontend. This works for now, but more specialized tabs will be needed in the future. Very roughly,...
## Unmet Need: In order to give TOs access to actions like rolling back a tournament (a feature of the `TournamentManager`), we need a separate tab for them to look...
## Unmet Need: SquireWeb needs a page for creating and submitting a new user account. This should include email and password as well as all the components of the squire...
## Unmet Need: The SquireWeb needs a front landing page. This should include a short bit about what Squire is, links to our Discord and GitHub, and paths to either...