7 ms·

tracking

by gondo 8y ago

tracking

jopsen 8y ago
https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users https://developers.google.com/fonts/faq#what_does_using_the_... 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)
- deleted 8y ago
  [deleted]
- philtar 8y ago
  Do you have a guess why those assets are not cached more aggressively?
  - fantyoon 8y ago
    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.
    - outside1234 8y ago
      So it’s tracking then
  - jopsen 8y ago
    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.
- PavlovsCat 8y ago
  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.
  - jopsen 8y ago
    > Tracking popularity is still tracking. Tracking usually refers to tracking users, which as I read the FAQ isn't what it's for.
    - PavlovsCat 8y ago
      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.
jefftk 8y ago
While I don't know anything about fonts stuff, successful execution of the ad tag leads to an ad request, and this happens on every page view which has the script and not just the ones where the file has fallen out of cache. So there's no additional useful information Google would get from a low cache lifetime for the script. The script request is to a cookiless domain for performance, unlike the ad request, so there's not even much useful information on that request. (Disclosure: I work at Google, on ads JS, and I previously worked on mod_pagespeed. Not speaking for Google, just myself.)

tracking

by gondo 8y ago

tracking

https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users https://developers.google.com/fonts/faq#what_does_using_the_... 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)

deleted 8y ago
[deleted]
philtar 8y ago
Do you have a guess why those assets are not cached more aggressively?
- fantyoon 8y ago
  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.
  - outside1234 8y ago
    So it’s tracking then
- jopsen 8y ago
  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.
PavlovsCat 8y ago
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.
- jopsen 8y ago
  > Tracking popularity is still tracking. Tracking usually refers to tracking users, which as I read the FAQ isn't what it's for.
  - PavlovsCat 8y ago
    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.

jefftk 8y ago

While I don't know anything about fonts stuff, successful execution of the ad tag leads to an ad request, and this happens on every page view which has the script and not just the ones where the file has fallen out of cache. So there's no additional useful information Google would get from a low cache lifetime for the script. The script request is to a cookiless domain for performance, unlike the ad request, so there's not even much useful information on that request. (Disclosure: I work at Google, on ads JS, and I previously worked on mod_pagespeed. Not speaking for Google, just myself.)