Yes please!

This is another reason why connectivity is so critical - arguably foundational - to the future of autonomy; line-of-sight detection of hazards and incidents will always be inferior to geospatial data about hazards.

Literally every post and piece I’ve seen about Bluesky being an “echo chamber” so far has been a crystal clear example of projection.

Our team at HAAS Alert are regular consumers of all the incredible work you and your team are doing at TechCrunch - we have a weekly internal newsletter of key stories in and outside of transpo and TC is *always* a primary source for us. Indispensable!

Welcome!

This means that local responders, cities, counties, and states are the ones that have to solve this for AVs, not the other way around.

Even the recent California regulation on AVs (AB 1777) places the responsibility for avoiding emergency incidents on the *emergency responders and managers,* requiring first for them to communicate geofence data for roadside incidents first, and then for AVs to avoid/vacate the area after 2 mins.

Indeed, to the extent that any regulatory environment exists around robotaxis and AVs, they tend to be both hyperlocal and deliberately intended to *facilitate* deployment rather than constraining or regulating it.

What is your daily schedule like? I’m pretty impressed at your ability to juggle TPM, real-time discussion, and something as studious and focused as woodworking.

Actually, for me it was seeing someone post on Twitter that one positive of Bluesky was seeing daily posts from @jamellebouie.net again. That did it for me. One I got here I realized how much of what I loved at Twitter actually migrated/settled over here.

It’s truly shocking to see how much better the experience is on this app compared to the alternatives.