HNHacker News
TopNewBestAskShowJobs

eastdakota

11,162 karma · joined December 6, 2010

A little bit geek, wonk, and nerd. Repeat entrepreneur, recovering lawyer and former ski instructor. CEO & co-founder of CloudFlare. [ my public key: https://keybase.io/eastdakota; my proof: https://keybase.io/eastdakota/sigs/_uDY0ZsLTEWaNu5daRtuwzZtJDJJrtGS4uXoYxwI634 ]
submissionscomments
eastdakota··on An Uber-like CDN
Travis built RedSwoosh (https://en.m.wikipedia.org/wiki/Red_Swoosh) and then went on to build Uber. Now someone saw Uber and claims it inspired them to rebuild RedSwoosh. ¯\_(ツ)_/¯
eastdakota··on Ask HN: What's your favorite illustration in computer science?
The Elliptic Curve explainer GIF in this blog post:

https://blog.cloudflare.com/a-relatively-easy-to-understand-...

Maybe this image if the URL doesn’t get munged:

https://blog.cloudflare.com/cdn-cgi/mirage/551bd7d005a1232db...

eastdakota··on The State of HTTP in 2022
No they don’t.
eastdakota··on Boeing’s last 747 is rolling out of the factory
My favorite seat was actually on the lower level. The furthest forward window seat on either side (usually 1A or 1K) was unique. It’s directly below the cockpit and the fuselage is curved at that point so you get the almost pilot-like view out the window of facing forward.

https://www.seatguru.com/airlines/Lufthansa/Lufthansa_Boeing...

eastdakota··on Cloudflare servers don't own IPs anymore so how do they connect to the internet?
Fun fact: the first product we announced to celebrate Cloudflare’s launch day anniversary was a IPv4<->IPv6 gateway:

https://blog.cloudflare.com/introducing-cloudflares-automati...

The success of that convinced us we should do something to improve the Internet every year to celebrate our “birthday.” Over time we ended up with more than one product that met that criteria and timing, so it went from a day of celebration to a week. That became our Birthday Week. Then we saw how well bundling a set of announcements into a week was so we decided to do it other times of the year. And that’s how Cloudflare Innovation Weeks got started, explicitly with us delivering IPv6 support back in 2011.

eastdakota··on Cloudflare servers don't own IPs anymore so how do they connect to the internet?
¯\_(ツ)_/¯

Another perspective is that the connection of an IP to specific content or individuals was a bug of the Internet’s original design and thankfully we’re finally finding ways to disassociate them.

eastdakota··on Ask HN: Learning about fundraising as first-time tech founders
My thoughts…

1. How much and at what valuation?

The answer to this is harder to think about with convertible notes, so I’d tend to think about it the way the VC in your first priced round will think about it. For them, today, they’ll want to, after the round, own ~20% of the company. “Today” is important because that number will fluctuate. A year ago, when money was flowing freely, that number may have been as low as 10%. In a few months, if things tighten up further, it may get as high as 30%. But my sense of the market today is 20%.

While it seems wacky, everything else in your first question then flows from this. If you raise $1M, and the VC wants 20%, then your valuation after the round closes (post-money valuation) is $5M. Raise $2M and it’s $10M. Raise $3M and it’s $15M. Etc… to some rational limit.

So the two numbers you’re really trying to figure out are: 1) how much the VC you want to talk to targets owning in your company; and 2) how much you need to get to the next milestone. If for #1 the answer is greater than 20% then it means either VCs aren’t as excited about you or venture markets have even further seized up. For #2, once upon a time I’d probably have said think about what you need for the next 18 months. Today, as I think we’re headed into tough times, I’d probably be thinking about what you need for 24 – 30 months.

By the way, at Cloudflare we raised our first round in 2009, the last period where venture markets were really seized up. In our first round we raised $2M and sold the VCs ~30% of the company. But 10 years later when we went public, in spite of raising another $200M+, the founding team still owned 25%+ of the company and held super voting shares giving us full control. So sweat these fund raising questions a bit, but mostly just focus on building a great business.

