| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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
|
|
|
|
moving down was impossible
|
|
user was
|
|
|
|
bottom
|
|
|
|
|
|
|
|
empty and suggesting to send a message
|
|
but skipping the bottom line when selecting for better UX and selecting
while not in "SnapToBottom" will now start from the bottom of the
screen, not the last message
|
|
first char in a non-blank line crashes due to index out of bounds
|
|
|
|
|
