Migrations in response to openode v3

[thenfour]

Openode v3 is changing how it handles websockets. Here's a short email conversation:

<me>
Hi, Do I understand correctly that websockets will no longer work in v3? If this is the case I will need to move to a different hosting provider which is a shame because your service has been great. Can you confirm this for me please?
thanks,

<openode>
They will still work. However the implementation should notice:

- Connections have a maximum duration of few minutes. And so your application should be able to reconnect automatically. Can be done automatically with socket.io for example.
- It's recommended to use something like redis in case multiple instances are run simultaneously. See an example here https://github.com/openode-io/openode-socketio-redis

See the note https://www.openode.io/docs/installation/legacy_upgrade.md "Notes for websites using web socket"

There was also a comment about persistent storage being "discouraged".

I believe significant work would be needed to support the new architecture, and these would be changes which are not very handy for 7jam. For example supporting a websocket refreshing constantly would mean there are potentially messages you missed (think note offs), which forces a full room refresh and all notes off. For every user, every few minutes.

So the search begins for a new provider which can support websockets.

[thenfour]

migration to uberspace completed