Commit graph

15 commits

Author SHA1 Message Date
Lambda
c9a435ab34 Renamed MSC3575 -> MSC4186, remove obsolete config 2025-08-10 19:37:15 +00:00
Lambda
b4f6c88e57 MSC3575: make known rooms global per connection rather than per list 2025-08-10 19:37:14 +00:00
Lambda
a72ff4f6e6 MSC3575: avoid double-processing rooms in case of overlapping ranges 2025-08-10 19:36:31 +00:00
Lambda
ede39370a4 MSC3575: allow empty conn_id 2025-08-10 19:17:45 +00:00
Lambda
64ad940bad MSC3575: remove sticky parameters 2025-08-10 19:17:41 +00:00
Lambda
991f1e2c0d MSC3575: factor out ConnectionKey 2025-08-10 17:25:47 +00:00
Lambda
3bbee92db4 MSC3575: remove useless Ok-wrapping 2025-08-10 16:56:57 +00:00
Lambda
e75fe7b75a MSC3575: factor out TodoRoom 2025-08-10 11:41:24 +00:00
Lambda
6d4f165629 MSC3575: use explicit loop for ops creation 2025-08-10 11:27:02 +00:00
Lambda
dd705a2bb2 Revert "Remove support for MSC3575 (sliding sync)"
This reverts commit d87848b9a6.
2025-08-10 10:49:50 +00:00
Jonas Platte
d87848b9a6
Remove support for MSC3575 (sliding sync)
Co-authored-by: Olivia Lee <olivia@computer.surgery>
2025-08-08 22:24:56 +02:00
Olivia Lee
fb4d168921 fix new lints from clippy 0.1.85 2025-08-06 12:27:45 -07:00
Olivia Lee
b82458a460
use event content in account_data service api instead of full events
This eliminates the possibility of passing an event that has a
mismatching type, reducing the space of possible invalid states.
2025-06-02 11:07:21 -07:00
Olivia Lee
66210bc32d
separate account_data service methods for room vs global events
Previously we were mashing everything together as RoomAccountDataEvent,
even the global events. This technically worked, because of the hidden
custom fields on the ruma event types, but it's confusing and easy to
mess up. Separate methods with appropriate types are preferable.
2025-06-02 11:07:21 -07:00
Lambda
79783ebe56 sync: split into separate files 2024-12-11 17:38:49 +00:00