It gets a little off-topic, but I guess you can split this thread if needed, but…
If the API will be read-only if the servers are down, does that mean that:
- if you have a (non-planned) server outage, saving of data via that API will also fail?
- (basically the same question:) Does that mean Firefox does not cache the data locally before uploading it to this API?
You know, I am asking 1 especially, because you never know what incidents may happen. And you’ve such a one recently, #armagadd-on-2.0. So – just in case – you may want to limit the damage when that server is down.
- Also related to this: Will
browser.storage.sync.set() reject the Promise, if it is down/read-only?
That could be kinda bad if your add-on then shows an error – without further explanation. (AFAIK my ones should do so.) I really have not implemented a local fallback or so, I thought the API/Firefox already does so.
So as a proposal: Why not cache the changes locally that are written, to that API and then upload the changes when the server is back online?
This would actually help against a “server is down” scenario.
Thinking of this, actually, I can likewise be offline at some time, would this behave in the same way then?