Closed
Bug 1311764
Opened 8 years ago
Closed 4 years ago
chrome.storage.sync: support syncing to self-hosted
Categories
(WebExtensions :: Storage, defect, P5)
WebExtensions
Storage
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1634615
People
(Reporter: glasserc, Unassigned)
References
Details
(Whiteboard: [storage]triaged)
Right now there are a bunch of places in the chrome.storage.sync code where we assume we're syncing to our "official" FxA servers. It would be good to loosen these assumptions and be more accepting of people who want to sync to their own services. I don't think all the requirements are clear yet. In particular, how do we handle crypto?
|
||
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: General
Priority: -- → P5
Whiteboard: [storage]triaged
|
|
||
Updated•7 years ago
|
Component: WebExtensions: General → WebExtensions: Storage
|
||
Updated•6 years ago
|
Product: Toolkit → WebExtensions
|
||
Comment 1•4 years ago
|
||
Switching from Kinto to the Sync backend means self-hosting will work the same as it does for the rest of Sync (we know our self-hosting story could always be better, but it's documented and folks can use it today)...so duping this out.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•