| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
precise type of content until the mechanism is extended to other types in the future
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
content types
|
| |
|
| |
|
| |
|
|
|
|
| |
for protocol 'friend requests' which aren't likely to swamp the delivery system). Remove it from the queue_delivery function which was too late to do anything.
|
| |
|
| |
|
| |
|
|
|
|
| |
this is not backward compatible and older sites will see some incorrect delivery reports from newer sites until the next upgrade; as their systems will not know how to read the ecnrypted final reports.
|
| |
|
| |
|
| |
|
|
|
|
| |
the delivery engine and split off site records from channel records.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
singly in separate processes - not yet tested
|
| |
|
| |
|
|
|
|
| |
0 in DB
|