Consider Rewriting Backend in Tungstenite

[Glacier150]

We need to totally overhaul the backend, the ws library is insufferable to work with. We need to burn the midnight oil. Tungstenite is the way. We need to lock down the firewall, these hackers these days. We need to prevent inspect element hacking.

[mariano-f-r]

I do agree that Tungstenite would provide us with much more low-level control over incoming Websocket connection. I will try rerunning the website using it to see how the developer experience changes.

[mariano-f-r]

So far, a basic proof of concept is working. However, due to separations of concerns, and the fact that Tungstenite only does WebSockets, we will need to create a separate frontend service (React SPA, etc) to use the app.

[mariano-f-r]

This means that #44 is now tantamount for this migration to be completed.

[mariano-f-r]

Also, said proof of concept only works locally so far. Once we start nearing a date for a deployment of the new backend, then I will start adding the Shuttle IaaC boilerplate.