properly remove per-device push rules

[ara4n]

the APIs are still hanging around, which confuses people. we should add them back to the spec deliberately in future

[richvdh]

@ara4n: which APIs does this refer to specifically?

[richvdh]

synapse returns an undocumented devices property in response to GET /_matrix/client/r0/pushrules/, so maybe that is what this is referring to? but removing that would be a synapse bug rather than a spec one.

[richvdh]

I've opened matrix-org/synapse#12482 to track updating the Synapse API.

As it concerns the spec, device scopes are mentioned in a couple of places: https://spec.matrix.org/v1.2/client-server-api/#get_matrixclientv3pushrulesscopekindruleidactions and https://spec.matrix.org/v1.2/client-server-api/#get_matrixclientv3pushrulesscopekindruleidenabled, which both say:

scope: Required: Either global or device/<profile_tag> to specify global rules or device rules for the given profile_tag.

Synapse returns a 400 M_UNRECOGNIZED for any such request where scope is not global.

[frederikb96]

Do I understand correctly, that the per device push rules are going to be removed and that there will be no way to have different notification profiles for different devices?

[richvdh]

Per-device push rules have never been supported. There have been some ideas for supporting per-device notification profiles in Matrix, but it won't be based on push rules.