silverwind

Can maybe take a look at ui in a few days.

> I agree with lunny, this is more complex than I imagined but hey, if it works that's awesome. Do we really have 2 way communication here though? Maybe SSE...

I think single-instance support is fine intially. I previously proposed a notification mechanism that works in multi-instance as well: - The triggering node (e.g. the one that did the database...

Running into this JS error in Firefox currently when testing the branch:

Trying to fix the JS...

htmx will not be the final websocket solution, that will be in custom JS code in a `SharedWorker`. But I do think it's important we get the backend side of...

Needs a `make tidy`. PS: I need to read through above but I'm generally okay with everything to finally get this websocket in so we can also start removing the...

And needs a `make fmt` 😆

> when the client disconnects, the subscription should be removed This will work for main thread websocket that reconnects on every page load, but once we move it to SharedWorker,...

> When using the url as topic, I would need to publish to all urls a specific event could possibly be interesting for. So ie an issue name change would...