keybase / keybase/keybase-issues
Get rid of cross-origin requests to Google
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
keybase.pub is currently making cross-origin requests to fonts.googleapis.com and fonts.gstatic.com. Please get rid of them, to help decrease Google tracking exposure of your visitors.
Note that keybase.io behaves better, and loads font files from the same domain.
Also see the following screenshot of my [Firefox Lightbeam](https://addons.mozilla.org/en-US/firefox/addon/lightbeam/) graph. The two triangular nodes that connect Google services with Keybase are the aforementioned domains.

In the meantime I am blocking those two domains, which is just a workaround and degrades the appearance of keybase.pub a bit.
Further references:
- https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users
- https://whotracks.me/trackers/google_fonts.html
- https://whotracks.me/trackers/gstatic.html
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting how keybase.pub loads fonts and compare that behavior with keybase.io, as described in the issue. Done means keybase.pub no longer makes cross-origin requests to fonts.googleapis.com or fonts.gstatic.com while retaining the intended appearance.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100