Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve fonts.googleapis.com at build-time, not at runtime #4395

Open
Ezwen opened this issue Mar 18, 2022 · 0 comments
Open

Resolve fonts.googleapis.com at build-time, not at runtime #4395

Ezwen opened this issue Mar 18, 2022 · 0 comments

Comments

@Ezwen
Copy link

Ezwen commented Mar 18, 2022

Expected Behavior

When running RestyaBoard in a browser, I would expect it to be self-contained, and to not rely any resources (eg. fonts, JS libraries, etc) provided by third-party servers/companies. The reason is that, when downloaded from third parties (eg. Google), such resources are used as a mean for tracking their users.

Current Behavior

Currently, RestyaBoard has a hard-coded dependency to fonts.googleapis.com/css?family=Open+Sans, which means RestyaBoard running in a browser will always try to reach servers from Google. This means Google can track RestyaBoard users, to some extent.

See this line from index.html

<link href="//fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet" type="text/css">

Screenshots (if appropriate):

Capture d’écran de 2022-03-18 15-22-10

Possible Solution

Steps to Reproduce (for bugs)

  1. Download the provided docker-compose file.
  2. Change the volume declarations as required for the local bindings.
  3. Run docker-compose up
  4. Open Firefox (without addons)
  5. Open the developer tab (ctrl+shift+c), reach the network section
  6. Open http://localhost:1234

Context

Your Environment

  • Version used: 1.7.1
  • Environment name and version (e.g. OS, PHP, PostgreSQL): using the provided docker-compose file.
  • Operating System and version (desktop or mobile): desktop
  • Link to your project: N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant