- Agreed
- Yeah this is more a potential optimization, the very message queue of the GenServer is an excellent approach for most cases, agree as well
initial state that could be persisted on the client between sessions on IndexDB or localstorage.
Great, that’s exactly what I’ve been doing to hydrate LiveSocket as mentioned above, but thinking about it if you keep the store saved and stored(duh) at the server, related to a user_id, then the client only needs to know that user_id and it becomes cheaper to kickstart it all to the latest state
