social.giorgiocomai.eu
  • Login
  • Public

    • Public
    • Groups
    • Recent tags
    • Popular
    • People

Conversation

Notices

  1. rysiek ✅ (rysiek)'s status on Thursday, 24-Jan-2019 21:05:32 CET rysiek ✅ rysiek ✅

    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.

    #WebDev #SysAdmin #Google

    Thursday, 24-Jan-2019 21:05:32 CET from mastodon.social permalink
    • Giorgio Comai likes this.
    • Adrian Cochrane (alcinnz)'s status on Thursday, 24-Jan-2019 21:49:52 CET Adrian Cochrane Adrian Cochrane
      in reply to

      @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.

      Thursday, 24-Jan-2019 21:49:52 CET permalink
    • rysiek ✅ (rysiek)'s status on Thursday, 24-Jan-2019 21:50:58 CET rysiek ✅ rysiek ✅
      in reply to
      • Adrian Cochrane

      @alcinnz patches welcome!

      Thursday, 24-Jan-2019 21:50:58 CET permalink
    • rysiek ✅ (rysiek)'s status on Thursday, 24-Jan-2019 22:42:59 CET rysiek ✅ rysiek ✅
      in reply to

      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.

      Thursday, 24-Jan-2019 22:42:59 CET permalink
    • rysiek ✅ (rysiek)'s status on Friday, 25-Jan-2019 00:10:45 CET rysiek ✅ rysiek ✅
      in reply to
      • OCCRP

      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)

      Friday, 25-Jan-2019 00:10:45 CET permalink
    • Jacek (jacek)'s status on Friday, 25-Jan-2019 11:34:57 CET Jacek Jacek
      in reply to

      @rysiek On a related topic: Does using Google Fonts break GDPR?

      Friday, 25-Jan-2019 11:34:57 CET permalink
    • rysiek ✅ (rysiek)'s status on Friday, 25-Jan-2019 11:37:38 CET rysiek ✅ rysiek ✅
      in reply to
      • Jacek

      @jacek I would say it breaks GDPR if you don't inform your users about it.

      Friday, 25-Jan-2019 11:37:38 CET permalink
    • Jacek (jacek)'s status on Friday, 25-Jan-2019 11:41:46 CET Jacek Jacek
      in reply to

      @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).

      Friday, 25-Jan-2019 11:41:46 CET permalink
    • rysiek ✅ (rysiek)'s status on Friday, 25-Jan-2019 11:44:06 CET rysiek ✅ rysiek ✅
      in reply to
      • Jacek

      @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! :)

      Friday, 25-Jan-2019 11:44:06 CET permalink
    • Giorgio Comai (giocomai)'s status on Friday, 25-Jan-2019 11:45:38 CET Giorgio Comai Giorgio Comai
      in reply to
      • Giorgio Comai
      Looks excellent and useful! It's such a pain to do this manually, so - I admit - one defaults to just leaving the calls to Google fonts there
      Friday, 25-Jan-2019 11:45:38 CET permalink
    • rysiek ✅ (rysiek)'s status on Friday, 25-Jan-2019 11:46:23 CET rysiek ✅ rysiek ✅
      in reply to
      • Giorgio Comai

      @giocomai yeah, same here. Happy you find it useful. Suggestions and patches welcome!

      Friday, 25-Jan-2019 11:46:23 CET permalink
    • Jacek (jacek)'s status on Friday, 25-Jan-2019 11:46:34 CET Jacek Jacek
      in reply to

      @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).

      Friday, 25-Jan-2019 11:46:34 CET permalink
    • rysiek ✅ (rysiek)'s status on Friday, 25-Jan-2019 11:47:12 CET rysiek ✅ rysiek ✅
      in reply to
      • Jacek

      @jacek sure, but random sites moving away from Google Fonts are *already* a measurable improvement of users privacy.

      Friday, 25-Jan-2019 11:47:12 CET permalink
    • Giorgio Comai (giocomai)'s status on Friday, 25-Jan-2019 11:50:18 CET Giorgio Comai Giorgio Comai
      in reply to
      • Giorgio Comai
      Will give it a try soon and will see how it goes! thanks!
      Friday, 25-Jan-2019 11:50:18 CET permalink
      rysiek ✅ likes this.

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

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.

Creative Commons Attribution 3.0 All social.giorgiocomai.eu content and data are available under the Creative Commons Attribution 3.0 license.