Public CDNs Are Useless and Dangerous

• Google Fonts

  492 17,611 9.9 HTML

  Font files available from Google Fonts, and a public issue tracker for all things Google Fonts

  

+1

It's not even clear if using Google Fonts is GDPR compliant (since you're leaking the fact that your visitor has visited your website):

https://github.com/google/fonts/issues/1495

Even if you do want to use your own custom pretty font on your site, just self host it, or bundle it with something like https://fortawesome.com/

• esm.sh

  58 2,825 9.8 Go

  A fast, smart, & global CDN for modern(es2015+) web development.

  

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• fontsource

  40 4,576 9.1 TypeScript

  Self-host Open Source fonts in neatly bundled NPM packages.

  

You're very right, my bad. I meant to link to Fontsource:

https://fontsource.org/

They provide the tools to bundle the fonts and serve them yourself:

https://fontsource.org/fonts/merriweather-sans

Will update original comment.

• ipfs

  29 7,434 8.7 JavaScript

  Discontinued IPFS implementation in JavaScript

  

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Suggest a related project