Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Allow for make_awaitable's return value to be re-used. (#8261) | Patrick Cloke | 2020-09-08 | 1 | -1/+1 |
| | |||||
* | Convert federation client to async/await. (#7975) | Patrick Cloke | 2020-07-30 | 1 | -5/+5 |
| | |||||
* | Convert state resolution to async/await (#7942) | Patrick Cloke | 2020-07-24 | 1 | -12/+7 |
| | |||||
* | Add option to enable encryption by default for new rooms (#7639) | Andrew Morgan | 2020-06-10 | 1 | -1/+5 |
| | | | | | | | | | Fixes https://github.com/matrix-org/synapse/issues/2431 Adds config option `encryption_enabled_by_default_for_room_type`, which determines whether encryption should be enabled with the default encryption algorithm in private or public rooms upon creation. Whether the room is private or public is decided based upon the room creation preset that is used. Part of this PR is also pulling out all of the individual instances of `m.megolm.v1.aes-sha2` into a constant variable to eliminate typos ala https://github.com/matrix-org/synapse/pull/7637 Based on #7637 | ||||
* | Fix encryption algorithm typos in tests/comments (#7637) | Andrew Morgan | 2020-06-04 | 1 | -1/+1 |
| | | | | | | | | @uhoreg has confirmed these were both typos. They are only in comments and tests though, rather than anything critical. Introduced in: * https://github.com/matrix-org/synapse/pull/7157 * https://github.com/matrix-org/synapse/pull/5726 | ||||
* | Fix device list update stream ids going backward (#7158) | Richard van der Hoff | 2020-04-03 | 1 | -0/+6 |
| | | | | | | | | | | | | | | | | Occasionally we could get a federation device list update transaction which looked like: ``` [ {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D2', 'prev_id': [], 'stream_id': 12, 'deleted': True}}, {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D1', 'prev_id': [12], 'stream_id': 11, 'deleted': True}}, {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D3', 'prev_id': [11], 'stream_id': 13, 'deleted': True}} ] ``` Having `stream_ids` which are lower than `prev_ids` looks odd. It might work (I'm not actually sure), but in any case it doesn't seem like a reasonable thing to expect other implementations to support. | ||||
* | Rewrite prune_old_outbound_device_pokes for efficiency (#7159) | Richard van der Hoff | 2020-03-30 | 1 | -0/+92 |
| | | | | make sure we clear out all but one update for the user | ||||
* | Add tests for outbound device pokes | Richard van der Hoff | 2020-03-27 | 1 | -3/+300 |
| | |||||
* | Implementation of MSC2314 (#6176) | Amber Brown | 2019-11-28 | 1 | -1/+3 |
| | |||||
* | Run Black. (#5482) | Amber Brown | 2019-06-20 | 1 | -24/+24 |
| | |||||
* | Run Black on the tests again (#5170) | Amber Brown | 2019-05-10 | 1 | -47/+66 |
| | |||||
* | Batch up outgoing read-receipts to reduce federation traffic. (#4890) | Richard van der Hoff | 2019-03-20 | 1 | -0/+128 |
Rate-limit outgoing read-receipts as per #4730. |