The offline version still needs internet to send new posts but it saves drafts so you can send them later. Not sure what you mean by synchronizing reads against

The offline version still needs internet to send new posts but it saves drafts so you can send them later. Not sure what you mean by synchronizing reads against writes; reads only ever occur on the copy in S3, and writes only directly occur on the copy in the linux server. In theory it is possible for a read to occur while S3 is in the middle of updating the db files (not sure if they update multiple files atomically) but it would be a rare problem, and probably could be automatically dealt with by rerunning the request after a short wait.