Live data from Hacker News

Cloudflare Email Service: private beta

blog.cloudflare.com

441–450 of 578 posts

Re: Cloudflare Email Service: private beta

#441
post #4

Eventually all Internet protocols will be MITMed by cloudflare. Your single point of interception!

Yes, Cloudflare would be the ideal point for spy agencies to MITM things. It wouldn't surprise me if the funding for it came from them. And since they sit in between, many API audit logs wouldn't even flag intrusions because everything would look like you'd done it.

Re: Cloudflare Email Service: private beta

#442

Earlier quoted context omitted.

>Cloudflare’s ToS and contracts prevent them from doing nastiness Crypto AG's ToS also presumably said "we pinky promise not to backdoor our devices" when selling it to foreign governments, and look how they ended up. https://en.m.wikipedia.org/wiki/Crypto_AG

Crypto AG was a literal CIA front. Are you saying you think Cloudflare is a CIA front?

Yes. 0% sarcasm.

It is possibly the biggest MITM operation in the history of computing. An unbelievable intelligence asset.

Re: Cloudflare Email Service: private beta

#443

Earlier quoted context omitted.

Try https://mailpace.com The lowest plan $40/year for 1k emails/month isn’t on the Pricing page, but you can select it when signing up.

Sounds expensive. Amazon SES has 1k emails/month included for free (if you use an API to send). When sending via SMTP that quota does not apply, but still 1k Emails just costs 0.1$ (yes, 10 cents). I do not use any other AWS services but SES for my emails because of the pricing, I host everything else on Hetzner.

Yes but AWS SES emails don't get delivered to inboxes

Re: Cloudflare Email Service: private beta

#444

> Imagine a user emails your support address. A Worker can receive the email, parse its content, call a third-party API to create a ticket, and then use the Email Sending binding to send an immediate confirmation back to the user with their ticket number. That’s the power of a unified Email Service. This is/was already possible. You can just reply to an email from an email worker.

i did this exact thing literally 15 years ago with a simple django app -- there's no way they are using this kind of example in 2025 year of our lord.

Re: Cloudflare Email Service: private beta

#445

Earlier quoted context omitted.

Yes, but also you can't send an email in any meaningful way on the internet without going through a middleman anyways so while philosophically you're correct, in reality it's already the case.

I don't think that is true for email or xmpp. Could you please explain?

You can roll your own email if you can get your head around setting up an OpenBSD box and configuring OpenSMTPD and the correct domain DNS records - but the issue will be email deliverability. Gmail etc are going to treat as spam most emails that turn up from a residential or VPS linked IP address.

Personal email servers will communicate with each other happily but you need a middleman one for important recipients if you want to be sure it gets into an inbox.

Re: Cloudflare Email Service: private beta

#446
post #249

Earlier quoted context omitted.

For example, recently certain big corp ask me to verify something. I clicked on the link in the E-Mail and it was suck on Cloudflare the click button over and over again. No matter how many times I clicked. Do I need to find another internet access now?

You need to become more like a "normal person." No VPN (unless your ISP is extremely shady, then do use a VPN or change ISP), no overly zealous adblock (ublock origin on default settings should be fine), no JS blocking / weird privacy extensions / whatever, nno PiHole, just what your average, relatively tech-savvy geek would use. HN readerships's problems with Cloudflare are mostly their own fault. "normal" internet…

Hmmmm, it's rare that I'll bite, but in this instance, I just have to

> You need to become more like a "normal person."

Isn't in inherently problematic that there is even a definition of a "normal person"? Who gets to judge this? Why do I have to conform? This immediately creates in-groups and out-groups. We should all know better than to allow this to happen. Classification is fine. Probably even needed to help with inclusion. Restriction based on classification can very quickly become problematic.

> No VPN (unless your ISP is extremely shady, then do use a VPN or change ISP)

That's all ISPs by now. You should never just trust any authority logging what you do. What is fine today might not be fine with tomorrow's government and those logs (as much as some might pretend they are not) are permanent. VPN bans will start to pop up all over the place soon and everyone half-paying attention knows why

