starred/nsupdate.info-nsupdate-info

Fork 0

mirror of https://github.com/nsupdate-info/nsupdate.info.git synced 2026-04-25 08:35:56 +03:00

[GH-ISSUE #23] use xstatic packages for jquery, bootstrap, etc. #23

New issue

Open

opened 2026-02-26 09:34:59 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 09:34:59 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/23

ThomasWaldmann wrote:
they offer a little metadata including CDN information, additional to the static files, all installable via pypi.

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/23 ThomasWaldmann wrote: they offer a little metadata including CDN information, additional to the static files, all installable via pypi.

kerem added the

enhancement

task

labels

2026-02-26 09:34:59 +03:00

kerem commented

2026-02-26 09:35:00 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 22, 2013):

asmaps wrote:
CDN is good for now. For self-serving put them in static

@ThomasWaldmann commented on GitHub (Oct 22, 2013): asmaps wrote: CDN is good for now. For self-serving put them in static

kerem commented

2026-02-26 09:35:00 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 23, 2013):

if we just put it in static, we have 3rd party stuff in our project, not nice.

so let's just use xstatic, it was invented just for that and is low-fat.

@ThomasWaldmann commented on GitHub (Oct 23, 2013): if we just put it in static, we have 3rd party stuff in our project, not nice. so let's just use xstatic, it was invented just for that and is low-fat.

kerem commented

2026-02-26 09:35:00 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 12, 2013):

this task can be held back as long as we just use all 3rd party stuff from the CDNs.

but as soon as we have a reason to serve that stuff on our own, it should be done like described in this task.

@ThomasWaldmann commented on GitHub (Nov 12, 2013): this task can be held back as long as we just use all 3rd party stuff from the CDNs. but as soon as we have a reason to serve that stuff on our own, it should be done like described in this task.

kerem commented

2026-02-26 09:35:00 +03:00

Author

Owner

@elnappo commented on GitHub (Oct 30, 2014):

one reason is: http://www.heise.de/security/meldung/Nach-Hack-Verdacht-jQuery-Entwickler-untersuchen-ihre-Server-2402550.html
in english: http://www.riskiq.com/resources/blog/jquerycom-malware-attack-puts-privileged-enterprise-it-accounts-risk

@elnappo commented on GitHub (Oct 30, 2014): one reason is: http://www.heise.de/security/meldung/Nach-Hack-Verdacht-jQuery-Entwickler-untersuchen-ihre-Server-2402550.html in english: http://www.riskiq.com/resources/blog/jquerycom-malware-attack-puts-privileged-enterprise-it-accounts-risk

kerem commented

2026-02-26 09:35:00 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 30, 2014):

Yeah (although in that specific case they said that the CDN isn't affected - but it could happen...).

@ThomasWaldmann commented on GitHub (Oct 30, 2014): Yeah (although in that specific case they said that the CDN isn't affected - but it could happen...).

kerem referenced this issue

2026-02-26 10:30:58 +03:00

[GH-ISSUE #469] Remove third parties from Website #341

kerem referenced this issue

2026-02-26 10:31:27 +03:00

[PR #261] [MERGED] Update font awesome and jquery, add subresource integrity see #23 #430