News for hackers. Stuff that matters.
Re:GDPR penalty for passing on of IP address to Google by us... by ZeroGravitas on Sunday January 30, 2022 @05:59AM (#30135812)
This seems logical and reasonable to me, though it seems others are surprised/appalled.

What would a technical solution that respects privacy look like? The website making the call to Google in the background (minus user details) and forwarding the response onward? Why isn't it done that way, it feels like it's the more obvious solution if you're not trying to track users.

Early internet was very wary of 'hotlinking' because it costs money to serve things, people used to try to offload hosting costs to others. Now it seems people take that on willing with the expectation to make enough money to cover it.

Is it just scale, or is it the user info that makes these services viable?

Early Google used to use the argument that them making the web better was profitable, because more people using the web meant more money for them. Does that still apply? Would they still provide Google Fonts if they were legally bound to not use any user information they recieved?

Re:GDPR penalty for passing on of IP address to Google by us... by tgv on Sunday January 30, 2022 @06:02AM (#30135840)
> What would a technical solution that respects privacy look like?

In case of fonts: hosting it on your domain.

Re:GDPR penalty for passing on of IP address to Google by us... by ZeroGravitas on Sunday January 30, 2022 @06:08AM (#30135897)
Google Fonts actually provides a couple of extra services, which can't be replicated just by 'hosting' the files.

Not as relevant now, but in the past a big feature was serving the smallest font file to the user based on the browser version they had.

Nowadays, the ability to use a Unicode aware font without sending the whole thing to every user is another feature they offer.

Both feel like things that browser improvements could take care of themselves eventually though and in the meantime libraries running locally could handle.

(For similar services, licencing plays a part, as you may be paying for the font per view or something like that, but that Doesn't apply for Google Fonts)

Re:GDPR penalty for passing on of IP address to Google by us... by Scarblac on Sunday January 30, 2022 @06:03AM (#30135847)
A main selling point of using CDNs for commonly used assets (like Google fonts) is that lots of websites use the same URL, so the browser is likely to have the asset in cache already from a previous use on another site. Makes the site faster and uses less bandwidth.

I don't think there is a solution right now. Maybe browsers can stop sending these headers to well known CDN domains by default.

Re:GDPR penalty for passing on of IP address to Google by us... by the_mitsuhiko on Sunday January 30, 2022 @06:05AM (#30135875)
Browsers do not share these caches due to privacy concerns. There is no benefit to it being in a central vs your own cdn.
Re:GDPR penalty for passing on of IP address to Google by us... by Scarblac on Sunday January 30, 2022 @06:07AM (#30135883)
Ah OK, I'm probably years out of date then. I'll look it up.
Re:GDPR penalty for passing on of IP address to Google by us... by isbvhodnvemrwvn on Sunday January 30, 2022 @06:52AM (#30136236)
It was implemented within the last 2 years, with exception of Safari which did it in 2013.
Re:GDPR penalty for passing on of IP address to Google by us... by daanlo on Sunday January 30, 2022 @06:11AM (#30135918)
I think one of the main reasons it is done via hotlinking is that it is easier for the „webmaster“ to copy a JS snippet than to do something server side or self host. Most of these webmasters aren‘t developers.

This is particularly true for anything that comes as a „module“, like GDPR cookie notices (that are very frequently included via a JS snippet loaded from a third party site).