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 }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
We should be able to use the new local processor in service-digitalassetlinks and avoid Google API calls for TWAs. We lose whatever caching is done by the servers but gain improved privacy.
data-sync-user
changed the title
Resolve Digital Asset Links without using Google API
FNX3-21939 ⁃ Resolve Digital Asset Links without using Google API
Aug 11, 2020
data-sync-user
changed the title
FNX3-21939 ⁃ Resolve Digital Asset Links without using Google API
FNX-14010 ⁃ Resolve Digital Asset Links without using Google API
Aug 11, 2020
data-sync-user
changed the title
FNX-14010 ⁃ Resolve Digital Asset Links without using Google API
FNX2-15515 ⁃ Resolve Digital Asset Links without using Google API
Aug 11, 2020
kbrosnan
changed the title
FNX2-15515 ⁃ Resolve Digital Asset Links without using Google API
Resolve Digital Asset Links without using Google API
Aug 28, 2020
We should be able to use the new local processor in
service-digitalassetlinks
and avoid Google API calls for TWAs. We lose whatever caching is done by the servers but gain improved privacy.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: