I accidentally a Font Degooglifier:
https://git.occrp.org/libre/fonts-degooglifier
I was sick and tired of having to manually degooglify fonts, so I made this. Seems to work. Handles both local files and URLs.
Perhaps somebody finds it useful.
I accidentally a Font Degooglifier:
https://git.occrp.org/libre/fonts-degooglifier
I was sick and tired of having to manually degooglify fonts, so I made this. Seems to work. Handles both local files and URLs.
Perhaps somebody finds it useful.
@rysiek Something that could be useful:
use hueristics upon the filenames to fix the @font-face rules so they declare the same font family but different font weights, styles, etc.
It always annoys me that Google fonts doesn't declare their @font-face rules properly, in the way that works best for designers and browsers. That they confuse the concepts of font files and font families.
@alcinnz patches welcome!
Humm... Currently Fonts Degooglifier works by creating a copy of the CSS file and working on that copy.
I am starting to think it should instead create a backup and work on the original.
I wanted to go slow and not break things, but it does seem more intuitive.
Phew! Fonts in 3 @OCCRP projects ungooglified! Easy, since now I have the right tool for the job. ;)
1. Sandcastle property map:
https://cdn.occrp.org/projects/sandcastle/en/index.html
Related investigation:
https://www.occrp.org/en/goldensands/
2. Libre code if anyone wants to make a similar map (also ungooglified now):
https://git.occrp.org/libre/property-map
3. Putin's Circle:
https://cdn.occrp.org/projects/putinandtheproxies/en/
Related investigation:
https://www.occrp.org/en/putinandtheproxies/
(this one does not have a libre code thingy... sorry)
@rysiek On a related topic: Does using Google Fonts break GDPR?
@jacek I would say it breaks GDPR if you don't inform your users about it.
@rysiek This also my opinion (however since informed consent should be given **before** accessing `fonts.google.com` it really means that it breaks/bends GDPR almost always).
Some lawyer I know insists that it **just** needs to be deep in privacy policy.
However I managed to get decision to remove google fonts from internal cookiecutter template citing --- well we have no privacy policy in this template either ;) (and apart of google fonts this side IMO doesn't require user consent).
@jacek there we go. Here's a toot for everyone saying "#GDPR doesn't work".
You are not the first person to tell me they are removing some privacy-invading tech due to GDPR. Well done! :)
@giocomai yeah, same here. Happy you find it useful. Suggestions and patches welcome!
@rysiek Well first they take down google and facebook general privacy violations. Only then someone will go against random sites using google fonts . . . (unless someone actually renders "constent page" without loading them).
@jacek sure, but random sites moving away from Google Fonts are *already* a measurable improvement of users privacy.
social.giorgiocomai.eu is a social network, courtesy of Giorgio Comai. It runs on GNU social, version 1.2.0-beta4, available under the GNU Affero General Public License.
All social.giorgiocomai.eu content and data are available under the Creative Commons Attribution 3.0 license.