Offline mode

[NULLx76]

Is your feature request related to a problem? Please describe.
Semi related to #45 , as this feature request will likely incorporate that issue.

Also related to #97 , however that likely will never be fixed as it is incompatible with our current real time editing feature.

Describe the solution you'd like
It would be nice if CSHub would work offline, with of course limited functionality. Just viewing posts should be good enough, if we really want to we could make it so that things like favouriting would still work and were "queued up" for when a connection becomes available again.

Additional context
The easiest way to achieve this is probably by using the service worker, Google has good documentation on how to achieve this, which we can make use of.

[RobbinBaauw]

Yeah the odd thing is, it should already work: we use the service worker and a lot of posts are cached (upon opening), though we might need to do more aggresive caching

Offline editing won't happen indeed, with the current realtime editing it's nearly impossible to do that correctly (as in, you would get merge problems, the current setup would allow for offline editing though).

And I think queueing requests shouldn't be that hard, we could make some store for it which stores the requests to be made

[NULLx76]

In that case consider this a bug report

…

On Thu, 28 Feb 2019, 09:15 Robbin Baauw, ***@***.***> wrote: Yeah the odd thing is, it should already work: we use the service working and a lot of posts are cached (though we might need to more aggresive caching) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#131 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABubLmSea1F9joSQwk8jhs709lK0-Bjaks5vR5APgaJpZM4bWO2B> .

[RobbinBaauw]

We could do this by taking the cache if no response within an x amount of seconds

[RobbinBaauw]

We should actually use a cache first approach!