News for hackers. Stuff that matters.

timrivera

Re:Ask HN: why Google doesn't see HN as a link farm? on Friday January 17, 2014 @04:55PM (#7078701)
> Most link farms do not have incoming links from highly ranked sites

That's a good point I didn't consider.

Re:Ask HN: why Google doesn't see HN as a link farm? on Friday January 17, 2014 @04:25PM (#7078508)
Thanks for the heads up, I didn't know that.

Ask HN: why Google doesn't see HN as a link farm?

Honest question. We know Google [1] (Bing and other s.e.) is fighting an endless war against link farms. AFAIK HN doesn't use rel="nofollow" [2] (EDIT: not entirely true, see comments below) so its link juice may flow to any website that is submitted. However, HN and its linked sites don't seem to be negatively affected nor penalized. What makes HN different from what Google consider a link...

( Read More... | 8 comments | 8 points | on HN )
Re:How To: Hosting with Amazon S3, CloudFront and Route 53 on Monday January 13, 2014 @03:08PM (#7052950)
there's also the IP Anycast [1] option. That's what you get with OVH CDN [2], for example, but not with CloudFront. Anycast routing is totally independent from DNS, thus it works fine with an A record and also makes it easy to install SSL certificates.

[1] http://en.wikipedia.org/wiki/Anycast

[2] https://www.ovh.co.uk/cdn/

Re:How To: Hosting with Amazon S3, CloudFront and Route 53 on Monday January 13, 2014 @02:29PM (#7052724)
This is actually a great point against using custom domains (CNAMEs) with Cloudfront. At least if you can't afford the custom SSL certficate option.

Cloudflare somehow got this right. They serve non HTTPS enabled web sites with different IP addresses so that you can never reach them over HTTPS (could be better "This webpage is not available" vs. scary red "This is probably not the site you are looking for!" message in Chrome). Plus, they have a great free anycast DNS network that can be compared to Route 53. And best off all, you never pay for the bandwidth.

Re:How To: Hosting with Amazon S3, CloudFront and Route 53 on Monday January 13, 2014 @02:20PM (#7052675)
That's what I immediately thought when I first read it, especially now that Github Pages are served over Fastly's CDN [1]. Then I realized that Github Pages do not support server side (301) redirects at all. Quite a big turn-off when you move an existing website over a new platform.

[1] https://news.ycombinator.com/item?id=7019148, https://news.ycombinator.com/item?id=6975830

Re:Bing now supports https on Saturday January 11, 2014 @04:14PM (#7043778)
Bing used to be hosted by Akamai, looks like they switched over their own edge network.

Also, https://bing.com just redirected to plain http, now you can actually search over https like with Google and DDG.

Re:Faster, More Awesome GitHub Pages on Wednesday January 08, 2014 @10:15AM (#7023944)
definitely not doing Anycast. As I wrote just a few days ago [1] github.map.fastly.net resolves to a different IP address based on the geographic location of the user. The exact server location might be approximated from the X-Served-By response header:

  X-Served-By: cache-fra1225-FRA
  X-Served-By: cache-d46-DAL
[1] https://news.ycombinator.com/item?id=6975830