Live data from Hacker News

Thoughts on Cloudflare

xn--gckvb8fzb.com

11–20 of 88 posts

Re: Thoughts on Cloudflare

#11
post #9
post #8

Earlier quoted context omitted.

not (exactly) a unicode encoding issue, it's IDNA encoding. it's unicode encoded as ascii.

So it’s an issue with HN being a trash website. A trash website that I like a lot, but still a trash website. Maybe in 20 years we’ll be able to use emojis on here.

Not really, it's just yet another inconclusive indication that absolutely nobody wants unicode for machine evaluated strings.

Re: Thoughts on Cloudflare

#12

Author did a surprisingly good job hanging on to all the receipts to support his claim "cloudflare bad." But his alternatives are all CDN providers - which is not even the side of the business that makes cloudflare unique and makes them money. The piece, thorough as it may be, does not offer alternatives to products that cover the exciting parts of their business and I was looking forward to seeing what those were -…

I am using Cloudflare as a back-end and only using workers (can disable all their security, performance, caching, and whatever stuff they offer; which is really just a worker). The product (workers) is differentiated and I don't think there is any company/service out there that is offering an equivalent.

I do not think that's the author complaint, though. I frequently get these cloudflare captachas and it is why I disabled their firewall (it's pure garbage) for my own sites. Cloudflare does not have any monopoly over the services you mentioned (workers, tunnels, images, etc.) but they do have a kind-of-monopoly over DNS/CDN.

Re: Thoughts on Cloudflare

#13
I once had to migrate a good number of web properties off of Cloudflare for a client. They were an agency that had used it as a go-to for many years and many clients, until the CEO of the company stated publicly that they would no longer use cloudflare as a political thing (there had been a news story that Cloudflare was providing ddos protection for some Nazi websites and refused to take them down, or something similar enough).

My takeaway was basically that people use Cloudflare a lot because it is a strong service with a ton to offer at a very low price point. It's a bit like gmail - just very convenient and offers a lot for free or very cheap. Switching at that scale made a significant increase in their monthly bill.

I do applaud people who go out of their way to create alternatives to major services like cloudflare, gmail, chrome, etc. As an individual it can be hard to do though, or at least not always the path of least resistance.

Re: Thoughts on Cloudflare

#14
post #9
post #8

Earlier quoted context omitted.

not (exactly) a unicode encoding issue, it's IDNA encoding. it's unicode encoded as ascii.

So it’s an issue with HN being a trash website. A trash website that I like a lot, but still a trash website. Maybe in 20 years we’ll be able to use emojis on here.

We can use emojis, just higher class ones.

𓂺

Re: Thoughts on Cloudflare

#17
post #9
post #8

Earlier quoted context omitted.

not (exactly) a unicode encoding issue, it's IDNA encoding. it's unicode encoded as ascii.

So it’s an issue with HN being a trash website. A trash website that I like a lot, but still a trash website. Maybe in 20 years we’ll be able to use emojis on here.

This is a punny code, and I'm fine - if not happy - that HN doesn't choose to render their underlying unicode symbols. It's very easy to spoof URLs this way, e.g. using a symbol from another language to craft a look-alike URL that can match a reputable site.

Browsers like now Chrome try and alert you if the URL visually looks spoofed (because they do support unicode symbols in the omnibox), but I'm yet to see how well this holds up in production.

And I hope in even 20 years we still can't use emojis here, our language isn't so pitiful that we must regress to brightly coloured symbols.

Re: Thoughts on Cloudflare

#19
Very good post. Cloudflare is continuously adding services to their cloud offerings (the latest being Email delivery) in a familiar pattern of "let's make it impossible to switch".

Re: Thoughts on Cloudflare

#20
post #7

If it wasn't on HN, being upvoted by some, I wouldn't have clicked on the link judging from the domain name. Turns out it is unicode issues. I wonder if HN will ever fix it.

One shouldn't judge a domain by its codepage ;-)
Post reply on HN