- Apr 12, 2017
-
-
Erik Johnston authored
Reduce federation replication traffic
-
Paul Evans authored
Add a counter metric for successfully-sent transactions
-
Erik Johnston authored
Dedupe KeyedEdu and Devices federation repl traffic
-
Erik Johnston authored
-
Erik Johnston authored
Remove HTTP replication APIs
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
Fix getting latest device IP for user with no devices
-
- Apr 11, 2017
-
-
Paul "LeoNerd" Evans authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
- Apr 10, 2017
-
-
Matthew Hodgson authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
This is mainly done by moving the calculation of where to send presence updates from the presence handler to the transaction queue, so we only need to send the presence event (and not the destinations) across the replication connection. Before we were duplicating by sending the full state across once per destination.
-
Erik Johnston authored
-
David Baker authored
Support authenticated SMTP
-
Erik Johnston authored
Fix up federation SendQueue and document types
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
- Apr 07, 2017
-
-
Richard van der Hoff authored
When we do an invite rejection, save the signed leave event to the db
-
Richard van der Hoff authored
During a rejection of an invite received over federation, we ask a remote server to make us a `leave` event, then sign it, then send that with `send_leave`. We were saving the *unsigned* version of the event (which has a different event id to the signed version) to our db (and sending it to the clients), whereas other servers in the room will have seen the *signed* version. We're not aware of any actual problems that caused, except that it makes the database confusing to look at and generally leaves the room in a weird state.
-