forked from MirrorHub/synapse
2d89c66b88
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.
1 line
91 B
Text
1 line
91 B
Text
Connect historical chunks together with chunk events instead of a content field (MSC2716).
|