Eric Eastwood 2d89c66b88 Switch to `chunk` events so we can auth via power_levels (MSC2716) (#10432) ... Previously, we were using `content.chunk_id` to connect one chunk to another. But these events can be from any `sender` and we can't tell who should be able to send historical events. We know we only want the application service to do it but these events have the sender of a real historical message, not the application service user ID as the sender. Other federated homeservers also have no indicator which senders are an application service on the originating homeserver. So we want to auth all of the MSC2716 events via power_levels and have them be sent by the application service with proper PL levels in the room.		2021-07-21 10:29:57 +00:00
..
.gitignore	Correct attrs package name in requirements (#3492)	2018-07-07 10:46:59 +10:00
10283.feature	MSC3244 room capabilities implementation (#10283)	2021-07-20 12:59:23 +01:00
10432.misc	Switch to `chunk` events so we can auth via power_levels (MSC2716) (#10432)	2021-07-21 10:29:57 +00:00