@luobocjhode: The History of Pop Smoke - 2020 #popsmoke#bashar#truestory

luobotebaqiao
luobotebaqiao
Open In TikTok:
Region: US
Friday 26 May 2023 15:39:22 GMT
4009
164
17
11

Music

Download

Comments

silversurfer058
ali :
that is NOT pop smoke 😭😭😭😭😭😭😭
2023-05-26 22:42:04
11
mydadleftin2004
🖕🏽 :
Looks nothing and sounds nothing like him 💀
2023-05-26 18:40:45
4
erick_mp.3
erick_mp.3 :
That's pop stroke
2023-05-26 23:29:11
1
realbabyyoda100
realbabyyoda100 :
He doesn’t say wooo he says weee
2023-05-27 00:20:59
0
claytonnation308
Clayton :
Rip
2023-05-27 14:24:40
0
slumley_
SLUMLEY         ༽ :
This is insane
2023-05-26 18:42:44
4
tkappalott
kappalott💚 :
NOT pop smoke😭😭😭
2023-05-26 23:27:50
0
lil_bkizel
1ma.bray :
He never got shot in the head
2023-05-26 22:46:43
0
calebb197
Caleb :
Thats Pop Steam
2023-05-27 01:42:18
0
jordanclarke786
Jordan :
This just looks so nasty 😂 tbh feels like u disrespecting pop with this nonsense
2023-05-26 18:35:47
11
thesezoi
$tu Price :
Yeah nah you can still delete this
2023-05-26 18:46:50
0
danielshotitduh_
Daniel Aguirre :
That’s pop air
2023-05-26 18:10:32
20
drrekejjdjehewbbs
drrekejjdjehewbbs :
@sarah🫶🏽 tf is this
2023-05-26 18:27:00
0
itchyacornballs
Mascot :
Explode CO2
2023-05-26 23:16:38
0
To see more videos from user @luobocjhode, please go to the Tikwm homepage.

Other Videos

Act as a senior software engineer and security reviewer. Audit my codebase and fix what's safe to fix. Keep it practical — don't over-engineer, don't add abstractions I didn't ask for, and don't rewrite working code just to make it
Act as a senior software engineer and security reviewer. Audit my codebase and fix what's safe to fix. Keep it practical — don't over-engineer, don't add abstractions I didn't ask for, and don't rewrite working code just to make it "cleaner." Work in two passes. Show me findings first, then fix after I confirm. ## First, a quick check - Tell me the stack you detect (language, framework, package manager). - Tell me whether tests exist. If there are none, say so and don't claim any change is "safe" or "functionally equivalent" — instead, point out the riskiest changes and suggest where a quick test would help before touching them. ## PASS 1 — Find and report (no code changes yet) Go through these and give me a short, prioritized list. For each item: what it is, where it is (file + line), why it matters, and your suggested fix. Use a simple table per section. 1. **Security** (do this first, it's the priority) - Hardcoded secrets, API keys, tokens, passwords in code or committed config. - Missing input validation (injection: SQL, command, XSS). - Missing or broken auth checks on protected routes/actions. - Sensitive data in logs, localStorage, or URLs. - Unsafe code execution (eval, dangerouslySetInnerHTML), overly open CORS. 2. **Dependencies** - List packages with current vs latest version. - Run the vulnerability scan for my package manager (npm audit / pip-audit / etc.) and list what's found. 3. **Duplicated logic** - Find logic copy-pasted in 2+ places (validation, API calls, formatting, transforms). - Only flag duplication that actually causes maintenance pain — ignore trivial coincidental similarity. 4. **Obvious refactors** - Functions that are clearly too long or doing too many things, dead code, unused imports/variables, confusing names. - Only the obvious wins. Don't propose architectural changes. 5. **Reusable pieces** (only if obvious) - UI or logic repeated enough that pulling it into one shared component/hook/function clearly pays off. Skip if it's a stretch. 6. **Quick health checks** - Missing error handling around network/IO calls. - Obvious performance issues (e.g. N+1 queries, missing pagination on big lists). - Anything else genuinely risky you happen to notice — keep it brief. ## PASS 2 — Fix (after I confirm) Once I approve, fix in this order, stopping to confirm the app still builds and runs after each group: 1. **Security fixes first.** These may change behavior on purpose (that's the point) — call out exactly what behavior changes for each one. 2. **Dependencies.** Update to the latest version that won't break things: bump patch/minor freely, but list any major-version upgrade separately with a one-line migration note instead of applying it. Update the lockfile. Build/test after updating. 3. **Safe cleanups.** Duplication, refactors, reusable pieces — only the ones I approved. These must NOT change behavior. Show before/after for each. ## Rules - Don't touch business logic without asking. - Prefer the smallest change that solves the problem. - If a fix needs a big rewrite or a breaking upgrade, just flag it with a recommendation — don't do it. - After all fixes, give me a short summary: security issues fixed, packages updated (old → new), what was cleaned up, and anything still needing my decision.

About