@carterpcs: Trump mobile contacted me… #c#carterpcstech #trumpphone #trumpmobile

Carterpcs
Carterpcs
Open In TikTok:
Region: US
Thursday 25 June 2026 02:43:43 GMT
1260725
142327
753
591

Music

Download

Comments

bananatoad_
banana :
forced to agree to marketing emails 😭
2026-06-25 04:06:48
18084
bendy.1018
Bendy_1018 :
What happened to “Carter Here”?
2026-06-25 02:50:15
6484
bd_.randy
⃟ :
He still gonna diss the phone when he gets it
2026-06-25 02:53:08
736
moviegod91
Movie_hub 🎬 :
I can't feel my hands carter.
2026-06-25 03:14:02
2421
tkfelf
Tkfelf :
2026-06-25 04:25:32
222
dailydoseofmemesspot
️ :
1,000 likes to get me one ❤️❤️❤️
2026-06-25 02:45:22
156
ibralollyy
i̶b̶r̶a̶l̶o̶l̶💤 :
200k pc's for a like
2026-06-25 19:34:37
15
gogiji8769
... :
Day 36, carter can I get please get a laptop, I really need it for my A levels my mom won't buy me one. This one got passed down to me and it crashes with 2/3 tabs open😭
2026-06-25 16:48:07
13
user12368551679368
ant :
Why do you have 777 text messages?
2026-06-25 06:04:27
6
user4908022074808
ching⁴ :
30k likes for a xiaomi 17 ultra with photography kit?
2026-06-25 03:03:53
8
filipolina_official
Original_nugget🍗 :
Didnt you order it like 2years ago
2026-06-25 10:33:34
7
matekordzadze8
Matefn :
Carter can I get a gpu for my birthday🥳🎂🎉
2026-06-25 18:44:49
2
thatonemelon3
melon :
Yooooo w man!!
2026-06-25 02:53:14
2
erosvampire
🩸ErosVampire🩸 :
Nah dont freeze it get a new one lol
2026-06-25 06:40:52
3
vien.vien464
Vien Vien :
If this video get 100k likes he has to give me a phone
2026-06-25 11:46:26
2
g1_org11
g1_org1 :
Day 41 asking for a free gaming pc
2026-06-25 07:18:16
8
joledole1
joledole1 :
136 th video asking Carter to help me finish my pc build pls (cpu,gpu,ram)🫩
2026-06-25 04:39:25
7
user17854223789
user776103 :
How many likes for a trump mobile Carter?
2026-06-25 04:50:16
15
notnangojoey
NN :
If I get 10k likes you have to give me a ps5
2026-06-25 11:07:15
6
mk_innovation0
Stoner__fx :
Can I get a phone or pc if my comment hits 2k?😭
2026-06-25 04:10:22
9
itsbrandonmax
Brandon Max :
I can relate
2026-06-25 12:31:23
47
yoel.609
Yoel(:✡️ :
Carter, how many likes for a follow back? it’s free bro pls
2026-06-25 02:50:02
6
To see more videos from user @carterpcs, 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