WebSockets seem to not work in mobile network aside from 4G (and H?)

Current version of firefox seems to not support pointer events. (it's supposed to be compatible)

Clipboard and Keyboard input.

Low priority: Current version of Safari seems to not support pointer events. (was never targeted)

Invalid operation on server should not happen. That said it can and the connection shouldn't hang because of that (later requests don't work).

This is easily seen with images since they're temporary way longer (need to wait API upload and normal send). Moving a figure while it is still temporary disconnects a Client (socket gets stuck) because it's an invalid operation on server (trying to move a figure that doesn't exist).

Currently using git subtree for deployment, this file is unnecessary

Seems to work if using server on localhost.

Using deployed server client receives no notification about connection closing.

In hotfix/1.0.1 a performance patch was made. This performance patch was made trying to fix a bug where a user that was drawing a line would lose the origin to draw point visualization when receiving another line from WebSockets and the visualization of the pen color turned into the received line color.

This happened because receiving a line from WS induced a redraw of the board. Since it does not redraw anymore the bug seemed to be fixed. The problem is that most of the other WS operations cause a redraw in the board and the same bug still persists there (and there is no other option than redrawing).