And, again, this is assuming venture not angels. And assuming a priced round, not a SAFE (convertible debt). But it can provide a good mental model to think about what you’ll do when you get to your first VC-led round.

2. Financial projections?

Focus on costs, not revenue. Assume you’ll generate no revenue. Think about how long, with that assumption, whatever you raise will last you. Today (again, winter is here or coming soon) think 24 – 30 months until you can raise again.

3. EU or US investors?

10 years ago the answer probably was US. Today venture is much more distributed. I’d think less about where and more about who. And think about the individual, not the firm. It’s so much easier having conversations with people who “get” your space. At Cloudflare, we made a list of the top 10 cyber security investors. We then found ways to meet those 10 people. The number two person on our list offered us a term sheet within 15 minutes of the start of our conversation. Rest is history.

eastdakota··on CloudFront vs. Cloudflare, and how to reduce response times for both (2021)
Wanna bet?

https://www.buzzfeednews.com/amphtml/johnpaczkowski/amazon-p...

https://amp.theguardian.com/media/2010/dec/01/wikileaks-webs...

Etc etc…

eastdakota··on Microsoft bakes a VPN into Edge and turns it on
The motivation is to keep up with Apple who themselves are trying to distinguish themselves from Google. Doesn’t need to be sinister. If your primary business model doesn’t depend on tracking people to sell ads, and you’re competing with someone else whose does, then leaning in to making the use of your software/hardware more private makes sense.
eastdakota··on Cloudflare Hardware Keys (Yubico Partnership)
More details: https://blog.cloudflare.com/making-phishing-defense-seamless...
eastdakota··on Turnstile: privacy-preserving alternative to CAPTCHA by Cloudflare
This is yet another example of Cloudflare centralizing the web. I’m tired of this. Sure the only previously viable solution was ReCAPTCHA from Google. But it’s Google. I depend on them for search. And, sure, their business model depends on them being able to track me online. But I know them. And it’s hard for me to live without them. So I’m ok with depending on them, but I worry about further centralization of the Internet if there’s an alternative. At the end of the day, I like the Internet how it is and how I’ve gotten used to it. Facebook is clearly evil, but I still check them from time to time to keep up with my friends, but a lot less than I used to. I, of course, need to use Google so even though their business is inherently about tracking me, what’s the alternative. But Cloudflare, they’re new. They disrupt what I’m used to. They add another player to the mix. So how dare they centralize the Internet?? This is total BS. I’ll stick with ReCAPTCHA.
eastdakota··on Cloudflare Calls
“Pardon me, Cisco”: https://youtu.be/T47T_mG7YbU
eastdakota··on Zero Trust SIM
That’s the idea: the employer pays for the data you use to do your job.
eastdakota··on Zero Trust SIM
Except it’d be the end of a $20B company that I have a huge stake in ensuring doesn’t end. So, so long as I’m CEO, there’s no way in hell that’ll happen. If all you believe in is my economic interest, it’s far more lucrative to be the trusted, private network over time than any alternative. And so we’ll invest like crazy to ensure, even if compelled, we wouldn’t have the ability to compromise the integrity of the data flowing through our network.
eastdakota··on Cloudflare Beta (2009)
A bit more about this as I’m remembering. Cloudflare’s original “data center” (which was really just a single server) was located in Chicago. We had the zip/postal code for Project Honey Pot participants from when they signed up so we emailed anyone within a certain radius around Chicago to be our first beta testers. We knew they were the folks most likely to have acceptable performance.

The original way you signed up for Cloudflare was to give us your GoDaddy username and password and we’d login, slurp the DNS records, then update the name servers. It was magic when it worked. But it was almost too easy so if something broke people didn’t know how to undo what we’d done. Worse: sometimes we’d miss a DNS record like an MX record and be unable to even contact the user.

The crazy thing is we emailed people basically with the content on this page and asking Project Honey Pot users to give us their user names and password. A scary number of people just did without asking any questions.

