Hacker News Reader

Comment by pantalaimon | Hacker News Reader

I also don't understand what stops ycombinator from supporting IPv6. It's a pretty simple website, what's the big effort?

View on HN

The most touted reason is that their anti-spam systems only support IPv4. Their old Cloudflare endpoint however is still alive and you can't disable IPv6 on Cloudflare so feel free to add the following to your /etc/hosts:

    2606:4700::6810:686e news.ycombinator.com

Interestingly when I tried to post the above comment over IPv6 I got a Cloudflare "You have been blocked" page. This might be something they do not want you to know! :D

Wouldn’t it be reasonable for their backend to only accept (write) requests from whatever the anti-spam proxy is? Otherwise, there’s little point.

Currently there are no proxies in front and you connect directly to their baremetal server hosting the site. I presume the anti-spam system is custom-built and part of their own codebase. Cloudflare is officially sanctioned, but retired from widespread use.

You in fact CAN disable ipv6 on Cloudflare, but they make you do it with an API request.

This was possible only for some time, now it's only enterprise option I'm afraid. For Free/Pro plan option is grayed out and API refuses to change it.

Doesn't that still only remove the records from DNS? So far for all Cloudflare sites that IPv6 disabled I've been able to derive the IPv6 address by hand and make requests without issues.

Interesting that apparently this is a problem, I would have thought that spam filtering is completely outsourceable by now.

Doesn’t CloudFlare have good bot detection? What does HN do that relies on IP addresses that CloudFlare can’t do?

HN can do things like "This user is posting from an IP which geolocates far from where it normally posts from". It can take into account the total post history, user upvotes, etc.

Cloudflare bot detection is more request-by-request. Cloudflares product is more intended to prevent DDoS attacks with millions of bots. I don't think it's sufficiently fine tuned to prevent a handful of spam comments through.

I know of so many websites that break spectacularly when you do that...

This was an interesting Cloudflare "feature" I found out about the hard way. Even if you only use Cloudflare for DNS hosting, they will happily accept proxied requests for your hostnames and route them to your origin. I discovered this when we received a L7 DDoS from only Cloudflare IPs - the attacker had pointed their bots at Cloudflare with our hostname (bold move!).

The official solution (and might be why you see the blocked page) is to set up the WAF to block all requests.

Do they also accept proxied requests for domains that are not yet verified?

Could you elaborate on this? What is being proxied, http requests? And can you use any CF IP?

Yes, HTTP / HTTPS requests can be proxied this way. Any CF IP seems to work. HTTPS only works if the target hasn't disabled Universal SSL (i.e, they have a TLS cert provisioned on Cloudflare's IPs).

We're just slow.

I truly feel this statement in my bones the longer I'm in technology...

How does ipv4 vs ipv6 affect speed?

They're slow in migrating, not there's a difference between IPv4 and IPv6 performance.

Reply on news.ycombinator.com