Just shipped real-time chat for Findora, a Lost & Found web app I’m building for my university campus.
The goal is simple: help students and staff reconnect with lost items faster through direct, in-app communication between finders and owners.
Built with Socket.IO
I tipped somebody in Ghana using @myhappr and he just withdrew his earnings and got some credited instantly. 🤝
Claim your page today, share your page with your fans and start receiving support across the world.
Visit myhappr.xyz
Trusted and verified 🤝
Happy New Month from @myhappr
Yo chat, Introducing my startup @myhappr
Basically Buymeacoffee alternative for Africans.
> Create your account
> Add your payout details
> Start receiving tips/support from other countries too.
> Withdraw your earnings.
Checkout the platform out. myhappr.xyz/
Day 1.
Finally started building Vestlee 👨🏽💻
Been dealing with the same annoying problem for way too long and I got tired of acting like it’s normal 😭
So instead of complaining about it again… I’m building.
This one might actually be crazy.
Stay tuned.
We heard you,
You wanted faster access to your digests. So we built it.
Push notifications are now live on Brevpulse. Get alerted the moment your daily insights are ready... with a quick summary at a glance.
Head to app.brevpulse.xyz and turn it on.
Exactly-Once in Distributed Systems 🔑
Today I learned why exactly-once is so tricky: true exactly-once is impossible. Networks fail, messages get lost, and retries can duplicate actions.
The way systems handle it? Combine retries, idempotency keys, and transaction states to
simulate exactly-once.
Why it matters: in critical systems like payments, duplication or loss can be disastrous. Understanding this makes you think beyond code about reliability, trust, and real-world consequences.
Think your background jobs in Node.js are really running in the background? Think again. If your worker shares the same process as your web server, CPU-heavy jobs can still block requests. True decoupling = separate process.
We’ve become spoiled by HTTPS.
OAuth 1.0 was designed for a hostile internet. It assumed the network was compromised, the wire was tapped, and the environment was out to get you.
It was clunky, difficult, and brilliant.
A thread on why we should still study "heavy" protocols.
Implementation was a nightmare.
One millisecond of clock skew or a misplaced parameter meant a 401 Unauthorized.
We traded Developer Experience (DX) for Protocol Resilience. OAuth 1.0 didn’t care if your network was "secure" it carried its own armor. 🛡️
The takeaway for modern engineers?
Good system design starts with environmental assumptions, not convenience.
Legacy protocols feel heavy because they solved harder problems. Modern systems quietly rely on the scars these protocols earned.
Resilience > Comfort.
Just shipped real-time chat for Findora, a Lost & Found web app I’m building for my university campus.
The goal is simple: help students and staff reconnect with lost items faster through direct, in-app communication between finders and owners.
Built with Socket.IO