[Meta] Divergence from the spec

[turt2live]

This is a new issue for #2603

Known issues:

• Enforce Server-Server 4.1 PDU fields #3162 / We should check "depth" increases. (SYN-196) #1254
• Synapse creates invalid rooms as per stable/unstable spec #2644
• Federation event format returns a client event format #2604
• Incorrect HTTP Status returned on unknown/invalid access token #2602
• room_id missing from response body for rooms/{roomId}/join endpoint #2349 (fixed by Add room_id to the response of rooms/{roomId}/join #2986)
• Document default room creator PL matrix-spec-proposals#1081 (split from (Attempt to) Fix event authorization rules to allow first Power Levels events to be injected in the room matrix-spec-proposals#1052)
• Fix auth rules to allow first PL event matrix-spec-proposals#1080 (split from (Attempt to) Fix event authorization rules to allow first Power Levels events to be injected in the room matrix-spec-proposals#1052)
• Add status for unknown user's filter ID matrix-spec-proposals#1045
• m.direct not updated on the room creator's account when starting a private chat #4173
• Third Party Lookups: the returned protocol instance icons are not Matrix Content URIs #4175
• peeking doesn't work over federation #4236
• Appservice API does not recieve full unsigned content #4268
• Move /admin/whois back to /_matrix namespace #5280 - heavily arguable - see issue
• synapse requires unspecified user for m.login.password UI auth #5665

[turt2live]

ma1uta has also started a list at https://github.com/ma1uta/jeon/blob/master/SpecDiff.md

(source)

[richvdh]

I wonder if we need this issue, rather than just using the 'spec compliance' label (https://github.com/matrix-org/synapse/labels/spec%20compliance)

[clokep]

That seems easier to keep up-to-date. I added the "spec compliance" label to the issues in the description that are still open.