P24L
banner
p24l.bsky.social
P24L
@p24l.bsky.social
me
"The worst was yet to come, he knew. Already he could feel a world of trouble waiting for him behind the next door, but the worst that could have happened was also already behind him; the thing not done, which could have been – which he would have had to live with for the rest of his life.”
January 6, 2026 at 5:46 PM
The tension here is mild. Deliberately so.
The story tightens slowly, quietly, almost politely.
And because of that, the ending doesn’t shock — it lands.
January 6, 2026 at 5:46 PM
I didn’t know about the Magdalen laundries in Ireland before reading this book.
The book doesn’t lecture or explain.
January 6, 2026 at 5:46 PM
I didn’t know about the Magdalen laundries in Ireland before reading this book.
The book doesn’t lecture or explain.
January 6, 2026 at 5:46 PM
něco o zrní
December 31, 2025 at 11:12 AM
dot-com was a bubble too, but the tech actually worked out in the end.
do you think it’ll be different with LLMs?
December 31, 2025 at 11:08 AM
Talk. Don’t push.
Listen more than you speak.
No surprises, no cowboy moves.
Good deals aren’t won in a moment — they’re built, slowly, by people who plan to still be around.
blog.hyperlimit.app/posts/howto_...
Good Deals Don’t Make Noise
Real-world lessons from long-term business negotiations. No theatrics, no paper-slamming — just trust, timing, and knowing you’ll have to sit at the same table again.
blog.hyperlimit.app
December 30, 2025 at 5:59 PM
5/6 Start higher than where you expect to land.
Not ’cause you’re greedy.
But ’cause deals need room to breathe.
Cash helps — but it’s rarely the real prize.
December 30, 2025 at 5:59 PM
4/6 If you’re in a long-term deal, think long-term.
Before you negotiate, ask yourself:
“What happens if this goes sideways?”
Then take a few steps like you mean it — and let the other side see it.
December 30, 2025 at 5:59 PM
3/6 Contracts are like a fire extinguisher.
Good to have on the wall.
Everybody sees it.
Nobody wants to grab it unless the place is already burning.
December 30, 2025 at 5:59 PM
2/6 When the other guy fucks up, it ain’t time to slam signed papers on the table.
’Cause sooner or later, you gonna fuck up too.
And page 47 won’t save you then.
December 30, 2025 at 5:59 PM
exactly, yeah — looks like that’s the way to go for now.
October 5, 2025 at 5:34 PM
makes sense — i like the service-proxied vision a lot.
my angle was more minimal: push relay fed from Jetstream public stream,
no oauth, just APNs/FCM dispatch.
basically a public notif layer we could prototype today.
October 5, 2025 at 5:26 PM
Or @mackuba.eu might know? Don’t really want to rely on a poller with app password.
October 5, 2025 at 5:08 PM
Looks like push has to go through AppView for now.

Wondering if a parallel push layer could work — basically a community-level registerPush endpoint + Jetstream-based dispatcher for APNs/FCM.
Would that fit into your infra experiments?
October 5, 2025 at 5:08 PM
Limit - reply 2
October 2, 2025 at 5:55 PM
Limit - reply 1
October 2, 2025 at 5:54 PM
i know you keep the quality bar high ✨
but even a minimal client-side oauth lib would already shift the ecosystem in a safer direction.
October 2, 2025 at 7:00 AM
and honestly, current practice across alt clients is kinda scary.
app passwords everywhere. it’s fragile + bad UX.
if you give them just proper oauth client flow (plus optional backend piece), the overall security bar goes way up.
October 2, 2025 at 7:00 AM
on security: many bugs only show up once devs actually start using the code.
that’s why my PRs to your AtProtoKit were mostly trivial fixes — i was the first one hitting those paths. early use = early feedback.
October 2, 2025 at 7:00 AM
if you’re building all 3, the client-side part feels like the biggest win + lowest effort.
i hacked a dirty but working version for ATProtoKit pretty fast, and it already made a big difference.
so maybe shipping that first, standalone, could unlock adoption sooner?
October 2, 2025 at 7:00 AM