| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to re-accept the TOS, users can delete the cache if they wish to review
it
|
|
dir to store things like device ID and TOS hashes (only storing device
ID currently)
|
|
|
|
screen model, still missing accept/decline and authentication
|
|
authentication separation between API calls, actually authentication
(nonce, and verification) is not implemented yet
|
|
refactored some log statements
|
|
single message
|
|
|
|
expanded later
|
|
writes to fully proccess
|
|
|
|
and show their names properly in messages
|
|
instead of "u")
|
|
|
|
|
|
|
|
|
|
don't get darkened)
|
|
|
|
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
|
|
|
|
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
|
|
|
|
and not save if it takes longer than 1 second
|
|
in the user signals
|
|
|
|
|
|
|
|
|
|
banning
|
|
|
|
|
|
|
|
|
|
|
|
the server
|
|
|
|
|
|
with chat messages
|
|
|
