We need to stop abandoning politics to elections and buffoons. We need to ask political questions all the time, whether we are in church, school, market....even our love lives. If we dont understand the messed up economy, we won't understand why our youth hesitate to marry.
The banter years are over! 😂
You are smiling? Yeeees... bro!
Patience paid off for the Arsenal faithful, and now deserved champions 🏆
Congratulations to the team and big respect to all the Gunners worldwide ❤️
The UI era is ending. 🪦
For 70 years we designed computer interfaces. Mainframe, CLI, GUI, Touch.
But with AI, the interface is disappearing. What will come next?
My talk from @mastra's conf this week:
Agents are going to use software 100X more than people will in the future. As a result, enterprise platforms will become headless and be able to work with any agent on or off platform. If you don’t do that you’re DOA.
What some have missed is that this creates vastly more use-cases for these platforms than even existed pre-AI. This isn’t zero sum. Software value props have traditionally been capped at the number of users you have in a company. Agents have no upper limit.
We’re going to run agents to process data at a scale humans never could, they’re going to be running 24/7 in parallel doing work for us, and they can integrate workflows across systems to generate all new value propositions.
Once you embrace this approach, it becomes obvious how much more upside there is.
Read this through to see the reasons.
1. USSD sessions carry state and session data
Every request from Interswitch to your endpoint comes with a payload: session ID, phone number (MSISDN), current menu level, user input, etc.
Even a “fetch” operation still needs that context to know whose data to retrieve.
GET requests don’t have a body, so you’d be forced to push sensitive identifiers into query strings which is a very high security risk.
2. Query strings are a security liability
Phone numbers, session tokens, and transaction references sitting in URLs get logged everywhere: proxies, load balancers, Nginx access logs, monitoring tools.
POST bodies are not exposed the same way by default.
For a payment system, that is a non-negotiable hygiene requirement.
3. Interswitch’s gateway is built around a request / response dialogue model
Their system sends a payload to your server at each USSD menu step and expects a structured response back.
This is not traditional REST API design.
They are triggering handlers, passing context, and expecting replies. The HTTP verb semantics (GET = read, POST = write) simply don’t really apply here.
4. Idempotency and retry behaviour
USSD sessions drop. Gateways retry requests. Networks are unreliable.
GET being safe doesn’t solve much at this layer.
POST forces you to consciously design idempotent handlers, which is exactly what you want in financial systems.
5. Payload size and flexibility
USSD flows often carry more than a single parameter: session history, user tier, levy codes, amounts, and state transitions.
POST gives you structured payloads (JSON or form body).
GET quickly runs into URL length limits and rigidity.
Yeah, this is a known bug on X's web browser player—videos are loading twice with a slight offset, creating the echo effect on audio.
The media team already has reports and is pushing a fix. Refreshing the page or switching to the X app usually clears it for now. Thanks for flagging!
What the Artemis II astronauts did over the last 10 days was a testament to their bravery. And the fact that they traveled farther from Earth than anyone ever has, re-entered our atmosphere at more than 24,000 mph, and splashed down safely was a testament to human ingenuity. Thanks to everyone at @NASA for making this mission possible, and for taking us along for the ride.
I was happy to meet Chief Justice Emeritus and presidential aspirant David Maraga as he left Nakuru town. He's on a countrywide tour to popularize his presidential bid and encourage young people to register as voters.
@dkmaraga