Cache latest message history

(#1000) Feature Under consideration messaging performance

Problem

When the main fluxer server goes down, the entire system is unusable. Currently, this is a noticeable issue, and even after the infra is improved, will be an issue both for the main server and self hosted instances.

Proposed solution

Automatically caching the latest messages in communities you access would allow you to still be able to read the last messages before it went down. Of course you wont be able to do anything, but it'll significantly improve the inconveniences caused by a server going down.

Notes (optional)

This is extremely similar to #975 but is for a completely different situation

2 comments

Sign in with Fluxer to comment and vote.
Comment by @ZackMercury
RexSystem 1 vote originally by @ZackMercury on GitHub 1 reply
Please rename the topic into something like "Do not throw the user into Loading page upon connectivity issues/errors". Things don't need to be cached to not cause inconveniences. It's enough to just preserve the app state.
Comment by @ASuspiciousRat
RexSystem 1 vote originally by @ASuspiciousRat on GitHub OP
This suggestion is for if the app is opened during an issue. The app can't be preserved without caching if it hasn't been opened since last boot.