|operations/puppet : production||wmcs: Fix double Access-Control-Allow-Origin headers for tools-static|
|operations/puppet : production||wmcs: Update tools-static reverse proxy rules for Google fonts|
|operations/puppet : production||tools-static: add /fontcdn/ to reverse-proxy to Google Fonts|
|Open||None||T133919 [EPIC] Protect end-user privacy by restricting non-consensual third-party browser interactions|
|Open||None||T103934 Convert all Labs tools to use cdnjs for static libraries and fonts|
|Resolved||zhuyifei1999||T110027 Create a fonts CDN for use on Tool Labs|
- Mentioned In
- T209998: Possible privacy break when loading font from toolserver (https://tools-static.wmflabs.org/fontcdn/)
T189459: Adding an extra tab in the top of Basque Wikipedia
T182604: tools-static is throwing space warnings due to cdnjs git repo size
T168786: Monumental imports css from fonts.googleapis.com
- Mentioned Here
- T96799: Provide a clone of cdnjs for toollabs users
Having a caching proxy for things like fonts would not be a violation of "Using Wikimedia Labs as a network proxy" in my opinion. That rule is about making an open proxy rather than a focused cache to improve visitor privacy.
We should just setup something similar to the https://cdnjs.com/ mirror that we run at https://tools.wmflabs.org/cdnjs/. The steps taken to set that up are documented in part at T96799: Provide a clone of cdnjs for toollabs users. The hard part as always is promoting the use of the new service once it has been setup.