WARP is here

The article mentions that WARP is exposing the end user's IP to websites they visit. I'd be interested in how they do that, especially with HTTPS websites where they can't MITM and inject headers.

> WARP is not designed to allow you to access geo-restricted content when you’re traveling. It will not hide your IP address from the websites you visit.

There's also a technical version of this post: https://blog.cloudflare.com/warp-technical-challenges/

I'm hyped to see Rust code running on so many phones.

How would this work together with nextdns.io?

I was openly critical of Cloudflare when they announced Warp the first time. My accusations were over-reaching, and I ultimately retracted them. But I'm still skeptical, and I still won't use Warp.

Here's what still bothers me: Cloudflare is a single company with points of presence all over the world, handling traffic for websites all over the world (including some big ones), and now trying to attract consumers worldwide to proxy their traffic through its network. That's a lot of power, and we all know the saying about power and corruption. It doesn't matter how conscientious the leadership are. I'd prefer that the temptation to abuse that power was just not there at all.

My idea of a better Internet is a return to the way the Internet was -- a large number of small providers, communicating with each other over open standard protocols. So, yes, I should switch to something other than Comcast here in my apartment. So far, I've been afraid that doing that would leave me with a truly abysmal quality of service. (I'm in Bellevue, Washington.) But at least I can avoid adding Cloudflare, with its terrifying power, to the mix.

Granted, I mostly use the Internet on a stationary computer with a cable connection at home. About the only thing I do on my phone away from a WiFi connection is request an Uber ride. And I do need that to work reliably. But it is working just fine without Warp. So, maybe Warp is just not for me. Still, for the people that would benefit, I'm afraid of how much more power they're going to be giving Cloudflare when they tap that "on" button.

Great eye! We haven't figured out how to expose them yet for sites not using Cloudflare. We do have some experience solving this problem for Spectrum [1] we're hoping to lean on. The most important thing to us is users don't expect us to keep their IP private, as that is not the intent of WARP.

1- https://blog.cloudflare.com/mmproxy-creative-way-of-preservi...