Tech Lead @Cloudflare Basin and K2. Prev co-founder @ArroyoSystems, @LyftEng, @GetSift.
Berkeley, CA
Joined May 2008
- Tweets877
- Following381
- Followers1K
- Likes1.6K
Micah Wylde retweeted
Proud that @Cloudflare through the #AthenianProject embedded security engineers with the teams at critical U.S. news organizations to ensure they could report tonight’s election results without fear of disruption by cyber attack. cloudflare.com/athenian/
This discourse is much easier to understand when you realize everyone engaging in it is 23
hot take: SF *isn't* a "transient city"
the pandemic caused a massive one-time turnover in the tech scene so now you have a New Tech Scene that has less continuity with the old one
but otherwise the city doesn't really have a particular propensity to people leaving
7
457
If you missed my talk at Connect about how agents are using Cloudflare Basin, it's now available to stream:
Your agent can't answer a question with data you didn't collect.
In @mwylde's Cloudflare Basin demo, Claude finds missing checkout events, adds instrumentation, and creates a pipeline to collect them.
See what changes when agents can build the data infrastructure, too.
1
6
450
Fun looking back at old HN comments from the early days of Theranos. medman77 had them completely clocked way back in 2013
Since we’re all talking about Amanda Seyfried right now you should go watch The Testament of Ann Lee, where she plays the main figure of Shakerism and also it’s sort of a musical
1
226
Micah Wylde retweeted
today we're launching @polylane for @Cloudflare
let proactive agents continously watch your workers, durable objects, workflows, etc.
they fix bugs, improve performance and handle all your alerts
we have this on our own prod account and we merge ~8 pull requests every day
Day 3 of Cloudflare connect! Come hear me talk about agents and data infra at 1:50 if you’re around.
Micah Wylde retweeted
Two classes extremely bad cyber vulnerabilities disclosed in the last 24 hours. The first potentially impacts everyone online. The second impacts nearly everyone running a server.
tl;dr: Everyone should upgrade their OS and Browser as soon as possible. If you run a server you should upgrade PHP (or ensure it’s removed if you’re not using it) as soon as possible.
The first class of vulnerabilities is a set of root TLS certificates that were discovered to have a trivial private key. Literally the number 4. These roots were controlled by #eMudhra. The problem is that with that an attacker could create a certificate and, if they could get in the traffic flow, intercept traffic to any site or service. The solution is to stop trusting certificates issued by these vulnerable roots. Upgrading your browser and OS is the fastest way for most Internet users to do this.
The second class of vulnerabilities doesn’t apply to most consumers directly, but does apply to most anyone running a server. These vulnerabilities have been dubbed #php2shell. PHP is one of the most widely used web programming languages. It’s estimated 70% of websites run on PHP. These vulnerabilities allow an attacker to send a crafted set of queries to a server running PHP and potentially take over the server. From there they could potentially read, modify, delete, or repurpose anything on the server. The solution is to upgrade PHP to the latest version ASAP. Even if you’re not using PHP for your web development, it’s often included by default. So make sure it is either upgraded or fully removed.
@Cloudflare received advanced warning of both of these classes of vulnerabilities. We’ve ensured that where we act as a proxy we are no longer trusting the vulnerable roots. We are also reviewing certificate transparency (CT) logs for any sign the vulnerability was exploited before its disclosure. We have not found any evidence but CT logs are not perfect and a sophisticated attacker who knew about the weakness could have exploited it without a new certificate being logged.
For the PHP vulnerabilities, we have deployed mitigations available for all customers for free. Because of the complexity of the vulnerabilities and number of ways it can be exploited, we also released new WAF capabilities that are unique in the industry to catch the exploit based on the response. These too are available for every Cloudflare customer for free.
Even if you are taking advantage of Cloudflare’s protection, it is important to upgrade your OS, browsers, and PHP installations as soon as possible. We can provide a strong bandaid, but the best protection is to fix the underlying problem.
If you’re interested in learning more, you can read our blogs:
Vulnerable roots: blog.cloudflare.com/emudhra-…
PHP vulnerabilities: blog.cloudflare.com/php-vuln…
it's easy to get used to it when you're inside, but stepping back it's crazy how much is happening at cloudflare every single week
So cool to see true systems engineering suceed. One regret of my career is never applying to oxide
Our $445M Series D -- and a wild milestone
oxide.computer/blog/our-445m…
Micah Wylde retweeted
Cloudflare K2 is an interesting design. blog.cloudflare.com/cloudfla…
Instead of rebuilding replication, consensus, brokers, etc, it pushes much of that complexity down to R2.
Batch in memory. Write immutable segments. Accept ~1s produce p99.
It reminds me of SlateDB, which makes a similar trade-off with S3.
If your workload can tolerate the latency, let object storage do more of the distributed systems work.
If you're a startup, buy a datalake. Go into debt if you have to.
(not that you have to with Cloudflare Basin, it's basically free at pre-PMF scale)
Micah Wylde retweeted
Basin Pipelines ingest limit just jumped to 1 GB/s. Handle massive telemetry volumes in one stream now.
developers.cloudflare.com/ch…
also I hear we got someone pretty incredible for the closing concert but I'm not allowed to say who teapaw.org/yayalexisgay/status/21…
ok so @Cloudflare asked me to make them a promo video for Cloudflare Connect and this........ is what I made 😇
1
87
If you're excited to learn more about Cloudflare Basin, have I got the conference for you! Save $100 on registration before 10/5 using code CONNECT100
cloudflare.com/connect/
The Cloudflare Data Platform has been in beta for the past year and has helped amazing companies like @anomalyco ingest, store, and query their analytical data. Today, for @Cloudflare Birthday Week, we're going GA. And we have a new name: Cloudflare Basin.
had this internally for a while, so useful for debugging worker perf/uptime issues. O11y can be hard with serverless, but this shows the upside: all reqs out of a worker go through the runtime, so we can inject automatic trace ids, and it just works. Incredible ship by the team!
Cloudflare Tracing is now in open beta 🚀
Our teams rely on traces everyday to understand what happens to a request as it moves through our platform. Cloudflare Traces brings that same visibility to you.
✅Get automatic spans throughout the entire request
✅Control what gets traced with trace rules
✅Propagate traces across your stack a la W3C trace context
✅Query traces through our dashboard, SQL API or Cloudflare MCP
✅Export traces to any OTLP-compatible destination
Micah Wylde retweeted
“No,” sobs @awscloud. “You can’t do that without spending three days ducking with IAM, region problems, and reading contradictory documentation scattered around our site first…”
📣 cloudflare K2 is here and is in open beta! k2 lets you send events to a K2 stream, which stores them as an ordered log.
K2 implements a partitioned, durable log on top of R2 object storage (read: built to scaaaale!)
blog.cloudflare.com/cloudfla…