| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
expanded later
|
|
writes to fully proccess
|
|
and show their names properly in messages
|
|
instead of "u")
|
|
|
|
|
|
correct
|
|
the signal already open, it will be added as the first signal
|
|
"signal" and it's variants as this is the new terminology for "user
signals" which are direct messages between 2 users
|
|
so the client can use it to persist notifications
|
|
|
|
got to the top message but then more messages have been added
|
|
new messages in the frequency/receiver
|
|
components have updated instead of before so the view will reflect the
update in case any of the updates change the notifications
|
|
and sends the info to the client when it connects
|
|
|
|
|
|
frequency, similar to how discord works
|
|
user (which can be either receiver or sender)
|
|
in the user signals
|
|
|
|
will cause a desync and crash the server and show an invalid network on
the client side
|
|
|
|
|
|
|
|
side
|
|
for frequency swapping, this will add delay when swapping frequencies
but it prevents issues when the swapping packet gets received as part of
the propagation
|
|
|
|
|
|
|
|
|
|
|
|
user was
|
|
frequency" per network
|
|
|
|
|
|
|
|
|
