Live data from Hacker News

Tell HN: Cloudflare Is Blocking Piped

news.ycombinator.com

121–127 of 127 posts

Re: Tell HN: Cloudflare Is Blocking Piped

#121

Earlier quoted context omitted.

I'm surprised you're handing incoming requests from everybody. We only process the CloudFlare ones and drop the rest.

You can fill the pipes to the server(s) you're targeting, it doesn't have to be application layer.

Right, "finding a provider whose reaction to an aggravating quantity of incoming packets was charging money rather than throttling the connection" was basically the load bearing part of the solution here.

Fortunately, while said quantity was indeed aggravating, it was low enough that the cost was financially and logistically less than trying to do something more elegant.

Sometimes brute force and ignorance is, in fact, the right answer, and I don't have to -like- that being true for it to be true.

Re: Tell HN: Cloudflare Is Blocking Piped

#122
post #110

Earlier quoted context omitted.

No need for AI, browser can easily be automated and captcha can be solved using cheap services

> captcha can be solved using cheap services call it what it is - you're using slave labor in a 3rd world country to solve rudimentary puzzles for you

It's probably not slave labor. It may be really poorly paid labor but if you had slave labor you'd probably use it for something profitable like construction like they do in the Persian gulf countries instead of solving captchas that people pay $3 per 1000 for.

Re: Tell HN: Cloudflare Is Blocking Piped

#124

I used to love Cloudflare but their argument for free speech absolutism went out the window when they started making judgement calls about which sites to block and which to keep. Now I'm just disappointed but not surprised. Will probably move off entirely once Tailscale funnels allow for custom termination CNAMEs. If this particular instance is them getting DMCA'd then it's not really their fault, but I'm confirmatio…

"I know that Cloudflare is legally required by the US government to abide by the DMCA, but this supports my theory they are censoring the web more and more on purpose!" ?????

No I'm saying this case explicitly does not support my argument, however there are enough cases of them making judgement calls that this independent pattern has formed and it's easy for me to fall into the trap of confirmation bias. My initial comment wasn't clear but it doesn't let me edit now.

Re: Tell HN: Cloudflare Is Blocking Piped

#125
post #73

Earlier quoted context omitted.

this won't stop the overall trend, but it can help you get around cloudflare's effective scraping blocking (copying my comment from a previous thread): If you're scraping with Python, try cloudscraper—among other things(!), it supports JS rendering (basically the bare-minimum check cloudflare does), without needing to run a full browser in the background. It's built on requests, so integration was pretty easy. https:…

JS rendering is not enough. Cloudflare monitors UI interactions and browser footprints to assess whether it’s a human or a bot.

trust me, I'm aware—cloudscraper can also solve cloudflare challenges, including turnstile

Re: Tell HN: Cloudflare Is Blocking Piped

#126

Earlier quoted context omitted.

>The big unanswered question is how they'll manage to stay good given the obvious incentive of abusing this setup. Why do you think they're still "good"? CloudFlare has chosen to abandon sites that held free speech (abhorrent speech, but still free speech) while still protecting forums upon which credit cards and methamphetamine were listed for sale on the front page. To me, that's not a sign of a "good" actor.

Free speech doesn't exist within the context of a privately held website.

Agreed, but it's a strange value system that says, "Dealing meth and stolen credit cards is okay, but having a web forum that makes fun of people is not."

Re: Tell HN: Cloudflare Is Blocking Piped

#127
post #77

Earlier quoted context omitted.

I think the ability to put TLS in front of a non-TLS'd website comes of a few properties: 1. It's probably better than nothing. 2. It's a legacy thing. A company like Cloudflare has to make a choice - how frequently do we break users who've set up their site in a way that is no longer in line with security best practices? It looks like the decision they've made is to break infrequently. Certainly the site I set up in…

I think even now you can find Linux distros preferring to ship their data over HTTP with GPG-keys recommended for the security. This isn't really to solve the same problem though. The GPG key thing is so you can use mirrors for hosting that are distributed but still trust the package came from the real source. TLS termination of where the packages are retrieved is separate.

Yes, the gpg piece provides that functionality nicely. However, it’s exceedingly common for the mirrors to not be provided over TLS for cost reasons. Netflix switched to serving video over TLS for no other reason than to promote the usage of TLS (after a lot of custom engineering (pki on cpu, crypto on nic iirc?) to reduce the overheads of doing this.
Post reply on HN