matrix-spec-proposals MSC4174: Web push

rendered

Client implementation: synapse impl: https://github.com/element-hq/synapse/pull/17987 updated hydrogen impl: https://github.com/element-hq/hydrogen-web/pull/1201

Note: in addition to this MSC, it would be very useful to have MSC4173, if someone is interested in implementing this MSC as well

Aug 01 '24 15:08 p1gp1g

Thank you for your feedback @clokep, I'm updated the proposal soon

Aug 07 '24 10:08 p1gp1g

Client implementation: https://github.com/p1gp1g/hydrogen-web/commit/e7cc4880b0d294a989b757aee0c17abee5601aa7

Nov 21 '24 08:11 p1gp1g

synapse impl: https://github.com/element-hq/synapse/pull/17987 updated hydrogen impl: https://github.com/element-hq/hydrogen-web/pull/1201

Dec 02 '24 22:12 MatMaul

Implementations seem to implement what's described in the MSC, so removing the needs-checking label

Jan 21 '25 16:01 tulir

We have introduced a handshake to validate a push subscription on the WEBPUSH IMAP extension. Validating the subscription is easy to implement and reduces a lot the risk of a bad actor registering a lot of non-webpush endpoint in order to use it as a DDOS amplification. I think we should introduce it here as well

Mar 24 '25 15:03 p1gp1g

I've added the validation token to the MSC

May 26 '25 12:05 p1gp1g

Upvoting this

May 30 '25 15:05 warioishere

Last but not least, the title "webpush push kind" sounded a bit like a typo and one has to read it twice to make sense of it. Perhaps rather "Extend Notification pusher to an optional "webpush"" or something similar. "push kind" is kind of very insidery if you already know the spec.

Jun 01 '25 10:06 spaetz

Thanks @spaetz for your suggestions and review, I've somehow forgotten to get back to them.

I've updated the title to something more simple: web push, and I think I've responded to all your comments

Nov 15 '25 20:11 p1gp1g

@p1gp1g think you have more typos xd

Nov 17 '25 11:11 Fuseteam