| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
style guidelines, we now have tabs
|
| |
|
|
|
|
| |
clarity
|
|
|
|
| |
for consistency.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
underlying socket (more useful this way)
|
| |
|
|\ |
|
| |
| |
| |
| | |
clients, re-visit some time down the line
|
| |
| |
| |
| | |
want to use
|
| | |
|
| |
| |
| |
| | |
traceback with no LuaSec)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
with libevent (no packet merging)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
connection of type 'ssl'
|
| | |
|
| |
| |
| |
| | |
message
|
| | |
|
| | |
|
| |
| |
| |
| | |
- all connections support TLS
|
| | |
|
| | |
|
| |
| |
| |
| | |
outgoing s2s connections not being encrypted)
|
| | |
|
| |
| |
| |
| | |
functions - passing a sslctx now indicates you want to use SSL from the start
|
| |
| |
| |
| | |
role lists and presence broadcasts after role changes (thanks teo)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
port multiplexing
|
|\ \ |
|