For every one of these CDNs you use, chances that people with scriptblockers will use your site goes down. When I see that a site tries to resolve scripts from 50 domains, for what should really just be static HTML, I generally leave. So please. Don't use CDNs. If you want people to trust you, host your own damn stuff on your own domain.
Cdnjs - the missing cdn
31–40 of 79 posts
Re: Cdnjs - the missing cdn
#32Earlier quoted context omitted.
I assume you are the creator of cdnjs - what are your relation with cloudflare beyond just the sponsorship? Are you working for them? Do you advise them? I'm wondering what is the performance increase delivered by cloudflare. I've heard many mixed opinions and I'm at the interesection where I have to decide whether I'm using them or others. btw - kudos to Cloudflare for sponsoring this - seems like a great way to put…
We have a very good relationship with Cloudflare. See these releases by Cloudflare: http://blog.cloudflare.com/cdnjs-community-moderated-javascr... https://www.cloudflare.com/apps/cdnjs As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854
If I'm guessing what the names of your Pingdom checks mean correctly, they seem to show CloudFlare making your response time 10ms slower. I'm assuming that cdnjs.cloudflare.com is the site with CF in front, and cdnjs.com is without, not sure if that's correct.
Re: Cdnjs - the missing cdn
#33Ok, I'm not a developer and I'm probably missing the big picture or smth; my question: - All this fuss is about hosting a few text files none bigger than several KB?? Who in this world does NOT afford to host a few small files nowadays?
The idea is that users wouldn't have to download the same jquery or whatever script over and over for every site they visit. It makes less sense when it comes to not-so-popular script files, but I guess there's a convenience factor too.
Or at the very least, we need some way to say "get this script from this URL, but only if it hashes to , since otherwise it's been compromised". Why worry about CDNs when you can design the script-switcheroo attack right out the system in the first place?
I wrote about this in June: http://rachelbythebay.com/w/2012/06/27/src/
Re: Cdnjs - the missing cdn
#34For every one of these CDNs you use, chances that people with scriptblockers will use your site goes down. When I see that a site tries to resolve scripts from 50 domains, for what should really just be static HTML, I generally leave. So please. Don't use CDNs. If you want people to trust you, host your own damn stuff on your own domain.
Re: Cdnjs - the missing cdn
#35Earlier quoted context omitted.
We have a very good relationship with Cloudflare. See these releases by Cloudflare: http://blog.cloudflare.com/cdnjs-community-moderated-javascr... https://www.cloudflare.com/apps/cdnjs As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854
> As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854 If I'm guessing what the names of your Pingdom checks mean correctly, they seem to show CloudFlare making your response time 10ms slower. I'm assuming that cdnjs.cloudflare.com is the site with CF in front, and cdnjs.com is without, not sure if that's correct.
Re: Cdnjs - the missing cdn
#36Earlier quoted context omitted.
We have a very good relationship with Cloudflare. See these releases by Cloudflare: http://blog.cloudflare.com/cdnjs-community-moderated-javascr... https://www.cloudflare.com/apps/cdnjs As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854
> As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854 If I'm guessing what the names of your Pingdom checks mean correctly, they seem to show CloudFlare making your response time 10ms slower. I'm assuming that cdnjs.cloudflare.com is the site with CF in front, and cdnjs.com is without, not sure if that's correct.
Re: Cdnjs - the missing cdn
#37Earlier quoted context omitted.
We have a very good relationship with Cloudflare. See these releases by Cloudflare: http://blog.cloudflare.com/cdnjs-community-moderated-javascr... https://www.cloudflare.com/apps/cdnjs As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854
> As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854 If I'm guessing what the names of your Pingdom checks mean correctly, they seem to show CloudFlare making your response time 10ms slower. I'm assuming that cdnjs.cloudflare.com is the site with CF in front, and cdnjs.com is without, not sure if that's correct.
Re: Cdnjs - the missing cdn
#38For every one of these CDNs you use, chances that people with scriptblockers will use your site goes down. When I see that a site tries to resolve scripts from 50 domains, for what should really just be static HTML, I generally leave. So please. Don't use CDNs. If you want people to trust you, host your own damn stuff on your own domain.
How does using CDNs make you distrust a website? If someone is loading jquery.min.js from Google shouldn't you trust it more ?
If a website needs scripts, I expect the website to serve it from a domain which belongs to it. For most sites I visit there are at least 30, sometimes 50 scripts from various sites and domains trying to track me, slowing down my browsing experience, and sucking up my systems ram.
Disabling those causes massive speed-ups. Plus it protects my privacy.
Install ScriptNo in Chrome (or similar for Firefox). You will be shocked by the difference. And you will be shocked by the massive script-abuse currently on the net.
And no, I will not wade through that long list for each and every page I visit, to whitelist whatever CDN you have decided to put in the same trustworthyness-group as doubleclick.net.
If your site breaks with those scripts blocked, I leave.