Jan Thurau

I cannot reproduce this (@valstu @juliankrispel @DenysPoliarush), if you can provide me with a sandbox / replit I'll have a look right away. Please move to #566 though, this issue...

@osamatanveer I've just added an example to the provider documentation. If you want to use multiplexing, you'll have to create the websocket separately from the provider (see https://tiptap.dev/hocuspocus/provider/examples#multiplexing).

hey @martindzejky, the parameters are passed as HTTP parameters, so it indeed doesn't work with multiplexing (as we share the connection, it would be using the same HTTP parameters for...

hey @georeith, HocuspocusProvider will still accept url and parameters if there is no websocketProvider passed, but then it will just create its own HOcuspocusProviderWebsocket. I implemented this for easier migration....

hmm, at first it makes sense, but what is the wrong / right order? Depending on the connection speed of the client or if client is offline (and online again),...

hey @georeith, as a workaround for now, I think you can use `provider.document.on('update')`, to directly subscribe to the Yjs update event (https://docs.yjs.dev/api/document-updates). I was actually surprised to realize that we...

hey @jordanstephens, thanks for this! Indeed, the current implementation may cause issues in certain scenarios. We're currently planning a bigger protocol change to make yjs subdocs and multiplexing possible, I'll...

hey @ralphiee22, thanks for reporting this! This is weird indeed. Can you share a few more information about your setup, are you using any extensions? How exactly do you generate...

yes! Should be fixed by #4661. Let us know if the issue persists.

Thanks @douira! I'm currently working on v3 and a fix for this will be included.