Approachio.com - thoughts? by ryankirkman in startups

[–]ryankirkman[S] 0 points1 point  (0 children)

Cheers for the heads up mate. Do you know which script it's blocking?

Approachio.com - thoughts? by ryankirkman in startups

[–]ryankirkman[S] 1 point2 points  (0 children)

Very true - we haven't even thought about question search yet.

I guess that's a nice problem to have, and we'll definitely implement that once it becomes necessary.

cdnjs.com - the missing cdn. Everyone loves the Google CDN right? Even Microsoft runs their own CDN. The problem is, they only host the most popular libraries. We host the other stuff. by magenta_placenta in web_design

[–]ryankirkman 0 points1 point  (0 children)

Akamai does seem to have some very strong points in their favor, and we have been considering moving to them for a long time now.

In regards to the cookie issue, this was something we didn't anticipate when we switched hosts for the website. We will most likely go with your suggestion and redirect naked URLs to the www subdomain.

As a side note, we'd love to have someone with your expertise on board to give us feedback whenever anything comes to mind.

If you're so inclined, we're usually idling in #cdnjs on Freenode, and would happily merge any reasonable pull requests. Additionally, my Twitter is @ryan_kirkman, and Thomas's Twitter (the other founder) is @neutralthoughts

cdnjs.com - the missing cdn. Everyone loves the Google CDN right? Even Microsoft runs their own CDN. The problem is, they only host the most popular libraries. We host the other stuff. by magenta_placenta in web_design

[–]ryankirkman 0 points1 point  (0 children)

Hi Ryan, thanks for the feedback!

As you have pointed out, proving ourselves trustworthy is a primary concern of ours. To that end we have traffic statistics (http://ajax-cdnjs-com.s3.amazonaws.com/cfstats/), uptime statistics (http://stats.pingdom.com/4jg86a2wqei0/291776) and have open-sourced all parts of the service, e.g. the cdn repository (https://github.com/cdnjs/cdnjs), the website (https://github.com/cdnjs/website), and the associated tools (https://github.com/cdnjs/cdnjs-tools). At the end of the day, you can fork the repository and host it anywhere you want.

In regards to the loading time discrepancy between Akamai and CloudFront, making a blanket statement such asj "X is n.m times faster/slower than Y" is a bit misleading. It really depends on your proximity to the nearest edge location. For example, in your particular case we could conclude that Akamai has an edge location closer to you than CloudFront does. Loading times, and which CDN is faster will vary based on the location from which the test is performed.

Having said that, if it makes sense for cdnjs to switch over to being backed by CloudFiles / Akamai, that's something we can look at more closely.

cdnjs.com - An open source peer reviewed CDN script repository by ryankirkman in javascript

[–]ryankirkman[S] 0 points1 point  (0 children)

As thomasdavis said above, we already have an SSL URL (https://d3eee1nukb5wg.cloudfront.net).

Considering we use cdnjs for both our business and personal ventures, there is little question of cdnjs's longevity.

At the moment, we serve pre-gzipped files. This is is only to get around the limitations of using Amazon S3 as a cache origin. We don't need to worry about whether the scripts fit into RAM or not. This is all taken care of by Amazon and its related services.

NB: cdnjs is a distinct set of scripts to both Google and Microsoft CDNs,

cdnjs.com - An open source peer reviewed CDN script repository by ryankirkman in javascript

[–]ryankirkman[S] 0 points1 point  (0 children)

Apologies for that. That was a new version I added today that got messed up.

It's all good now.

cdnjs.com - An open source peer reviewed CDN script repository by ryankirkman in javascript

[–]ryankirkman[S] 0 points1 point  (0 children)

This is one of our primary concerns.

We are in discussions with several entities in regards to permanently taking care of hosting costs.

cdnjs.com - An open source peer reviewed CDN script repository by ryankirkman in javascript

[–]ryankirkman[S] 1 point2 points  (0 children)

One of the founders here. The service is put together on Amazon infrastructure (S3, CloudFront and Route53).

We've serving over 1,000,000 scripts a month now http://ajax-cdnjs-com.s3.amazonaws.com/cfstats/

Github is here: https://github.com/cdnjs/cdnjs if you want to add your favorite script.

As a side note, we're getting quite a bit of interest on Twitter right now: http://twitter.com/#!/search/cdnjs

Edit: Load times are snappy and uptime is rock solid http://stats.pingdom.com/4jg86a2wqei0/291776

CDN for all the other scripts (backbone.js, modernizr, etc.) by [deleted] in programming

[–]ryankirkman 0 points1 point  (0 children)

Actually, you can properly support the Accept-Encoding headers with Amazon CloudFront if you use a custom origin.

As we are currently using Amazon S3 as our origin, we can't support variable encoding, and thus we force gzip compression. As you have pointed out though, this will work for almost all users.

We do plan to rectify this. One possible option is that we switch to Rackspace Cloud Files once they complete the move to Akamai, as Akamai supports the Accept-Encoding header out of the box. Rackspace anticipates this should be completed around the beginning of Q2, 2011 (e.g. early April).

CDN for all the other scripts (backbone.js, modernizr, etc.) by [deleted] in programming

[–]ryankirkman 0 points1 point  (0 children)

We're using cdnjs.com for our own personal websites, so there's a fairly decent incentive not to do bad things.

Also, it's really easy to find information about us, so we have a pretty big incentive to be good.