> perhaps we could get away with defining “a standard to push updates to a resource’s state” over SSE?
For the record, this is exactly what the Mercure protocol does and it’s been serving successfully hundreds of websites in production for years: https://mercure.rocks/spec
I’m working on a "final" version of the spec (https://github.com/dunglas/mercure/pull/959), then plan to propose it as an RFC on the "independent submissions stream". (I submitted drafts several times on this group, but despite the protocols wide adoption in the wild, it never gained traction on list, so an independent submission is probably more appropriate).
Here is a comparison between Mercure, Braid and PREP: https://dunglas.dev/2023/11/mercure-braid-prep-news-about-subscribing-to-http-resource-updates/
Best,