Honored to see my piece recognized by the Dev Community. I am grateful for the conversations and insights it provided. It’s always the small details that teach the biggest lessons.
Article link: dev.to/johneliud/a-story-abo…
@dashaun
Congrats to our top authors this week! 🏆
@Lissy_Sykes, @aryanc193, Melvin Cheah, Polliog, @m4rri4nne, Warren Jitsing, and John Eliud Odhiambo.
This week's lineup features a massive frontend framework comparison, insights on replacing Redis with PostgreSQL, and much more.
dev.to/devteam/top-7-feature…
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
A 3-hour outage, 2 hours spent just finding the error across 12 servers. I built a Go log ingestion engine that never silently drops a log, and wrote up what I learned.
Link: medium.com/@johneliud4/where…
John retweeted
Not just PHP. Node.js has also announced security releases for October 21, with HIGH-severity vulnerabilities affecting its 26.x, 24.x and 22.x release lines.
If you run either stack in production, keep an eye on official advisories and apply patches promptly.
Security maintenance doesn't stop at your application code. Your runtime matters too.
Node.js advisory: nodejs.org/en/blog/vulnerabi…
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
John retweeted
My entry point into btcsuite has been "rpcclient".
Tracing how it builds JSON-RPC requests, uses Go’s "net/http" to communicate with a Bitcoin node, and handles responses and errors.
Connecting the API to the underlying communication, one piece at a time.
John retweeted
Major cheat code in life: Understanding you can reinvent yourself at any time. New habits, new standards, new gym, new clothes, new friend group, new career, etc. There's no rule that says you have to stay the person you've always been. You're allowed to decide... "I'm done being this version of me."
John retweeted
Na btw jiamini. Believe that you can do it, believe that nothing is out of reach for you, believe that you already have it. Don’t ever think hufiki na hutoshi, that’s some lame shit looking down on yourself!
Sending lots of love to the Apple community on my last day as CEO. My title changes tomorrow, but the love I have for the Apple community never will. Thank you for being a constant source of inspiration. My gratitude is endless, and I’m excited for the next chapter!
John retweeted
Finally.
$1M+ in a month.
Thank you to every partner and user who made this possible.
The best is still ahead.
To spend your stablecoins on everyday payment ⤵️
play.google.com/store/apps/d…
To the UX engineers out there, is this acceptable?
I didn't want to introduce any reCAPTCHA library and instead opted for the simplest countermeasure possible.
Portfolio: johneliudodhiambo.vercel.app
John retweeted
JUST IN: AI agent asked to book a gym class finds vulnerability in the gym’s software, & kicks another member off the waitlist so its user could have the spot.
John retweeted
Building with Ruby? Curious about Rails? Or looking to connect with fellow developers?
Join us for another community meetup as we discuss about building startup MVPs with Rails and component-driven UI with ViewComponent
📅: July 30
🕖: 7 PM EAT
🔗: meet.google.com/hja-erkd-zbb
John retweeted
Kimi K3 has received far more love than we expected, and our GPUs are feeling it.
Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected.
We're adding capacity as fast as we can and will reopen new subscription spots in batches.
Going forward, we'll also split membership into two more focused plans: Kimi Membership for Kimi Web, App, and Work; and Kimi Code Membership for coding workflows. This will help us match compute more precisely and keep the experience stable.
Thank you for your patience and understanding!






























