Currently only the responses from the site are cached and thus get used to load messages quickly.
Given the coming api and as a general improvment, it would make sense to directly save messages and not even make the requests in the first place. This would mean that the messages would end up locally, would persist for the user and the application would only check if new ones (since the last known message) arrived.
This has been long outstanding but has been in the application for some time. I just wanted to make sure it works (which it does ok for me). Closing this as it's coming with the 1.0 release.
Currently only the responses from the site are cached and thus get used to load messages quickly.
Given the coming api and as a general improvment, it would make sense to directly save messages and not even make the requests in the first place. This would mean that the messages would end up locally, would persist for the user and the application would only check if new ones (since the last known message) arrived.