It is not a mobile app. You export your data from Google (thanks GDPR!), and filter out personally identifiable data points before submitting. We also let you know exactly who is about to use your donated data (we only allow academic researchers to have access), and give you advance notice so you can delete it if you don’t want your data to be used in a particular project.
We are MIT licensed and are figuring out how to make data donation safe via UX and engineering. We need all the help we can get - even if it’s just feedback. Feel reach out! Nessup@gmail.com
What's shocking about this post is there is no mention of what private API(s) are being used by Electron. The link to the Mozilla blog post has nothing to do with Electron.
Does nothing for publishers' needs for deeper control and analytics. Just a "feel good" gesture that results in additional complexity for everyone involved. Google is not the only company in the world that knows how to load a page efficiently.
The publisher's cookie-based analytics will operate on the origin in the URL bar in this case. The document (though not the delivery server) will have access to publisher origin cookies.
Conceptually, you can think of a signed exchange as a 301 redirect to a new URL which has already been cached by the browser (so there is no 2nd network event). The cache was populated by the contents of the signed exchange, assuming the signature validates.
