Not all calls to setUserAsActive are followed by a server-user-active message about gikopoi2

[iccanobif]

This is intentional: user-ping messages are sent not only on reconnects but on also on actions like moving the mouse or focusing poipoi's tab (with a 10 minutes debounce). server-user-active events are only useful when an inactive user becomes active again (and their avatar stops being transparent), and normally they do so by moving the mouse or doing other actions that send a user-ping message before performing other actions that can call setUserAsActive() (such as posting a message or moving their avatar). setUserAsActive() on the other hand also updates the date in user.lastAction so it performs a slightly different role.
Not sending unneeded server-user-active messages saves bandwidth: do you really want to send one to all clients for every single avatar movement or message that happens in a room?

The only situation where these assumptions might be not true is bots, the use of which is not supported (and kinda frowned upon).