> no overly zealous adblock (ublock origin on default settings should be fine)

And what is the definition of overly zealous? Chrome has already dropped support for ublock, more or less. Adblocking is directly hostile to the data-hoovering machine. That should be enough reason to use very restrictive adblocking. I am using every filter list there is with Firefox on Linux. Cloudflare's checks are basically always fine. ReCaptcha, however, is a nightmare.

> no JS blocking / weird privacy extensions / whatever

Well, most of the web doesn't work when blocking JS outright. So I guess we've lost that battle. Though I'd argue that things like reader-mode and the ability to just get text content is pretty important to quite a lot of people still, especially those with disabilities. I don't understand the derogatory tone used when calling privacy extensions weird and the 'whatever' part is just a flippant dismissal of an entire ecosystem of extensions and applications that have a right to exist

> nno PiHole

PiHole is soon going to be the only way to protect yourself, considering what Google is pushing for with manifest v3. I don't yet use it, because it's a pain in the ass, but I'd rather have less internet and more control than vice versa

> just what your average, relatively tech-savvy geek would use.

Why do you think that you should be the one to define what or who that is? Furthermore, why should anyone be given that right? What are we really losing by allowing people to have custom setups vs. what are we losing when we don't?

> HN readerships's problems with Cloudflare are mostly their own fault. "normal" internet users don't have these problems

This reliance on the definition of "normal" is problematic, for the aforementioned reasons. You don't know what normal is and having a gate-keeper of this definition will lead to ever-smaller circles of people falling under that definition, until one day you are no longer normal and then what?

> [1] except for people in specific countries, and I do feel sorry for those.

Get ready to feel sorry for yourself in the near future :)

Re: Cloudflare Email Service: private beta

#447

Earlier quoted context omitted.

I don't know what kind of internet you used but mine didn't randomly decide to block my access to a website because some quasi monopolist decided I wasn't allowed to use a certain website for intransparent reasons.

That’s the website owner deciding to do that, Cloudflare just gives them the tools to do so.

Sure, the restaurant down the street chose to protect themselves against the likely risk of their competitor running DDoS against their website instead of their website agency getting a kickback out of a cloudflare partnership.

Re: Cloudflare Email Service: private beta

#448
Love this, assuming they come in as the lowest cost provider.

But I'm more interested in seeing how they'll maintain clean sending IPs.

I have a feeling they grossly underestimate how difficult this will be.

I will not touch this with a 10 foot pole for a few years while they iron out all the kinks.

Re: Cloudflare Email Service: private beta

#449
post #432

Earlier quoted context omitted.

> the internet was worse without Cloudflare Cloudflare acts as a proxy for dynamic content, thereby slowing down the internet. Their existence (and success) suggests a lack of infrastructure or solutions (ie. DDOS, CDN) from data centers on their own and by default, what is... sad, as if the data centers were falling asleep without adapting to the times. Soon we may have this picture: User > ISP > VPN (or proxy) > Cl…

Hmm, I don't know where you get that takeaway. For me, it's an edge cache, so it speeds up the internet. It sits between user and origin, often many hops closer, and serves content cached according to rules set by customer. When you're a CF customer they send you reports on how much bandwidth origin is saving and for me, historically, it's been most of it. And they do all of it for free most of the time! There's not…

Cache of static content, ie. images, css, js or an static html, the CDNs purpose, to shorten location.

At moment you serve dynamic content, you are literally redirecting the request through an intermediary server (from Cloudflare/Homologous to the original server and come back, they are acting as a proxy).

This results in a slowdown of the internet. In fact, it's easy to tell when a regularly visited site has changed and put Cloudflare in between, because it takes longer to load.

> It also keeps hackers from knowing origin's ip which is nice.

Only if you put extra care trying to hide tracks. But certainly it keeps script kiddies from knowing origin's ip, what it is the only one nice feature.

Datacenters should deal with this, but their passivity over the years seems to know no bounds.

Post reply on HN