We put this page up to prove this was a legitimate project after a (scary) few people asked us: “How do I know this isn’t phishing??”

Fun to find it still kicking around 12+ years later.

eastdakota··on Cloudflare Beta (2009)
Wow. That brings back memories.
eastdakota··on Cloudflare has replaced Nginx with in-house, Rust-written Pingora
Me too. And it's a big reason I'm excited about Rust.
eastdakota··on Cloudflare has replaced Nginx with in-house, Rust-written Pingora
Lee actually looked at HAProxy when we were building the first prototype of Cloudflare but found he could get better performance and extensibility from NGINX. Things obviously evolved, but we considered HAProxy early on and decided to go another way.
eastdakota··on Pingora, the proxy that connects Cloudflare to the Internet
We are planning on open sourcing it. That's mentioned in the post near the end.
eastdakota··on Blocking Kiwifarms
Yes, as noted in the post if you read to the end, I am very concerned about that.
eastdakota··on Blocking Kiwifarms
Reading over the comments I see everyone thinking this is about “free speech.” It is not. It’s about what in the US you’d call “due process” and in all the rest of the world you’d call “rule of law.”

Our decision today was that the risk created by the content could not be dealt with in a timely enough matter by the traditional rule of law systems.

That’s a failure of the rule of law on two dimensions: we shouldn’t be the ones making that call, and no one else who should was stepping up in spite of being aware of the threat.

Encourage you when these issues arise to think of them in the rule of law context, rather than free speech, in order to have a more robust conversation with frameworks that have an appeal and applicability across nearly every nation and government.

eastdakota··on Blocking Kiwifarms
Because we’re a U.S.-based company subject to SESTA and the one site in question we took down affirmatively told us they were violating SESTA. SESTA is a very bad law. But, if you’re violating it, don’t wave that fact in the face of your infrastructure providers who are liable under the law for providing service to you. We continue to work to overturn or repeal SESTA.
eastdakota··on Cloudflare's abuse policies and approach
No, these are hard and important issues. I trust our team to think them through and would never want to outsource or shirk that responsibility. Having what you do matter is the highest job satisfaction. We may not always get it right, but I’d never not want to be in the arena.
eastdakota··on MacBook Air M1 screen crack for no apparent reason
I had a brand new MacBook Air M2 whose trackpad arrived cracked. Didn’t even know there was glass in the trackpad. For the first few hours of using it I thought it was a hair or something that had fallen on it. Kept trying to wipe it away and triggered all sorts of gestures.
eastdakota··on The mechanics of a sophisticated phishing scam and how we stopped it
Yup.
eastdakota··on The mechanics of a sophisticated phishing scam and how we stopped it
You get a feed of what’s registered at a velocity that’s not publicly available.

In addition to that, controlling the registrar also allowed us to take advantage of features like registrar and registry locks managed by policies we had full control of. Auditing the policies of other registrars, even the supposedly secure ones, freaked us out enough to spend the money to build our own.

eastdakota··on The mechanics of a sophisticated phishing scam and how we stopped it
We’re tightening up controls and not letting any non-whitelisted/approved VPNs access any of our internal tools. This has been a feature of Cloudflare Access. We just hadn’t enabled it ourselves.
eastdakota··on The mechanics of a sophisticated phishing scam and how we stopped it
Oh, we’ve got that… stay tuned…
eastdakota··on The Problem with Speed Cubing [video]
I really thought this was going to be about something else which I am curious about. It seems as a complete layman to Speed Cubing that some ways the cube can be mixed (shuffled? randomized?) will be harder to solve than others. For experts in Speed Cubing, is that accurate? And, if so, among elite speed cubers how much are the records just a matter of the luck of the draw (mix)?
eastdakota··on Ask HN: Weird SSH Probes from Cloudflare IPs
That page is for the IPs that customers should whitelist as the source of traffic from our proxy services. These IPs are for Cloudflare WARP (our VPN-like app) and should not be whitelisted by customers in the same way. That's why they're not on that page.
← PreviousPage 5 of 21Next →