| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
keeping track of position
|
|
|
|
are broken
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
runtime the server.key instead of containing it in the server's
executable using go embed
|
|
|
|
|
|
also this is bad practice to modify a migration (they should be
immutable) but didn't want to have one with syntax errors and I will be
refactoring and splitting this one huge migration into multiple separate
migrations later on
|
|
that network
|
|
|
|
different locations, fixed the issue where it'd only work for the first
time by checking if the addresses match before remove the session
|
|
user ID, note that there seems to be a weird thing where if 2 clients
are from the same IP, the disconnected client will just reconnect to the
new client's socket, so they will both use the same connection for
communication
|
|
|
|
networks and members work
|
|
|
|
|
|
|
|
|
|
|
|
screen is not filled with messages
|
|
|