Slava
Slava
Unfortunately, no :(
Still the issue
@dmonad Don't know why the issue is marked with `wontfix` automatically. Hope it doesn't mean that it goes directly to a trash bin 😁
It could be a problem to distinguish between "your own" ids and "someone else's" ids in the awareness update handler. Could even require protocol changes. But I'm just wondering why...
Hey! Is there any way we can help with it?
@dmonad ping, very annoying issue for us, sorry
Hey! Is there any way we can help with it?
@dmonad could you please give any comment on this?
> @mifopen did you ever get this sorted? running into same issue I mixed two issues into one, so let me explain our workarounds one by one. The one described...
Here's the patch to introduce resurrected nodes ``` diff --git a/node_modules/y-protocols/awareness.js b/node_modules/y-protocols/awareness.js index 8f9ae94..b4a4603 100644 --- a/node_modules/y-protocols/awareness.js +++ b/node_modules/y-protocols/awareness.js @@ -10,7 +10,7 @@ import { Observable } from 'lib0/observable' import...