Wikipedia Moves to CloudFlare | Hacker News Reader

Wikipedia Moves to CloudFlare

twitter.com

15 pointsJ_tt9 comments

I really hope cloudflare doesn't go the way of a Google.

At one point they were benevolent dictators, and we the subjects enjoy being oppressed.

Now with the virtual signaling, rotted business ethics, 0 support available, and tone deaf corporate decisions, we put them into a place of power only to have it used against us.

It’s always possible but for now Cloudflare is a joy to work with and their engineering is top notch. If it wasn’t for their corp HQ being in the most crazy expensive city in the US that is the place I’d like to work. Check out their GitHub repos sometime, there are some real gems in there.

They have a large engineering office in Austin, too.

This is exactly why I was massively concerned about the cloudflare IPO. I always saw cloudflare as being one of the top tech companies in the world, no bullshit, high quality service, blog posts which are incredible, open source (contribution and libraries, iirc I've used their lz4 golang implementation in some hobby projects), free tier or REASONABLE indie pricing ($20/month for small businesses iirc) all of which screams cool-tech-startup...

then you bring in an IPO and the company is duty bound to make profits and it will all go to shit, and I'm really not looking forward to that both as an advocate and a customer.

This is interesting. I was wondering yesterday why Wikipedia does not use CloudFlare or some other CDN, but then I thought that cost would be enormous. It also crossed my mind that CF could sponsor the service, but then again - even they may not afford paying for the traffic for one of the world's most popular websites.

I am curious how this will unfold. Thank you Mr Prince and CloudFlare for your support. I am keeping my fingers crossed so this cooperation, in whatever form, is successful.

And another one bites the dust, increasing the monoculture of the web. Let's also not forget Firefox is going to enable DoH by default too, sending all our DNS queries to CloudFlare.

I don't know, I just think people should be much more concerned about this.

> helping us roll onto a new service offering of theirs that was barely yet in the wild

So something more than DDOS protection and CDN?

I'm guessing it's Magic Transit, since thats CloudFlare's latest thing, some other tweets suggested the same.

CF cannot handle extremely large attacks either; what makes this a more suitable solution than what they're currently using?

Edit: and before anyone downvotes me, understand that I am asking an earnest question. I don't know what Wikimedia currently uses to protect their infrastructure, and how it compares to Cloudflare.

Reply on news.ycombinator.com