zackbloom

It's at least meant to be the opposite, specific such that you can trust we're making real promises. You can read the full privacy policy here: https://www.cloudflare.com/public-resolver-mobile-privacy/

That is not something which has factored into the conversation on our (Cloudflare's) end. The bigger issue is even as we make technical improvements, we very much don't want to create a separate Internet. The minute we begin adding, removing, or changing content when it comes through Warp those questions begin to be asked.

Sorry about that, there's an issue we're currently dealing with which hits people who had a specific version of the old 1.1.1.1 app and just updated. It should be fixed shortly.

Yes! We're working on desktop clients as well but they'll be available a bit later than the mobile launches, as the most performance benefit is available when you're on a cell network.

You could try looking at https://1.1.1.1, it is more brief and to the point, but you might be looking for something more technical and direct?

I was, at one point in my life, a Boston Developer ;). Sadly at least one of those things is no longer accurate.

Switched the account so it wouldn't be confusing who was commenting.

It's WireGuard [1] coupled with tech from our Mobile SDK [2] and (in the case of Warp+) Argo [3]

1- https://github.com/cloudflare/boringtun

2- https://blog.cloudflare.com/mobile-sdk-acceleration/

3- https://www.cloudflare.com/products/argo-smart-routing/

It's exceptionally clear that she liked robbing banks. It literally says in the article "Surely Peggy Jo had to know that if she was in some kind of financial jam again, we would have helped her out."

Just to put this in perspective, a traditional phone line encodes 56 Kb/s of data, which was believed to be the size channel to send the human voice with a reasonable quality. They are doing it in 1.6 Kb/s!

I think you probably want to keep the Netlify but lose the React.

Author here, cool seeing this on HN. If you'd like another history, here's one on stock quotes which also forms a nice history of sending data far away: https://blog.cloudflare.com/history-of-stock-quotes/

Still no, an analog computer is an electronic computer which uses varying voltages and currents to calculate results. It's not the same as a manual computer.

You can also use Argo Tunnel to create a secure tunnel between your origin and Cloudflare.

Interesting idea: employee canaries. You have a way to follow 1-5 employees of a company you think are honest. If they quit, you get a message.

Cloudflare does have a form of hosting: https://workers.dev

(I work at Cloudflare)

The Reddit and StackExchange stories are before my time, but I believe they related to reliability issues we were having at the time. It was over three years ago at this point, a lot has changed.

I have a personal connection with your comparison because my company actually used Fastly before I joined Cloudflare, I had the exact perception you're describing. Four years later, being able to write JavaScript with Workers would have made my life so much easier than trying to do failover in VCL as I was then.

No, any amount of traffic can be served at any plan level.

I'm not sure we need another incentive for large companies to not use best-practices and modern technology.

They're running a business. They offer an inordinate amount of service totally free to millions of developers, and they make their actual client open-source for your pleasure. Is your argument they also have to go to the trouble of making their infrastructure easily self-hosted? How would they make the money to pay the lawyers to respond to the very legal threat this tweet is about without revenue?

In this case it's more useful to think of Cloudflare as a compute platform than a CDN. There are many other places where you can take JavaScript you write to run on Cloudflare and get it running (Lambda, App Engine, your own server). It won't be globally distributed or as fast, but it could be made to run.

In principle an aggregator is showing customers multiple hotels at once, so each vendor has to discount to be competitive. If you are going specifically to a single one they could exploit your lack of information to charge a higher price.

People at some point realized this though and the individual hotel sites had to promise to be the cheapest to hope to get visitors at all.

If your goal is to augment an existing domain on Cloudflare (as in the post), you can actually use Workers today. Login to your Cloudflare dashboard and click the "Workers" tab.

For the record, I think ForeFlight is honestly the best app I've ever used. In terms of depth, reliability, and ease of use it is really unmatched not just in aviation but in any app I use on a daily basis.

Giving all the information and capabilities a pilot needs is a hard problem.

I have a fundamental question. Do people think the move towards 'serverless', this desire for some percentage of developers to not have to worry all that much about the low level infrastructure their code is running on) to die? To accelerate?

It seems somewhat clear that some percentage of developers are interested in a fundamentally higher abstraction than what operating systems have classically provided. In a world where that's true for not just a small few but for most developers, it seems that something like processor architecture could be abstrated away. It's not like it's particularly easy to replicate serverless deployment environments on developer machines today, and yet it persists.

It breaks down into a few categories, organized by how futuristic they are:

CDN extensions: People who have always wanted to be able to cache POST requests, or aggregate responses but haven't been able to do it with the limitations imposed by traditional CDNs. Workers moves what was a configuration language into a full Turing-complete programming environment which can make subrequests, interact with the Cache API directly, etc.

Pushing out to the edge: There is a long list of services which are best done close to users but don't require a huge amount of state. For example, you might want to validate access tokens before requests hit your infrastructure, or do many of the other things commonly done in an API gateway. You also might want to move performance critical components of your API which don't require much state closer to users, things like aggregating and caching GraphQL or prerendering your React app. We have a Workers KV product which gives you just enough state to handle many of these cases in beta now.

Serverless apps: This is what workers.dev is all about. The idea that if you _can_ deploy code to a network almost as large as the Internet itself is it possible that is a better model than deploying to a single region or availability zone? Without cold-starts you get instant scaling to almost any volume of traffic which is a big advantage, to the point where this type of serverless seems faster and cheaper even if you ignore the network. As you mention it will require better distributed storage tools, but we're optimistic those will become available in the near future.

You can read more using the tag on our blog (https://blog.cloudflare.com/tag/workers/) or community forum (https://community.cloudflare.com/c/developers/workers). Thanks for caring, a lot of people work on Workers every day and seeing people get invested in what we're doing is everything.

Do you work for one of those other CDN providers by chance? It certainly takes a fair bit of work to get an anycast network working, but it's not nearly the controversial move it was eight years ago.

Lambda@Edge is very limited, you, for example, cannot make requests to arbitrary hosts from an @Edge.

What sort of authentication? Are you trying to ensure that only your webapp hits your backend (which in this case is implemented in Workers)? That's generally impossible on the web, as all the code in the browser used to hit it is accessible to visitors.

More and more distributed data stores are becoming available. We (Cloudflare) have a KV [1] which can be read quickly everywhere.

[1] - https://blog.cloudflare.com/building-with-workers-kv/

One way to think about it is: why not do everything on top of a network like Workers? Does it actually make sense to deploy services to a single location when they can be trivially started up near every user?