# cdnjs A free and open source CDN service powered by Cloudflare. Making it faster and easier to load library files on your websites. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Worth Reading 082926 DevFeed: [Worth Reading 082926]() Original publisher: [Read original article]() Author: Russ Published: 2026-08-29T14:47:35Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [cdnjs](), [ChatGPT](), [genai](), [data centers](), [DNSSEC]() Tags: [chatgpt](), [data-centers](), [dnssec](), [genai](), [technology](), [worth-reading]() ### AI overview A developer-oriented reading roundup covering content delivery networks, ChatGPT and scaling toward artificial general intelligence, high-density data-center builds, GenAI-assisted medical image analysis, and the practical difficulty of maintaining DNSSEC. ### Source excerpt The term "content delivery network" reflects the technology's original value proposition. Sam Altman released ChatGPT for free in late 2022. Many users fell in love both with it and Altman's argument that artificial general intelligence could be achieved through scaling. T If you work around data centers and high-density builds, you have probably heard the term "Multi-Core Fiber" thrown around. Ask yourself these questions, assuming you have a serious medical condition and your doctors are going to be using GenAI to scan your images and test results to discover the breadth and depth of your condition and to recommend treatment. Maybe adoption is low not because people don't believe DNSSEC is useful, but because turning it on and keeping it on is still genuinely harder than it should be. ## Firebase sponsors ViteConf 2022 and previews a Vite integration DevFeed: [Firebase sponsors ViteConf 2022 and previews a Vite integration]() Original publisher: [Read original article]() Author: David East Published: 2022-08-30T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Vite](), [cdnjs](), [hosting](), [JavaScript]() Tags: [community](), [conference](), [firebase](), [hosting](), [javascript](), [vite]() ### AI overview Firebase announces its sponsorship of ViteConf 2022, a free virtual conference scheduled for October 11-12. The article also previews a Firebase Hosting integration for Vite and a Firebase lightning talk at the event. ### Source excerpt We're thrilled to be sponsors of ViteConf 2022 and we can't wait to talk all things Vite! ## Public CDNs Can Create Security, Privacy, and Stability Risks DevFeed: [Public CDNs Can Create Security, Privacy, and Stability Risks]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2021-07-19T14:15:00Z Content type: opinion Language: en Sources: [HTTP Toolkit]() Topics: [cdnjs](), [Security & Privacy](), [Caching](), [modern web development](), [JavaScript](), [jQuery]() Tags: [browsers](), [caching](), [cdn](), [javascript](), [performance](), [reference](), [security](), [security-privacy]() ### AI overview This article argues that using public CDNs for common scripts and styles can introduce security, privacy, and stability risks while providing limited modern benefits. It recommends self-hosting content and dependencies, with a private caching CDN placed in front of the application for performance. ### Source excerpt Once upon a time, loading common scripts & styles from a public CDN like cdnjs or Google's Hosted Libraries was a 'best practice' - a great way to instantly speed up your page loads, optimize caching, and reduce costs. Nowadays, it's become a recipe for security, privacy & stability problems, with near-zero benefit. Just last week, a security researcher showed how this could go horribly wrong. There are ways to mitigate those risks, but in practice the best solution is to avoid them entirely: self-host your content and dependencies, and then use your own caching CDN directly in front of your application instead for performance. I'll explain what that means in a second. First though, why was this a good idea, and how has it now become such a mess? Why was this a good idea? The main benefit that public CDNs of popular libraries offered was shared caching. If you used a popular version of jQuery then you could reference it from a public CDN URL, and if a user had recently visited another site that used the same version of jQuery from the same CDN then it would load instantly, straight from their cache. In effect, sites could share resources (almost always JavaScript) between one another to improve caching, reduce load times, and save bandwidth for sites and visitors. Even in the uncached case, this still offered benefits. Browsers limit the number of simultaneous open connections by domain, which limits the performance of parallel resource downloads. By using a separate domain for some resources, resource loading could be spread across more connections, improving load times for visitors. Lastly, the main site's cookies aren't sent in requests to 3rd party domains. If you have large cookies stored for your domain, this creates a lot of unnecessary data sent in every request to your domain, again unnecessarily increasing bandwidth usage and load times (honestly I'm not sure if this overhead really had a practical impact, but it was certainly widely documented as an impor