Live data from Hacker News

Thoughts on Cloudflare

xn--gckvb8fzb.com

31–40 of 88 posts

Re: Thoughts on Cloudflare

#31
post #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".

I don’t see a problem with a company continuing to make useful products. Email delivery was a pretty logical next step for Cloudflare.

Non-sequitur. Op comment is not criticizing that they offer another product, but that they offer another proprietary product that furthers locks you into their ecosystem.

Re: Thoughts on Cloudflare

#32
post #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".

I don’t see a problem with a company continuing to make useful products. Email delivery was a pretty logical next step for Cloudflare.

The problem is that globally the concepts of monopolies being bad and antitrust regulations being good have in practice left the current zeitgeist

Re: Thoughts on Cloudflare

#33
post #5

It's pretty disappointing that the author (writing in 2025) says "perhaps to maintain its status as the world’s largest botnet operator," and links to a Spamhaus report from Q1 of 2020.[0] If you check the most recent version of the report from Spamhaus (Jan to June 2025)[1], Cloudflare is nowhere to be seen, and Digital Ocean, who they recommend as a Cloudflare alternative is listed as third largest botnet host in t…

Yes, I agree. The anti-monopolistic spirit of the post is good but when you read sentences like that or recommending "major cloud services" as an alternative, well, it starts to smell like a hit piece.

Re: Thoughts on Cloudflare

#34
post #29
post #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".

I'm currently on my Nth run of: - I want to deploy a tiny service for personal use - That has occasional requests (think ~10 a day) - Needs to respond to a few daily events: a CRON job here and there, read an email, webhooks... Think a simpler Zapier In principle this would be perfect for any of the many cloud function providers. But AFAIK all of them have this vendor lock-in built into their business model and I jus…

Write a dockerfile and pay for a PaaS service.

Re: Thoughts on Cloudflare

#36
post #30

What we really need is more IPV6 deployment so normal people can have plenty of routable addresses and we can go back to hosting more things on the edges like we used to, on computers we physically control. There are plenty of applications where the bandwidth of PON fiber commonly deployed to homes is more than sufficient, and the extra latency is irrelevant. Sure, it may be susceptible to DDoS attack, but if tens of…

Running a server from "home" (or an office) I think is too expensive for most businesses. Paying for battery backups, duplicate internet providers, diy NOC, is just too much, especially for small side projects where the goal is publish blogs or write code, not side-hustle SRE

Re: Thoughts on Cloudflare

#37
post #14
post #9

Earlier quoted context omitted.

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. 𓂺

Test ﷽

Re: Thoughts on Cloudflare

#38
Tangential nitpick: I wish HN would display the punycode IDN in the submission URL as the intended マリウス.com

I mean, I understand the opportunity for abuse, but if it displays fine as UTF8 in comments in the previous sentence it might make sense to display it correctly over there in the submission.

Re: Thoughts on Cloudflare

#40
post #29
post #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".

I'm currently on my Nth run of: - I want to deploy a tiny service for personal use - That has occasional requests (think ~10 a day) - Needs to respond to a few daily events: a CRON job here and there, read an email, webhooks... Think a simpler Zapier In principle this would be perfect for any of the many cloud function providers. But AFAIK all of them have this vendor lock-in built into their business model and I jus…

[deleted]
Post reply on HN