Re:Web.dev by Google
by PavlovsCat on Tuesday November 13, 2018 @05:03AM
(#18439890)
I see no explanation given why an asset that never changes would need to be requested once a day, and they clearly state they do record it.
> We only [sic] see 1 CSS request per font family, per day, per browser. Google Fonts logs records of the CSS and the font file requests, and access to this data is kept secure.
I read that as what's written there. It's for tracking. Tracking popularity is still tracking.
> Tracking popularity is still tracking.
Tracking usually refers to tracking users, which as I read the FAQ isn't what it's for.
Re:Web.dev by Google
by PavlovsCat on Wednesday November 14, 2018 @02:49AM
(#18448268)
They take and keep the tracking data. What they say they use it for doesn't change that. If they simply incremented a counter the bit about "keeping access to the data secure" would make no sense.
Do you have a guess why those assets are not cached more aggressively?
As I read the FAQ, the actual font files are aggressively cached.
It's only the CSS files that links to the font files that aren't cached forever.
Probably to allow for updates and estimate popularity, with low overhead assuming CSS files are small.
This is a complete guess but I suppose one request everyday would be enough to get atleast some idea of how popular any given font is. The page says its to keep them updated but I highly doubt that would be the reason.
Re:Web.dev by Google
by outside1234 on Tuesday November 13, 2018 @12:14AM
(#18438778)
So it’s tracking then
I'm no lawyer, but I read that as it is not used for tracking users.
(full disclosure: I work at Google, on something unrelated)