Did not enjoy the wait for AOS!

May Clipper have a boring journey.

Stunning. They have no right to make it look so easy.

I was ready to wait until Christmas for this and now I’m not emotionally prepared!

If there’s a catch attempt I’m expecting a mild success where something goes wrong (those arms sway sooo much), but I’m optimistic about Ship reentry. Going to be great.

Thanks for mentioning this! Loving the world so far.

Curious to see what happens in the Gulf given Zack Golden’s speculation from a few days ago. Are they really going to retrieve a booster that’s hundreds of meters below sea level? Feels hard.

Unfortunate for this to happen on a high profile flight, amid all the regulatory bickering.

I’m glad my concerns about these suits were overblown! They look like a big improvement over status quo.

Pretty confused about why SpaceX released this - it’s a vague, whiney, entitled message, even if they’re right!

Parts of the regulatory process are clunky, and the goals of an environmental assessment don’t always align with the goals of SpaceX - that’s the point. I’d be concerned if the company was happy with the process.

I don’t want to write an essay right now. I know it’s messy, and the process needs to improve. I just wish SpaceX had brought receipts before starting…whatever they just started.

Wasn’t expecting such beautiful shots at midnight in the desert!

This is probably going to be so boring, but I won’t be able to look away.

This makes a lot of sense! I’m going to give it another shot with these insights in mind. I think if I frame it as a future-facing tool like you describe I’ll avoid a lot of my previous mistakes.

Thanks for explaining :)

This is really helpful, thanks!

I think I need more practice with knowing when to create a node. In the past, every single entry would look like this:

I went to [Alice] birthday party and met [Bob]. We talked about [clouds].

And that got very cumbersome. I like your suggestion of using back links to create a better summary document.

Got it, I see what you mean. Thanks for this!

I keep failing to make Zettelkasten and org-roam work for me. Do you use a single knowledge base for your whole life, with millions of tags and pages? Or should I be making separate directories for each project? Is the “daily journal” the best place to put everything, with well tagged entries?

You don’t have to answer all of those!

This is how I feel. This is a wonderful moment where a switch to Dragon is easy and safe. Starliner is probably fine, but Dragon is clearly safer right now. Who cares about ISS scheduling changes and modified Starliner certification requirements?

I just checked prediction markets and they seem to think Starliner has a 20-30% chance. I think that’s way too high.

NieR: Automata

For some reason this New Scientist cartoon lives in my head. Maybe because it challenges the way I think about the future? Or maybe it’s just cute.

Original source, by Tom Gauld

Thanks so much for doing this! I almost forgot to enter.

I wonder how predictable the thrust reduction is. I would have thought they could account for this in software, but maybe there’s too much uncertainty. Or perhaps ground tests showed the seal can fail in dangerous ways.

If NASA defers to its fallback plan, flying on Dragon, it may spell the end of the Starliner program. During the development and testing of Starliner, the company has already lost $1.6 billion. Reflying a crew test flight mission, which likely would be necessary should Starliner return autonomously, would cost much more.

Through this lens, I get why they’re taking their time with the decision.

I was firmly in the “nothing is actually wrong and the media coverage is silly” camp, so this report is pretty shocking.

If there are real engineering reasons (as opposed to anxious bureaucrat ones) that Dragon needs to rescue them, this seems like one of the bigger crises in the modern era?

Will wait for more details, but clearly I was wrong about media coverage!

I won’t be using these features, but I’m not sure there’s cause for concern. The implementation seems very sensible and legitimately privacy-centric. The LLM runs locally and is meant as an very basic email proofreader. The crypto wallet is a likely an extension of the password management tech they’ve already developed, with transaction features that some people care about.

I can see why some people want these features, and I’m glad there are new alternatives.