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.

Sign up for GitHub

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

Jump to bottom

Put the static assets on the local server #74

Closed
Rembane opened this issue Feb 5, 2019 · 0 comments · Fixed by #114
Closed

Put the static assets on the local server #74

Rembane opened this issue Feb 5, 2019 · 0 comments · Fixed by #114
Assignees
@Rembane

Comments

@Rembane
Copy link
Contributor

Rembane commented Feb 5, 2019

The static assets are fetched from maxcdn and Google, if we instead put them on our web server we save our users privacy.
@Rembane Rembane linked a pull request Sep 24, 2023 that will close this issue
Inline fonts to not accidentally leak data to 3rd party hosting the fonts #114
Merged
Rembane added a commit that referenced this issue Sep 24, 2023
@Rembane
Chore: Inline fonts to not leak data to 3rd party
92ec7fa 
Web Fonts have the potential to leak data to where they are fetched
from, in our case it is Google Web Fonts. By inlining them we do not
leak data anywhere.

Close #74.
@Rembane Rembane self-assigned this Sep 24, 2023
icicel pushed a commit that referenced this issue Sep 24, 2023
@Rembane
Chore: Inline fonts to not leak data to 3rd party (#114)
05f7c1e 
Web Fonts have the potential to leak data to where they are fetched
from, in our case it is Google Web Fonts. By inlining them we do not
leak data anywhere.

Close #74.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rembane Rembane

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Inline fonts to not accidentally leak data to 3rd party hosting the fonts dtekcth/mat-chalmers
1 participant
@Rembane