Implemented SMS replies to schedule confirmations on One Final Message today. Should make confirming when cell service is spotty more reliable than relying on the web interface. And unlocks sending confirmations to burner flip-phones!
save it to your phone and share the QR code this saturday!
We launched a whole new way to get organized. blog link in comments
cool. i didn’t like you anyway
Taco cat backwards is taco cat but dog food lid backwards is dildo of god.
I built a thing
spectrumcodex.com
A red line I won’t cross: it’s your data, not ours
Like the Darmok and Jalad episode of Star Trek - communicating this way just seems natural to me. Higher signal to noise - greater bandwidth.
Thinking about Gestalt Language Processing. I don’t usually spread or share current memes, but I often find myself looking for an animated GIF or image to reply to something. They capture a whole mood that a few words can’t capture.
Orgasmatron 3000
I wonder if the Tyburn Tree is getting excited…
We provide The Beacon plan at no cost for 30 days. Please share this information with those who may need it, including solo female travelers, rock climbers, immigrants fearful of ICE, and others who may benefit from a rapid response to their inactivity
Watching the new season of Cross and that billionaire they killed looked a lot like Thiel. good.
That's the problem. Everyone has it. Almost nobody's solved it.
It's not urgent until it is. And when it is, it's too late.
onefinalmessage.com
Launched One Final Message recently.
It's been quiet, which tracks - nobody's excited to plan for their own unavailability.
But every person I've talked to about it has the same reaction: they pause, then say "I really should set something up," then make a mental list of data only they know
Drop an album that was important to you when you were 19.
Claude just output:
"The data flow is correct on paper. Let me now check the..."
on paper? really?
#claudecode
not too big. it was always planned. basically changing the plumbing between two workers - instead of going through a service binding, abstracting it through a queue.
better retry and dead letter semantics. easier scaling as well.
thanks. I think developing this is my way of “fighting the good fight”
For most apps, a failed delivery is a minor inconvenience. For us, it means someone's final message doesn't arrive.
Deliverability isn't a feature. It's the product. We don't get a second chance at the moment that matters, so we build like it.
#buildinpublic
Rearchitecting the delivery pipeline at @onefinalmessage.com this week. Moving from a Durable Object coordinator pattern to a messaging queue for better delivery guarantees.
I have a legitimate fact based question that can be easily answered by consulting a reference source on the internet but I think I will throw it out to social media so unhinged lunatics can respond…
We've added a canary statement for transparency
We publish a regular, dated statement that we haven't received any secret government orders. If it stops being updated, that silence is the signal.
Your messages deserve that kind of accountability.
onefinalmessage.com/canary
The desktop Safari video element is giving me heartburn.
#buildinpublic
Living your life is a political act.
We've built something that we are genuinely proud of.
It's called One Final Message — a service that makes sure your most critical information reaches the right people when you can't deliver it yourself.
It's not only for personal "just in case" — journalists, activists, whistleblowers, anyone in uncertain circumstances who needs a failsafe for sensitive information. Plans start at $3/mo with a free 30-day trial.
onefinalmessage.com
You store encrypted messages and choose your recipients. Simple check-ins confirm you're okay. If you ever stop responding, we verify through multiple channels before delivering anything. End-to-end encrypted throughout.
