Pinned Tweet
Hey, I'm Favour. I write code, build platforms, and teach others how to do the same.
What I bring to the table as a Full Stack Developer:
Product: Creator of MatchNexx (AI resume optimization).
Web3: Smart contracts and dApps across Solana and EVM.
Open Source: Creator of the sleek-toast notification library and the nub stack development boilerplate.
Leadership: Tech instructor and mentor for emerging developers.
I work with React, Next.js, TypeScript, Python, and Rust. If you need someone who can architect a backend and polish a frontend, my DMs are open. Let's work.
A working code is not equal to secured code💯 – at Mpape, Nigeria
Your API returns 200 OK.
Your tests are green.
Your app works perfectly.
But customer A can change an invoice ID and access customer B's private data. 💀
Congratulations. Your API is very polite to criminals. 😂
Working code ≠ Secure code.
Exploring StrikeHound AI by @ExploitforgeLTD for AI-assisted security testing.
strikehound.ai/
#APISecurity #CyberSecurity
Fahyvor retweeted
To the men who say "no worries" while carrying 100 worries, we appreciate you.
Happy International Men's Day
Confidence I have in God?
He can change any situation from bad to good in seconds.
Keep believing and don't give up. – at Mpape, Nigeria
4
90
CI/CD - Continuous Improvement Continuous Development.
CI/CD - Continuous Integration, Continuous Integration Deployment.
Pick your own 💯✌️ – at Mpape, Nigeria
1
30
Fahyvor retweeted
𝗢𝗔𝘂𝘁𝗵 𝘃𝘀 𝗔𝗣𝗜 𝗞𝗲𝘆 𝘃𝘀 𝗕𝗮𝘀𝗶𝗰 𝗔𝘂𝘁𝗵 𝘃𝘀 𝗺𝗧𝗟𝗦.
Do you know the differences?
They all help secure access, but what they actually verify, and how they do it, is very different.
𝗢𝗔𝘂𝘁𝗵 𝟮.𝟬 uses scoped access tokens to let applications access resources without sharing user passwords. Tokens can expire and access can be revoked.
𝗔𝗣𝗜 𝗞𝗲𝘆𝘀 use a shared secret to identify and authenticate the calling application. They're simple to implement, but the key itself doesn't prove who holds it.
𝗕𝗮𝘀𝗶𝗰 𝗔𝘂𝘁𝗵 sends a username and password with every request. It's straightforward, but credentials must be protected with HTTPS.
𝗺𝗧𝗟𝗦 uses certificates to authenticate both the client and server during the TLS handshake. It's useful for service-to-service communication where both sides need to verify identity.
But choosing an authentication method is only part of the problem. You also need to manage credentials throughout their lifecycle.
Take CI/CD pipelines. A deployment might depend on a long-lived API key or deploy key stored in its secrets.
Even if it's stored securely, that credential can still be leaked, copied, or forgotten. And rotating it can break deployments that depend on it.
One approach is to replace static credentials with 𝘀𝗵𝗼𝗿𝘁-𝗹𝗶𝘃𝗲𝗱, 𝗶𝗱𝗲𝗻𝘁𝗶𝘁𝘆-𝗯𝗮𝘀𝗲𝗱 𝗮𝗰𝗰𝗲𝘀𝘀.
Instead of retrieving a stored secret, the pipeline proves its identity and receives a credential scoped to what it needs. That credential expires automatically.
Teleport Machine ID implements this approach by letting CI/CD runners use their platform identity to obtain short-lived certificates instead of storing deploy keys.
This reduces the need to manage long-lived credentials while keeping access tied to specific machine identities.
𝗟𝗲𝗮𝗿𝗻 𝗵𝗼𝘄 𝘁𝗼 𝗲𝗹𝗶𝗺𝗶𝗻𝗮𝘁𝗲 𝘀𝘁𝗮𝘁𝗶𝗰 𝗰𝗿𝗲𝗱𝗲𝗻𝘁𝗶𝗮𝗹𝘀 → lucode.co/teleport-machine-w…
What else would you add?
——
💾 Save it for later.
🙏 Thanks to @goteleport for sponsoring this post.
➕ Follow Nikki Siapno to improve at system design and AI engineering.
Fahyvor retweeted
SHA-256 algorithm is actually a one-way encryption... hence the reason why it's safe to use when storing passwords.
SHA-256 algorithm is actually a one-way encryption... hence the reason why it's safe to use when storing passwords.
Fahyvor retweeted
You can be qualified, experienced and hardworking. Sometimes the only thing missing is someone willing to pay you properly.













