Proper use of websockets
Made the issue as I had some ideas that might help with logical implementation and wanted to write them down
- Hook websocket to our fetchers, as in when fetcher is created, WS is connected/subscribed, and same for when fetchers are removed. This requires some more work for every request that has a websocket alternative, I'm mostly thinking of chat messages, timelines and notifications.
- Keep state of websocket connection in fetchers so that each fetcher can have some idea of if WS is working or not
- Keep the interval going even WS is active, but just skip doing the actual fetch if our connection is fine so that it automatically uses traditional polling whenever connection is not active