Instagram story viewer> @poganlim> Post
LP(poganlim)'s profile avatar

LP

@poganlim

2 months ago
Photo by LP on August 22, 2026. May be an image of one or more people, beard, hat, bolo tie and text.
Photo by LP on August 22, 2026. May be an image of fishing, fishing rod, boat and text.
Photo by LP on August 22, 2026. May be an image of punching bag, sweatpants, mirror and text.
Photo by LP on August 22, 2026. May be an image of crowd, stadium and text.
Photo by LP on August 22, 2026. May be an image of standing, dartboard and text.
Download
11
Posted On: August 22nd 2026, 10:28 pm
Tagged Users:
@hydnreid
hydnreid
Life recently
Comments (11)
aaron.stuu 2 months ago

aaron.stuu

pookie wookie

tyler.pim 2 months ago

tyler.pim

comment media

dainewilson_ 2 months ago

dainewilson_

comment media

kfank5 2 months ago

kfank5

Love it!

austinjoffer 2 months ago

austinjoffer

My boy

claiborne.cage 2 months ago

claiborne.cage

comment media

jedidiah.1 2 months ago

jedidiah.1

comment media

ty__albrecht 2 months ago

ty__albrecht

comment media

_jack.fank 2 months ago

_jack.fank

comment media

More posts

I changed.Period.
🖤🖤
🚨 Interview question: 10,000 bots are hammering your login API. How do you stop them without locking out real users? Most people say "just block them." Here's why that fails 👇 ❌ Blocking IPs doesn't work. The bots come from thousands of different IPs, each sending only a few requests, so no single source looks suspicious. ❌ Login is expensive on purpose. bcrypt is deliberately slow so attackers can't guess passwords quickly. But that means every fake attempt burns real CPU, and enough of them turns an attack into an outage. ❌ Rate limits don't catch it. Attackers use email and password pairs leaked from other sites, with only 1-2 tries per account. Your "5 attempts" rule never triggers. ❌ Lockouts backfire. Now attackers can lock real users out on purpose. ✅ The real fix: decide earlier. Put a cheap risk check in front of the expensive one, and only spend CPU on requests that look real. What the risk check looks at: 🔹 TLS fingerprint: a real iPhone app and a Python script connect differently, even if both claim to be an iPhone 🔹 Failure rate: a client failing most of its logins is suspicious 🔹 Known device: have we seen this device before? No single signal is enough, so you combine them and respond in proportion: 🟢 Low risk → straight through 🟡 Medium risk → CAPTCHA 🔴 High risk → dropped before it touches bcrypt Real users barely notice. Bots get expensive. 💸 Interview answer in one line: score each request cheaply, challenge the doubtful ones, and protect the slow, expensive step behind them. 📌 Save this for your next system design interview 💬 Comment "SECURITY" if you want the next one on rate limiting ➕ Follow for more backend concepts explained visually Hashtags: #systemdesign #softwareengineering #backend #cybersecurity #codinginterview techinterview programming developer bcrypt webdevelopment learncoding computerscience botprotection apidesign tech
I Love Capetown 😍🥹!! #capetown #beach #campsbay #instagram
GRIEZMANN IS UNREAL 🤯
back to up