You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Get rid of origin if possible - less config, easier data migration, moving server between domains #749
Atomic Data uses a lot of URLs. The server needs to be aware where it is hosted in order to provide valid JSON-AD.
However, this poses a problem: Changes to port or schema (using HTTPS or HTTP) or domain causes identities to no longer resolve.
This requires users to migrate their data manually (e.g. export JSON-AD, rename all domains).
It would probably better to use a different type of ID internally. For example, instead of storing local identifiers as https://domain/ we do something likelocal:.
Whenever we serialise any resource, we need to convert it using the server_url.
We need to consider all the places where we use these URLs:
I like the idea of introducing atomic:// URL scheme and use current tauri app to register atomic:// schema locally, with an atomic server internally translating URLs to relevant FQDN + path.
To illustrate our discussion check out how ripgrep handles URLs schemas for different text editors: Printer
Closing as consolidated into #1139 during the requested backlog cleanup. The remaining requirements from this issue are preserved in a new comment on #1139. This is not a claim that every requested behavior is implemented; please continue current work in that tracker. The issue and discussion remain available for reference.
Activity
AlexMikhalev commentedon Dec 20, 2023
I like the idea of introducing atomic:// URL scheme and use current tauri app to register atomic:// schema locally, with an atomic server internally translating URLs to relevant FQDN + path.
To illustrate our discussion check out how ripgrep handles URLs schemas for different text editors: Printer
joepio commentedon Sep 12, 2026
Closing as consolidated into #1139 during the requested backlog cleanup. The remaining requirements from this issue are preserved in a new comment on #1139. This is not a claim that every requested behavior is implemented; please continue current work in that tracker. The issue and discussion remain available for reference.