Idea: persist liveview state across reconnections

Fly did an article that uses client-side session storage for this purpose.

Otherwise, my feeling is that whenever possible, state should always be recreateable via the db and more notably the URL—many neglect the latter. I’m even talking things like tabs that may already have the data loaded but hidden. Just giver ‘er a good ol’ window.history.pushState. But I will now step off my soapbox :slight_smile: