| Age | Commit message (Collapse) | Author |
|---|
|
so the client can use it to persist notifications
|
|
get completed even if the user disconnects, this is not ideal and should
be reworked in the future
|
|
the user has access to the frequency, because it is needed for the
is_admin ping type but also to prevent the case where someone was an
admin, got demoted and can now monitor when new messages are sent there
|
|
fixes the client to use this new system
|
|
and sends the info to the client when it connects
|
|
|
|
|
|
will cause a desync and crash the server and show an invalid network on
the client side
|
|
banning
|
|
|
|
is nil
|
|
|
|
|
|
|
|
each others messages (to save some time having to query the sender ID to
see if he's an admin)
|
|
person who is kicking and not to the person who was kicked
|
|
|
|
|
|
|
|
online users even if they didn't have access
|
|
|
|
side
|
|
frequencies even if you were a normal user and not an admin
|
|
permission 3 would be valid even though it's not
|
|
|
|
|
|
able to read it and also fixed some other bugs and implemented
propagation for members joining/leavings servers
|
|
|
|
|
|
keeping track of position
|
|
|
|
are broken
|
|
|
|
|
|
|
|
|
|
|
|
|
|
runtime the server.key instead of containing it in the server's
executable using go embed
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on the client
|
