zackbloom

CloudHub

Skunkworks [1] is a really great book by the designer of the propulsion system (and subsequently the first stealth airplane). I highly recommend it to anyone who wants to know how many drill bits you burn through trying to build a titanium airplane.

1- https://www.thriftbooks.com/w/skunk-works_ben-r-rich_leo-jan...

I'm one of the original creators of You Might Not Need jQuery. Most of the examples still date back to 2014, with modern JS they get much simpler and shorter (the fetch API and async/await help tremendously in the first example cited).

What if your server dies right as it's about to release that lock and mark the job done? How will you ever know if it was completed or not?

This is a little dystopian to me. You absolutely can have a job which pays you to build things you think matter.

If this is the only way they can get attribution on iOS devices, they won't have much of a choice.

Who says to invest in companies who's products you use? That does not seem like great advice. You should invest in companies who are undervalued by the market in your opinion, not just because you like the product but because you think they have a good business around it.

I believe what it does is economically incentivize more people to build renewable energy plants by paying them more for each kWh they generate. If you pay to cover one ton of CO2 you are raising the price paid for renewable energy, such that more renewable plants will be built, such that some future energy need will pull from those plants instead, ultimately generating the total amount of energy the world demands but with one ton less CO2 released.

I'm far from an expert though, hopefully someone will correct me if I'm wrong.

Identifying the device is probably on the order of nano to microseconds.

It's very possible he explained something entirely reasonable to the reporter who then misunderstood it.

Have you taken a look at the Cloudflare Keyless SSL tech?

The reason it has to be prefetched from not-you is to protect the users privacy. Until they click a link it is not considered acceptable to leak their search to the potential destination. Links have to be fetched from a third-party who the search engine trusts not to share the data, that at the moment is Google but will hopefully expand.

That is up to the website, some elect to use separate URLs for their AMP content, others serve a different version based on the requestor, others might be AMP-native and not have another incarnation.

[I work at Cloudflare]

It's hard to build a great website, particularly one which works well on mobile. AMP as a web framework makes it easier. There's nothing about that value it which is intrinsically linked to any particular way of rendering AMP, a good chunk of the web would be better off building on AMP independent of Google. That doesn't mean every site should, there are developers and teams who are capable and willing to build great sites and we support their right to not have to use AMP. The need to use AMP-the-framework to get instant loading is hopefully a temporary one partially fixed by signed exchanges.

The AMP cache is also made much less concerning and painful for users through the use of signed exchanges. By ensuring the content is what was provided by the origin we believe the Internet is becoming a more trustworthy place, opening the door to sites being able to be served from wherever they will be most performant.

Correct, it's essentially the same as it is now, but easier as you don't have to worry about removing the "google.com/amp" prefix.

That's kind of a funny way of thinking about it, buy yes? Loading an AMP page is (hopefully) an action which isn't mutating any state, so I would say it's more similar to how a CDN works. You decide you are interested in having a cache respond to a given request in a specific way, and it responds to requests which look a certain way with that response.

In this case it's significantly more secure though, as the exact request and response are signed and a third-party you trust (your browser) is deciding if that signature matches.

I work on AMP Real URL at Cloudflare and am happy answer any questions (live from AMPConf in Tokyo)!

If you're looking for a super in-depth technical post which includes all sorts of wonderful bits about the engineering and cryptography involved don't miss https://blog.cloudflare.com/real-urls-for-amp-cached-content...

AMP Real URL was built by engineers Avery Harnish (started when Avery was an intern!) and Gabbi Fisher, and is built on top of our Workers [1] tech.

1- https://www.cloudflare.com/products/cloudflare-workers/

It explains in the article. The waves were too high to get crew on the droneship to tie it down, and they only got worse.

Wow, I really had no idea this is what I was watching in the original video. They should consider adding a "This was filmed in one take on one piano" title card!

> Fifteen received 40 mg of propranolol after spending 2 minutes in proximity to a large tarantula, 15 got placebo, and another 15 received propranolol without exposure to a tarantula.

What about a group who was exposed to the tarantula without the propranolol?

We certainly didn't want the post to disappear. It was flagged by HN (either the mods or people with enough karma to flag), we would happily have it be restored if it were under our power.

I've read through every comment on this page and there's nothing here I wouldn't stand behind, even if much of seems to be misunderstood as in this thread.

> I technically told Billy, but I don't think he bothered to tell anyone else :)

Billy actually told Joaquin and I, but we were more psyched that Steve was joining than worried about how HN would find out.

The Cloudflare Wireguard implementation is open-sourced and BSD licensed, what would be the concern? https://github.com/cloudflare/boringtun

It's important to not confuse Lambda for Lambda@Edge. Lambda can be executed in a total of 18 AWS regions (if you don't count GovCloud). More importantly, actually running your code in every region would be somewhat tricky, their architecture is built around you deploying to each individually.

Lambda@Edge does run on their CDN nodes, but it isn't quite for general-purpose compute, there's a long list of restrictions you can find here: https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...

If you're interested in the performance differences, I ran some comparisons using Catchpoint a while ago: https://blog.cloudflare.com/serverless-performance-compariso...

Lambda and Lambda@Edge also deal with things like cold-starts which impact performance irrespective of the breadth of the network. You can see some of those numbers here: https://serverless-benchmark.com/

That is generally more of a recommendation. The recreational diving limit is generally considered to be 130ft, as that's the depth you can't spend more than a few minutes at without incurring mandatory decompression (breathing air).

You can take a deep diving course if you like, but not everyone bothers. Going below 130 though becomes a technical and very complex endeavour quickly.

Cloudflare | Engineers and Product Managers | Austin, TX | Full-time | Onsite

You might have seen our Warp launch today! We're building all manner of new ways for people to both use the Internet and build things on it. Our culture is fundamentally defined by small teams with outsized responsibility, solving hard technological challenges, and a focus on shipping products to our users as quickly as we can.

If you're interested I'm happy to answer questions and route to the right place: zack at cloudflare

I'm writing about our Austin jobs although we also have positions in SF, London and several other locations. I'm sure you can also find several other Cloudflare listings on this very page!

1. It will exit close to you, unless you have Warp+ in which case we might route it to a different PoP closer to your destination if that makes it faster. It is not designed to bypass censors.

2. No

3. Exactly what an actually nefarious person WOULD say!

This is correct. It's significantly harder to inject the origin IP into a TCP stream. We have ways [1] of doing it, but it requires some coordination on both sides.

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

You can read the full privacy policy here: https://www.cloudflare.com/public-resolver-mobile-privacy/

The short answer is we really don't want to have data. We store bits of it for aggregate analysis and debugging, but the goal is to not be able to map traffic to individual people as quickly as possible.

There are a few reasons:

1. When you use WireGuard as a VPN your device is connecting to wherever you happen to have hosted your server. Cloudflare's PoPs are located in 165 different Internet exchanges and ISPs, giving you a pretty good chance to be closer to you wherever you are in the world.

2. We (Cloudflare) have tech through our Mobile SDK product which can optimize the actual way the Internet TCP traffic is mapped into UDP.

3. We also have Argo, a technology for optimizing the routing of packets through the Internet which will be released as Warp+.