@fans_arurin: “ya beli aja” ENTENG BGTT NGOMONG NYA BJIRR?!! 😭😭 @aru & rin🫧 @aru @rin.dpu @varruaru #arurin #couplegoals #fyp #4upage #xybca

LIA~fans arurin🫧
LIA~fans arurin🫧
Open In TikTok:
Region: ID
Monday 29 June 2026 10:30:17 GMT
59233
4991
34
125

Music

Download

Comments

riskifriski124
za_🌸_hra🧸 :
pengen punya cowok royal kayak kak rin
2026-06-29 10:54:11
543
littlerainbow8
🌷 IKAAA 🌷 :
auranya kek "kuras harta ku sayang" damn 😭😭😭😭
2026-06-30 02:12:16
74
16_a.raa
2008 sikecil :
hah rambut nya ituh di potong kok ke beda orang 😭😭
2026-06-29 11:08:18
70
alfinnn_danielll
genaww :
when yahh punyaa cowo royal bangett
2026-06-30 00:44:50
9
c1tr58
my name is .... :
cowo idaman
2026-06-30 00:48:22
6
tiktok.comlena.karlena
Hi,maniz💞🤍 :
wah ini sih saingan ya Willie Salim yang ini mah
2026-06-30 03:05:05
0
dianaekowati1
bear_🐻 :
tukeran dong kak
2026-06-29 13:48:08
4
kesya_mahira
⋆。‧˚ʚ🍓beauty creator🍓 ɞ˚‧。⋆ :
kak kenalin aku iri 😭
2026-06-30 02:43:13
0
nin_stecuu2
☆ℕ𝕚𝕟cihuyy☆ :
aura ceo nya kuat bet
2026-06-30 02:39:01
0
askiya_nuraenii
𝚔𝚒𝚢𝚊💦 :
𝚜𝚊𝚙𝚊𝚊𝚊 𝚍𝚘𝚗𝚐
2026-06-29 10:38:14
3
pretty_putri19
sukayappinggg :
plis ka cwo nya seroyal itu "kuras harta ku sayang" type gw bnget cok
2026-06-30 02:29:43
0
alindyadyaaa
˚。⋆୨୧˚ll A_lyn˚。⋆୨୧˚ :
kak kmu org yg paling beruntung
2026-06-30 02:24:38
0
khusnulcantikk0
★km gpp ta null★ :
pertama kak sapa dongg🤭🤭🤭
2026-06-29 10:33:47
4
razz_167
? :
MOGA NULAR😖😖
2026-06-29 23:36:25
0
call_me_alyaaa
Lya? :
keduaaa
2026-06-29 10:33:58
2
syafrilsasa
nona fildas :
iri sih
2026-06-30 00:17:38
2
pipittt709
210713🦖 :
tapi sayangnya mereka......
2026-06-29 12:29:54
1
ririirawrrr
𐚁๋࣭⭑ֶָ֢( Riri ) :
ihh pengen benget cowok ke gitu satu 🤭😭
2026-06-29 11:46:43
3
saaa_4092
Saaa?? :
CUMA BISA WHENN WHEN WHEN😩😩
2026-06-29 12:31:28
3
lenn6824
￴ ￴ ￴ ￴ :
︎       ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎        ︎ ︎     ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎ ⓘ kamu tidak bisa melihat komentar ini, dikarenakan kamu just friend!   ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎           ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎       ︎ ︎       ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎       ︎ ︎       ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎           ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ       ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎     ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎       ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎       ︎ ︎       ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ᅠ         ︎ ︎         ︎ ︎ ︎ ︎
2026-06-29 10:35:14
1
tf_stand83
putri_12 juni✨ :
@aru & rin🫧
2026-06-30 01:55:41
0
eciiii5528
🤍 :
@aru & rin🫧
2026-06-29 10:39:13
0
andin_1245
~𝖎𝖈𝖊𝖑𝖑🐙 :
@𝓬𝓾𝓽𝓮𝓰𝓲𝓻𝓵 when ya
2026-06-30 03:05:37
1
To see more videos from user @fans_arurin, 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