| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
stored at the other end.
|
|
|
|
| |
other side
|
| |
|
|
|
|
| |
encoded message into the queue, it's still a hard slog, but there's light at the end of the tunnel - "a message is ready and waiting to be delivered".
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
of known sites
|
| |
|
| |
|
| |
|
|
|
|
| |
$global_perms for edge cases
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
aren't connected with
|
| |
|
| |
|
| |
|
|
|
|
| |
I've now got a plan
|
|
|
|
| |
structures
|
|
|
|
| |
friends, sorry, but red won't talk to you. This snake is dead.
|
| |
|
|
|
|
| |
plugging away at them
|
| |
|
| |
|
| |
|
|
|
|
| |
communications for channel meta info, don't yet know if it's working
|
| |
|
| |
|
| |
|
|
|
|
| |
permission synchronisation. After this, messaging should be a piece of cake.
|
|
|
|
| |
refresh their info
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(block,hide,archive,etc.)
|
| |
|
| |
|