Bunny fonts – privacy respecting drop-in replacement for Google Fonts

Re:Bunny fonts – privacy respecting drop-in replacement for ... by heretogetout on Sunday June 19, 2022 @01:44PM (#31801564)

If the font is already in your browser cache (which it might be if they're hosting it on a common CDN) web pages should load with the correct font right away instead of either loading blank areas or a default fallback font before switching to the correct font, causing jank.

The best solution here is to use standard fonts that are available in all browsers, of course.

[ Parent | on HN ]

Re:Bunny fonts – privacy respecting drop-in replacement for ... by modeless on Sunday June 19, 2022 @02:01PM (#31801716)

Sorry, not since cache partitioning. https://developer.chrome.com/blog/http-cache-partitioning/

Privacy killed the shared cache.

[ Parent | on HN ]

Re:Bunny fonts – privacy respecting drop-in replacement for ... by SquareWheel on Sunday June 19, 2022 @06:37PM (#31804198)

And it's such a niche privacy issue too. I would gladly take a shared cache over cache isolation. Especially for something used on as many sites as Google Fonts is.

[ Parent | on HN ]

Re:Bunny fonts – privacy respecting drop-in replacement for ... by mikeiz404 on Monday June 20, 2022 @03:50AM (#31807426)

You may be interested in the LocalCDN extension [1] which tries to solve the privacy vs speed issue for common resources by intercepting known remote resource requests and returning a local copy.

1: https://www.localcdn.org/

[ Parent | on HN ]

Re:Bunny fonts – privacy respecting drop-in replacement for ... by SquareWheel on Monday June 20, 2022 @07:18PM (#31817508)

It looks like it's only "officially" supported on Firefox, but I'll give it a try. Thanks.

[ Parent | on HN ]

Re:Bunny fonts – privacy respecting drop-in replacement for ... by mritzmann on Monday June 20, 2022 @03:26AM (#31807280)

For data protection reasons, this has not been the case for a long time. Both for Firefox and Chrome.

[ Parent | on HN ]