I had submitted an issue about the removal of the non-identifying direct CDN lin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		spdustin on Oct 24, 2016 \| parent \| context \| favorite \| on: Font Awesome 5 I had submitted an issue about the removal of the non-identifying direct CDN link to FontAwesome in favor of a user-identifying JavaScript embed, and it was closed. I tagged in to another issue to make the same point, https://github.com/FortAwesome/Font-Awesome/issues/9245#issu... Still no answer. Am I the only one that cares that the current state of FontAwesome encourages tying your email address (via a unique token) to your site's specific FontAwesome usage?

fortawesome on Oct 24, 2016 [–]

There are plenty of places to serve Font Awesome from a CDN for free. All the old options are there (and still listed in the documentation).

https://www.bootstrapcdn.com/fontawesome/ isn't going anywhere anytime soon.

(Also, 4.7 was released today with 41 new icons. If you had one of our unqiue CDN links, you'd be able to upgrade without pushing any code.)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact