A programmer trying to make the world a better place one line of code at a time. I also stream games and stuff. Opinions are my own. @richi.dev on bsky
Austin, Texas
Joined May 2012
- Tweets7.5K
- Following494
- Followers333
- Likes54.6K
> Approvals stay in place for unchanged code. When an otherwise unchanged stack is updated...Rebase stack now preserves approvals, even in repositories that dismiss stale approvals.
Thank geez. One of the few things I missed from Bitbucket
Stacked pull requests are generally available, letting you break large changes into smaller, focused PRs to review independently and merge together.
• Approvals persist through rebases; signed commits stay signed after rebasing
github.blog/changelog/2026-1…
"Why doesn't anyone like the Windows Store and Xbox app!"
*xbox freezes, then ask for an update for the 5th time this week*
Me, clicking the update button and checking 5 minutes later:
Richard Simpson retweeted
Most useless DM award goes to YouTube.
Hi there. We've sent you a DM
Readers added context they thought people might want to know
The DM from YouTube was that YouTube is “unable to offer further support”
x.com/aglubbable/sta…
Well that's a whole new level of Amazon fuck up. Got my package from the package locker and...it was already opened, is missing some of my stuff and has some random cosplay gear? Rip to whichever cosplayer didn't get their stuff.
I feel like both this and channels bury the lede a lil that both require their managed (or self hosted but licensed) runtime as the glue.
🚀 Introducing Open Tag
A better, open-source Claude Tag.
Works with any model, any agent harness, and fully custom agents.
Bring any Agent to Slack, MS Teams with Generative UI, Streaming, and much more!
Clone the repo and get it running in minutes
github.com/CopilotKit/OpenTa…
Powered by the Channels SDK & AG-UI
I really need GitHub to swipe bitbucket's "don't invalidate if diff hasn't changed" or make it so stacked PRs don't fall apart with Ruleset's strict approvals.
Richard Simpson retweeted
Introducing celld: a self-hosted, distributed Durable Objects and Workers implementation
- celld = V8 + S3 + SQLite + LTX+ Tokio
- programmed with exactly the Cloudflare Workers/DO JavaScript APIs and config
- order of magnitude cheaper at scale
- writes are durable before they're acknowledged, RPO=0
- only depends on an S3 compatible bucket - no other infrastructure
- ~4 MB memory per cell instance overhead
- hibernated cells cost ~nothing, just their S3 storage
- open source, Apache 2 licensed
Richard Simpson retweeted
gave up on waiting on nikita for the articles fix - part 1 is here part 2 is coming
Richard Simpson retweeted
Got logged out of corporate Slack.
My brain: Well, this is it. We had a good run. Damn.
Every. Single. Time. Without fail.
I get the idea behind this. But my takeaway from this is that SDKs at large still have a quality issue and we haven't put enough resources as a community in raising the state of the art (value on top of OpenAPI, etc...)
Knocking Bloated SDKs is super valid tho
These made me look at better auth again since it's been a while since I've worked on an Auth project and _gosh dang_ they have plugins for everything now. No excuse not to have good auth with all this.
Only other plugin I'd maybe like to see now is an OpenFGA sync plugin.
Better Auth is joining Vercel.
Vercel shares our commitment to keeping auth open source, framework and platform agnostic. Joining forces gives us more resources and room to focus on building the framework that much of the community relies on.
Together, we’ll also be able to invest more deeply in where auth is heading: a future where agents act on users’ behalf and need secure, scoped, and revocable access.
Pardon my french, but this feels like...utter horse shit? _Maybe_ there's a legit worry that being code open will let bad actors find holes quicker, but this just feels like a deceptive way to close source "business features".
Taking pot shots at open source on the way out too.
Open source is dead.
That’s not a statement we ever thought we’d make.
@calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up.
AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost.
In that world, transparency becomes exposure. Especially at scale.
After a lot of deliberation, we’ve made the decision to close the core @calcom codebase.
This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible.
We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple:
Protecting our customers and community at all costs.
This may not be the most popular call.
But we believe many companies will come to the same conclusion.
My full explanation below ↓
Richard Simpson retweeted
Today we ship Aspire 13!
Why 13? It’s a number that’s bigger than 10 but less than 14.
Seriously though, Aspire 13 marks the start of a new chapter for the project: the beginning of its polyglot era. We’re expanding beyond .NET, bringing the same model-driven, code-centric experience to Python, JavaScript, and beyond.
Check out the what's new on the new site:
aspire.dev/whats-new/aspire-…
#aspire @aspiredotdev
Richard Simpson retweeted
They have fired the staff of the CDC’s Morbidity and Mortality Weekly Report and 70 Epidemic Intelligence Service officers, who are disease detectives that respond to outbreaks.
I cannot emphasize enough how dangerous it is to dismantle our disease surveillance infrastructure.