Tosin retweeted
I created an AI Smart Glass to help blind people walk without a cane or a guide 👓
But this is not like the smart glasses people are used to seeing
Because this Glass combines AI, sensors, and GPS to help the user detect things in front of them, avoid obstacles, and know their location
But the most amazing thing is if the user gets lost, the GPS tracking system can help locate where they are from anywhere, and then send the location to the phone of the person taking care of them via WhatsApp or Email 📲
And now I am further developing it to a new level of AI + Voice, so it can speak with the user and also help them understand their surroundings
I have put the video showing how it works completely in the comment. 🎥
SHARE this project 🤝🔥
Let the world see what a young Nigerian can build
Tosin retweeted
🚨 DID YOU KNOW?
If you own a business in the UK or you’re thinking of starting one, you could win contracts from the UK Government and public sector organisations.
The contracts finder website lets you search for:
✅ Government contract opportunities
✅ Local council contracts
✅ NHS and public sector tenders
✅ Future procurement opportunities
✅ Previously awarded contracts (to see who wins and how much)
The best part? It’s completely FREE to use. You can search without an account, and creating one lets you save searches and receive email alerts for new opportunities.
This is a great resource for businesses offering services such as: cleaning, catering, construction, healthcare (tender writing) and many more
Many people in our community don’t realise these opportunities are publicly advertised.
Check it out here: gov.uk/contracts-finder
Share this with another Nigerian entrepreneur in the UK, you never know whose next big contract it could lead to 🇳🇬🤝🇬🇧
If you need any more information or support writing tender for any of these contracts, DM let’s plug you.
SKthePlug🔌
Tosin retweeted
Humanity 😭❤️
So this mum posts about her son Levi who has been fighting leukaemia and is always in the hospital.
But this time, this year he will be celebrating his birthday at home but sadly doesn't have any friends cos he is always in d hospital.
Now she posts and asks if people can just drive by and say hello and happy birthday to her son between 2 and 3pm and this was how people showed up for her.
If you're not a very technical person and would like to understand what he's saying, as someone whose daily job involves making content as simple as possible while still maintaining the intent, let me explain it to you
Whenever Interswitch needs to communicate with your bank 1/7
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.
1
41
















