Google Code Blog: Introducing the Google Font API & Google Font Directory

Re:Google Code Blog: Introducing the Google Font API & Googl... by qjz on Wednesday May 19, 2010 @04:21PM (#1362229)

I wish they'd serve everything from subdomains in google.com. I mean, seriously, why does Google keep registering new domains for projects (google<something>.com) when they could easily use <something>.google.com instead? What's wrong with fonts.google.com?

[ Parent | on HN ]

Re:Google Code Blog: Introducing the Google Font API & Googl... by Hovertruck on Wednesday May 19, 2010 @04:41PM (#1362274)

My guess is they don't want to send all the cookies stored on the google.com domain whenever someone loads a font.

[ Parent | on HN ]

Re:Google Code Blog: Introducing the Google Font API & Googl... by ggrot on Wednesday May 19, 2010 @05:01PM (#1362339)

Seems reasonable. It protects users too because they can't track the cookies across these domains even if they wanted to.

[ Parent | on HN ]

Re:Google Code Blog: Introducing the Google Font API & Googl... by revicon on Wednesday May 19, 2010 @08:21PM (#1362853)

Yahoo does this as well for the same cookie reason. Lots of stuff is hosted on yahoo.net that's considered potentially unsafe.

[ Parent | on HN ]