Farhan Y.
Farhan Y.
**update** 1. caching awareness users for 1min to make user availability smooth to others. 2. reducing online idle time from 2min to 12sec. hence, if you leave the tab, you'll...
@stuartc I think I understand clearly what you mean. So if I'm getting it right. we have to do. 1. `lastSeen` - for keeping ydoc awareness alive 2. `lastState` -...
@stuartc I've opened a new PR around this. separates the log for keeping ydoc alive and the one for updating the last activity. Works very fine so far. with smoothing...
For the consolidation of multiple tabs open by a user. I already have that in place but I've changed how the priority is picked in the other PR. `lastActivity` >...
with this said. on #4053 1. user last activity is tracked realtime `active` | `away`. 2. we keep our 10s `lastSeen` updates to ydoc. 3. to battle possible throttling. when...
Closing this PR soon in favour of #4053
We have 3 states. - **active** (a user who's actively issuing inputs while on the page. eg. mouse movements and key presses) - **inactive** (a user who's on the page...
Since the human Interface to a computer is just a mouse and keyboard. we'll track those two for active users
### Additional Context Just sharing x,y positions will obviously not work. will have to normalize the position values with zoom level and pan to be able to transmit the real...
Showing the actual mouse positions wouldn't be an easy task. I suggest we show other users actions based on their selection. eg. user A selects node "Transform data". then user...