In Germany, there is growing concern regarding usage of "undocumented" google functions. This is in relation to GDPR/DSGVO aspects and so far mostly concerns google fonts, however, one of our users complained about jquery being loaded from the google CDN.
Since the version of this file is hardcoded into SMF code anyway, would it be possible to also deploy jquery.min.js together with the SMF code in the future in order to preempt such concerns?
I haven't checked for other loads from remote CDNs, maybe there's more...
Quote from: arminus on August 12, 2022, 10:37:34 AMIn Germany, there is growing concern regarding usage of "undocumented" google functions. This is in relation to GDPR/DSGVO aspects and so far mostly concerns google fonts, however, one of our users complained about jquery being loaded from the google CDN.
Since the version of this file is hardcoded into SMF code anyway, would it be possible to also deploy jquery.min.js together with the SMF code in the future in order to preempt such concerns?
I haven't checked for other loads from remote CDNs, maybe there's more...
If you are using SMF 2.1 you can change how you load the Jquery Library.
Admin CP > Configuration > Features & Options > General
Then go to Source for the jQuery Library. You can choose Google CDN, jQuery CDN, Microsoft CDN, Local, or custom even.
Thanks, I wasn't aware of that.
Just saw this, reminded me that when alpha was first released none of the jquery functions worked for me. After some dicking around, it was determined that my browser security was blocking google cdn (I consider anything from google to be malware :P ). Apparently the current default setting in 2.1 is still google cdn, but it now works in my browser. Nonetheless, I have it set for local, which loads jquery from /Themes/default/scripts. Can't see why anyone would use anything else.