News for hackers. Stuff that matters.
Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @03:07PM (#22369500)
I was part of the team that founded this, about 10 years ago if memory serves. I'm still loosely involved, though no longer at Google. Inconsolata was one of the 20 fonts for the original launch, and we're now in the process of launching it as a variable font, with both width and weight axes. I'm also getting funding from them for Rust-based font tools.

Feel free to AMA, though no guarantees I'll have good answers.

Re:Google Fonts Analytics by saghm on Wednesday February 19, 2020 @04:53PM (#22370474)
> Inconsolata was one of the 20 fonts for the original launch

Am I understanding this correctly to mean that you were part of a group that invented this font? Independent of the great work you obviously did on everything else, if this is correct, I just wanted to give a specific thank you for that! It's been my go-to font for my terminal, text editor, monospace font in the browser, and even the font my Linux machines use when they boot up before launching the GUI for years now.

Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @04:58PM (#22370528)
No, I drew Inconsolata myself, as well as inventing spiral-based tools for designing fonts, as an alternative to Béziers. I started work on it far in advance of working on the "Google Font API" as it was called at launch, so it was very natural to include it, along with other great fonts by other talented designers.

I'm glad you like the font!

Re:Google Fonts Analytics by enriquto on Thursday February 20, 2020 @02:15AM (#22373305)
> No, I drew Inconsolata myself, as well as inventing spiral-based tools for designing fonts, as an alternative to Béziers.

Man, I love your phd thesis! I use it regularly to show my students an example of what a PhD is supposed to be; and, independently, to teach them some planar differential geometry. Your study of Euler's elastica is the best written account of it that exists (and I have read many more geometry books that would like to admit).

Re:Google Fonts Analytics by VMG on Thursday February 20, 2020 @03:54AM (#22373695)
Re:Google Fonts Analytics by saghm on Wednesday February 19, 2020 @06:05PM (#22371075)
> No, I drew Inconsolata myself, as well as inventing spiral-based tools for designing fonts, as an alternative to Béziers

Oh, wow! Keep up the amazing work!

Re:Google Fonts Analytics by antupis on Thursday February 20, 2020 @03:42AM (#22373652)
Thanks for your work, as a programmer with minor dyslexia Inconsolata, was heaven sent to me.
Re:Google Fonts Analytics by amelius on Wednesday February 19, 2020 @05:07PM (#22370621)
Curious, have your spiral based tools been documented/published somewhere?
Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @05:14PM (#22370666)
Best place is probably my thesis: https://levien.com/phd/phd.html . All of the code is available under permissive open source license. I've been continuing to poke around with this and hope to have a newer set of tools before long.
Re:Google Fonts Analytics by jacobolus on Wednesday February 19, 2020 @11:39PM (#22372713)
Let me recommend that anyone interested in fonts, 2d graphics, CAD, etc. read Raph’s thesis. It’s great!
Re:Google Fonts Analytics by dt3ft on Wednesday February 19, 2020 @03:20PM (#22369619)
Was this created in order to track users across different sites or because google wanted to make the world a better place? :)
Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @03:21PM (#22369637)
The latter.
Re:Google Fonts Analytics by BiteCode_dev on Wednesday February 19, 2020 @04:21PM (#22370207)
Do you think it's still used for the latter rather than the former now?
Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @04:24PM (#22370250)
Heh, that's a better question. I have no reason to believe that Google Fonts are being used to track users, but I don't have hard evidence on this either way. I am deeply concerned about the way the modern Internet is turning into a surveillance machine and its potential for abuse, but if I were evil, I'd probably go after much lower hanging fruit than fonts.
Re:Google Fonts Analytics by BiteCode_dev on Wednesday February 19, 2020 @04:30PM (#22370303)
Thanks for this honest answer.
Re:Google Fonts Analytics by OrgNet on Thursday February 20, 2020 @06:48PM (#22379700)
either way, loading fonts from google for every website is a stupid idea... it is why an extension like decentraleyes is a good idea (because most website don't think about the consequences).
Re:Google Fonts Analytics by ThePhysicist on Wednesday February 19, 2020 @04:25PM (#22370258)
I think Google might have better ways to track people. Fonts are also cached by CDNs and the local browser so I’m not sure if they provide good tracking data (they get loaded only for the first page visit for example and popular fonts like Open Sans are probably already in your cache when you open a page).

If you’re concerned about tracking as a website operator you can simply load the fonts from your own server, most of them can be found on Github and have liberal licenses (I think all fonts on fonts.google.com)

Re:Google Fonts Analytics by WorldMaker on Wednesday February 19, 2020 @04:53PM (#22370480)
You can even install the fonts locally to your machine and your browser will favor the local copy. There are some tools like Skyfonts that let you install the top X from Google Fonts and it can be a fun way to speed up a lot of the web; with the tradeoff that not a lot of people have the top X installed for useful large versions of X and that becomes its own fingerprint for surveillance software (testing how long text takes to render in an off screen canvas, for instance).

It's been suggested that Browsers or Operating Systems choose a useful X value and install the top fonts everywhere like they used to install the classic "core web fonts".

Re:Google Fonts Analytics by smichel17 on Wednesday February 19, 2020 @10:15PM (#22372393)
Also there's a addon called "decentraleyes" that will cache fonts, amongst other things. It's one of 3 extensions I install in every browser I'm allowed to. The others are uBlock origin and https everywhere. All 3 have good privacy/security/performance benefits with effectively no breakage, in their default configurations.
Re:Google Fonts Analytics by commoner on Wednesday February 19, 2020 @10:59PM (#22372571)
Decentraleyes is an excellent add-on that improves browsing speed and privacy with no negative side effects. Currently, the only font cached by Decentraleyes is Noto Sans. It also caches Google's Web Font Loader script and many major JavaScript frameworks.

https://decentraleyes.org

https://git.synz.io/Synzvato/decentraleyes

Web developers who are concerned about privacy exposure from Google Fonts can use google-webfonts-helper to extract the font files and self-host them.

https://google-webfonts-helper.herokuapp.com/fonts

https://github.com/majodev/google-webfonts-helper

Re:Google Fonts Analytics by commoner on Thursday February 20, 2020 @02:22AM (#22373329)
Correction: Decentraleyes doesn't actually cache any fonts. Noto Sans is just used for the add-on interface. Font caching would make an interesting feature if the add-on developer is willing to implement it, especially if it bypasses fingerprinting.
Re:Google Fonts Analytics by smichel17 on Tuesday February 25, 2020 @10:54AM (#22414134)
I stand corrected!
Re:Google Fonts Analytics by saagarjha on Wednesday February 19, 2020 @11:49PM (#22372755)
> You can even install the fonts locally to your machine and your browser will favor the local copy.

Note that some browsers are going in the opposite direction and actively hiding installed fonts from websites due to the potential for fingerprinting.

Re:Google Fonts Analytics by inetknght on Wednesday February 19, 2020 @06:18PM (#22371191)
Delivery of fonts aren't what's used to track people. Rendering of fonts is.

Different machines render fonts in a unique way. Consider different GPUs (hardware differences), different drivers (kernel/driver differences), browsers (user-land differences), and sizes (user settings) can all contribute to a font being rendered differently per-user and increasing entropy of a particular unique font id.

Re:Google Fonts Analytics by dt3ft on Wednesday February 19, 2020 @05:26PM (#22370770)
I am slightly concerned, yes. This is why I chose to host the fonts for my 20-things.com sideproject for as long as I can afford that luxury.
Re:Google Fonts Analytics by rememberlenny on Wednesday February 19, 2020 @03:29PM (#22369714)
I currently work on it as well, so happy to pitch in.
Re:Google Fonts Analytics by flixic on Wednesday February 19, 2020 @04:42PM (#22370393)
Any estimate when Inter can be expected?

https://github.com/google/fonts/issues/1455#event-2995287982

Re:Google Fonts Analytics by juandazapata on Wednesday February 19, 2020 @03:43PM (#22369848)
Does Google use this to fingerprint and track users across different websites?
Re:Google Fonts Analytics by open-source-ux on Wednesday February 19, 2020 @04:02PM (#22370019)
The Google Font FAQ includes the question: What does using the Google Fonts API mean for the privacy of my users?

> "...your requests for fonts are separate from and do not contain any credentials you send to google.com while using other Google services that are authenticated, such as Gmail."

>"Google Fonts logs records of the CSS and the font file requests, and access to this data is kept secure."

https://developers.google.com/fonts/faq#what_does_using_the_...

Re:Google Fonts Analytics by McDyver on Wednesday February 19, 2020 @04:09PM (#22370083)
So a lot of fluff and no actual reply. Users can be tracked without cookies being sent, while "access to the data is kept secure". Call me a cynic, but I lost my trust in google a long time ago.
Re:Google Fonts Analytics by lwf on Wednesday February 19, 2020 @04:45PM (#22370413)
To answer "track users across different websites", I think they pretty clearly say the opposite:

> The Google Fonts API is designed to limit the collection, storage, and use of end-user data to what is needed to serve fonts efficiently.

> When millions of websites all link to the same fonts, they are cached after visiting the first website and appear instantly on all other subsequently visited sites. [...] The result is that website visitors send very few requests to Google: We only see 1 CSS request per font family, per day, per browser.

I guess, what would you want to see that would assuage your concerns, beyond what is written in the FAQ?

Re:Google Fonts Analytics by tjoff on Wednesday February 19, 2020 @05:15PM (#22370678)
They do not say the opposite.

Apparently they need to collect and store end-user data for serving fonts efficiently. Wonder what that could be...

And if that information happens to be enough for further tracking then it seems to be fair game!

Re:Google Fonts Analytics by codyb on Wednesday February 19, 2020 @06:57PM (#22371464)
Couldn’t it just be for edge server location determination?

Not a Google fan, but at their volume of traffic seems like it could be something they’ve optimized for.

Re:Google Fonts Analytics by tjoff on Thursday February 20, 2020 @01:22AM (#22373102)
Could be!

But they could have said so. And they could also have said that the information is not correlated with anything else.

All we know is that they have, very carefully, written something vague that they could do pretty much anything they wanted with.

And we are left with the question, why would they do that?

Re:Google Fonts Analytics by codyb on Wednesday February 26, 2020 @07:41PM (#22429188)
Probably to not have to consult the lawyers every single time someone creates a new analytics aggregation.
Re:Google Fonts Analytics by laughinghan on Wednesday February 19, 2020 @06:16PM (#22371176)
"Users can be tracked without cookies being sent"

How? Stylesheets can't use fingerprinting or Flash cookies or anything like that, only scripts can.

Re:Google Fonts Analytics by nitrogen on Thursday February 20, 2020 @01:58AM (#22373233)
Stylesheets can fingerprint with the help of a server to track what resources get loaded or skipped, and a few clever media size queries etc.
Re:Google Fonts Analytics by singron on Wednesday February 19, 2020 @08:44PM (#22372060)
The Referer header will leak what page you were on and you probably already have connections to Google from the same client IP address. Even if you have Referer blocked, the particular font requested could indicate information about what page you are on when combined with other data.
Re:Google Fonts Analytics by youngtaff on Thursday February 20, 2020 @02:11AM (#22373293)
TLS Session resumption (tickets / caching)
Re:Google Fonts Analytics by saurik on Wednesday February 19, 2020 @04:20PM (#22370196)
Multiple people (I know as my upvote just now didn't even get you back in the black) downvoted you (and now me ;P), but you are absolutely correct that that quote didn't really have anything to do with the question.
Re:Google Fonts Analytics by csomar on Wednesday February 19, 2020 @04:35PM (#22370347)
Can you still be tracked if the fonts are delivered from your server?
Re:Google Fonts Analytics by chipotle_coyote on Wednesday February 19, 2020 @04:58PM (#22370530)
No. A font file served from your own server is just like any other static asset. (I increasingly tend to do this for my sites, as I've found that using FontSquirrel to create WOFF/WOFF2 files that contain subsets of fonts and/or "collapse" font features -- e.g., stylistic alternates -- can make for very small, efficient files if the subsetting meets your needs.)
Re:Google Fonts Analytics by adventist on Wednesday February 19, 2020 @03:09PM (#22369507)
Thank you for your service!
Re:Google Fonts Analytics by bytematic on Wednesday February 19, 2020 @08:12PM (#22371883)
Rust based font tools? Do you mean local font manipulation type scripts or some sort of web service?
Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @08:43PM (#22372049)
Mostly local font manipulation tools, including a GUI editor, but I can imagine some of the work ultimately becoming useful inside web services.
Re:Google Fonts Analytics by nixpulvis on Wednesday February 19, 2020 @10:43PM (#22372512)
Not font manipulation, but the Alacritty project has had an RFC [1] open for a while now to try and make font configuration better. It turns out I barely understand fontconfig every time I need to touch it. I'm just curious what (if any) your opinions about the de-facto Linux fontconfig framework are?

[1]: https://github.com/alacritty/alacritty/issues/957

Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @11:55PM (#22372778)
I haven't dug too deep into it, but from what I've seen it seems complex, messy, and not up to solving real problems such as CJK Han unification. I wrote a bit about these difficulties in https://github.com/linebender/skribo/blob/master/docs/script... , and what I think was most disappointing is that I didn't get any actual feedback at the time. So it feels like about the same level of dysfunction as most Linux UI work.
Re:Google Fonts Analytics by tiffanyh on Wednesday February 19, 2020 @03:31PM (#22369734)
Re: variable fonts.

What’s the rule of thumb on file size ... is 1 variable font smaller than 1 normal font? Or is it more like 1 variable font is smaller than 3 normal fonts combined (eg bold, italic, regular).

Re:Google Fonts Analytics by raphlinus on Wednesday February 19, 2020 @03:37PM (#22369786)
A coarse rule of thumb is that each axis doubles the font size. So one that has just a weight axis is twice a normal font. One with a weight and width axis is four times. So if you actually use multiple instances from the design space, it's a win.

This is only a rough guide, don't take it as gospel. I'm also researching ideas (radial basis function interpolation) to make it more sparse for larger numbers of dimensions.

Re:Google Fonts Analytics by mmmrk on Thursday February 20, 2020 @03:25AM (#22373581)
For some anecdata, compare the file sizes in the latest Cantarell release tarball from the GNOME FTP server.

The compression ratio varies depending on how the variable font was made though. E.g. Noto Sans clocks in at 1.5 MB because it is made from 8 masters for two axes. Reducing it to 5 masters results in a 900 KB binary.