3 ms·
No, it's just been a painful problem to solve. If you're interested, you can see the massive discussion around it at https://github.com/matrix-org/matrix-spec-
by Arathorn 4y ago
No, it's just been a painful problem to solve. If you're interested, you can see the massive discussion around it at https://github.com/matrix-org/matrix-spec-proposals/pull/2285 https://github.com/matrix-org/matrix-spec-proposals/pull/228.... The implementations have been around for a while, and as it happens we got to consensus on the spec discussion yesterday, and the PRs to enable it by default in Element Web and Synapse landed an hour ago:
https://github.com/matrix-org/matrix-js-sdk/pull/2524 https://github.com/matrix-org/matrix-js-sdk/pull/2524
https://github.com/vector-im/element-web/pull/22242 https://github.com/vector-im/element-web/pull/22242
https://github.com/matrix-org/synapse/pull/13273 https://github.com/matrix-org/synapse/pull/13273
- your_challenger 4y agoTalk about a bleeding edge feature
- LightHugger 4y agoI'm glad it's happening in that case. Last i had checked a contributor had locked the issue discussion a year or more ago after losing an argument about an interim stopgap being useful to solve the immediate privacy issue. A story as old as the internet itself, that one. So at least that one contributor did not care about interim privacy which gives the obvious "we don't care" signal when not contradicted by anyone else.