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
Improvement Request: Track Deep Linking vs. Credential Sharing in assetlinks.json
Currently, the custom metric for /.well-known/assetlinks.json at https://github.com/HTTPArchive/custom-metrics/blob/main/dist/well-known.js simply checks for the presence of the file. However, it would be valuable to gather more granular data about how websites are using this file, specifically regarding the types of relationships declared.
delegate_permission/common.handle_all_urls (Deep Linking): Indicates that the associated Android app can handle all URLs from the website, enabling deep linking functionality.
delegate_permission/common.get_login_creds (Credential Sharing): Allows the app to access the user's login credentials stored for the website.
Benefits of Tracking This Data:
Understand Deep Linking Adoption: Measure the prevalence of deep linking across the web and identify trends in its usage.
Monitor Credential Sharing Practices: Gain insights into how often websites allow apps to access user credentials, potentially highlighting security and privacy considerations.
Provide More Granular Reporting: Enable more detailed analysis and reporting in the Web Almanac, offering a deeper understanding of how websites utilize assetlinks.json.
Implementation Suggestion:
Modify the existing parseResponse function in well-known.js to specifically parse the assetlinks.json file and count the occurrences of each predefined relation string. This could be achieved by incorporating logic similar to the following:
fetch('/.well-known/assetlinks.json').then(response=>response.json()).then(data=>{letdeepLinkingCount=0;letcredentialSharingCount=0;data.forEach(statement=>{if(statement.relation==='delegate_permission/common.handle_all_urls'){deepLinkingCount++;}elseif(statement.relation==='delegate_permission/common.get_login_creds'){credentialSharingCount++;}});// Include these counts in the output JSON});
The text was updated successfully, but these errors were encountered:
Improvement Request: Track Deep Linking vs. Credential Sharing in
assetlinks.json
Currently, the custom metric for
/.well-known/assetlinks.json
at https://github.com/HTTPArchive/custom-metrics/blob/main/dist/well-known.js simply checks for the presence of the file. However, it would be valuable to gather more granular data about how websites are using this file, specifically regarding the types of relationships declared.Proposed Improvement:
Track the usage of the two predefined relation strings within the
assetlinks.json
file (as documented at https://developers.google.com/digital-asset-links/v1/relation-strings):delegate_permission/common.handle_all_urls
(Deep Linking): Indicates that the associated Android app can handle all URLs from the website, enabling deep linking functionality.delegate_permission/common.get_login_creds
(Credential Sharing): Allows the app to access the user's login credentials stored for the website.Benefits of Tracking This Data:
assetlinks.json
.Implementation Suggestion:
Modify the existing
parseResponse
function inwell-known.js
to specifically parse theassetlinks.json
file and count the occurrences of each predefined relation string. This could be achieved by incorporating logic similar to the following:The text was updated successfully, but these errors were encountered: