@katomedia2.0: He was driving his Tesla Cybertruck through an empty cemetery… nobody outside, but his screen showing PEOPLE?! 👻 yeah he got up outta there fast 😳 #Cybertruck #GhostSighting #Paranormal #ScaryTok #FYP

YouTube : Katomedia2.0

Open In TikTok:

Region: US

Monday 13 April 2026 18:20:47 GMT

158006

3040

174

1953

Music

Download

No Watermark .mp4 (5.05MB) No Watermark(HD) .mp4 (2.47MB) Watermark .mp4 (4.41MB) Music .mp3

Comments

Ronnie :

Aren’t they supposed to be in heaven or the other place?

2026-04-14 21:51:41

84

Tricia Ann74 :

Wondering souls that didn't cross over 😳

2026-04-14 11:49:01

53

mayankp.24 :

Those r souls

2026-04-13 19:04:52

166

Pixie Stix :

Does that mean we really do stay asleep once we die until we are woken up in Revelations?

2026-04-14 09:37:47

38

Sawshitt1 :

We Are God

2026-04-14 15:42:39

29

Nope54 :

What y’all think video games are lost souls .

2026-04-14 15:57:50

7

🦁Mooshai🦁 :

Some people say that cemetery is a prison for souls. I don’t know if anyone else heard about that

2026-04-14 15:44:36

19

AGuyFormerlyKnownAs :

They’re just in another dimension

2026-04-14 02:41:09

24

476usert :

remember this is a spiritual world

2026-04-14 23:39:04

21

Chris Rose :

This one here seems like it's picking up the grave markers and flowers, but i've seen some of these, where it looks like they walk right up to the car and try to get in,and on some cases disappear when they get to the car😳

2026-04-14 11:22:09

6

snow_time :

there's people outside out there. there just not there visible to the human eye anymore

2026-06-25 17:51:19

4

Maciel Bushcraft :

Os sensores confundem as lápides com pessoas.

2026-07-20 19:21:32

8

@paulixxita :

Yo por eso no me compro un carro con tanta tecnología que miedo 😂😂

2026-04-16 21:20:47

24

Sadrac Pimemtel :

Parece como si estuviéramos en otra dimensión

2026-05-19 16:45:30

6

Fran Yepez :

Eso detecta almas

2026-05-11 19:35:52

2

На солярке :

This is an AI error. All Tesla cars are packed with cameras, but the car's AI can't figure out what's going on. It just assumes it's a human.

2026-06-12 00:48:24

0

vonnievonne2020vision :

Definitely lost souls

2026-04-13 19:37:11

5

🤍 :

Por los sensores de movimiento

2026-06-01 18:32:48

2

dann :

rame bang

2026-04-27 07:34:15

0

Øøf :

That’s not how that technology works

2026-04-14 11:54:36

4

AnnMarie_NouVeauRiche :

Where TF They Going😳😳

2026-04-14 22:34:18

4

LaJayc60 :

WTH

2026-04-14 23:48:06

2

Poppa Smurph :

It should be way more spirits there, if it was real. Right?

2026-04-14 13:25:05

0

👁️PiscesEyez👁️ :

No they are there but they are on meta.

2026-04-14 13:54:09

2

To see more videos from user @katomedia2.0, please go to the Tikwm homepage.

Other Videos

BTS of “Yorimos - Freestyle” #foryoupage #ethiopian_tik_tok🇪🇹🇪🇹🇪🇹🇪🇹 #yorimos

BTS of “Yorimos - Freestyle” #foryoupage #ethiopian_tik_tok🇪🇹🇪🇹🇪🇹🇪🇹 #yorimos

KnowYourRights

#foryou #quality #lamineyamal #mila9aa @#foryou

#foryou #quality #lamineyamal #mila9aa @#foryou

I know right

ความจริงก็คือได้แค่เทคเดียว5555🥹

ความจริงก็คือได้แค่เทคเดียว5555🥹

Comment LOCK and I'll send you the cheat sheet comparing locks, atomic updates, and constraints. One ticket left. Two people click Buy at the same time. Both your screens say you got it. ⚡ The bug isn't in your checkout code, it's the gap between checking and writing. Your server reads the seat, sees available, and then, before it writes sold, does something else entirely ⚡ In that gap Leo's request runs the exact same read. It also sees available. Then both writes land, and you send two confirmation emails for one chair ⚡ This is a race condition: not a rare crash, but the ordinary outcome of two requests arriving at once. Nothing threw. Nothing warned. The database did exactly what it was asked, twice ⚡ The first fix is pessimistic locking. SELECT ... FOR UPDATE takes a row lock, and Leo's request can't even read that row until Maya's transaction commits. The queue behind it stops being optional ⚡ The second fix is better because it removes the gap entirely: fold the check into the write. UPDATE seats SET status='sold' WHERE seat='F12' AND status='available', one statement, one decision ⚡ That runs as a single atomic operation. The check and the update either both succeed or neither happens. There is no

Comment LOCK and I'll send you the cheat sheet comparing locks, atomic updates, and constraints. One ticket left. Two people click Buy at the same time. Both your screens say you got it. ⚡ The bug isn't in your checkout code, it's the gap between checking and writing. Your server reads the seat, sees available, and then, before it writes sold, does something else entirely ⚡ In that gap Leo's request runs the exact same read. It also sees available. Then both writes land, and you send two confirmation emails for one chair ⚡ This is a race condition: not a rare crash, but the ordinary outcome of two requests arriving at once. Nothing threw. Nothing warned. The database did exactly what it was asked, twice ⚡ The first fix is pessimistic locking. SELECT ... FOR UPDATE takes a row lock, and Leo's request can't even read that row until Maya's transaction commits. The queue behind it stops being optional ⚡ The second fix is better because it removes the gap entirely: fold the check into the write. UPDATE seats SET status='sold' WHERE seat='F12' AND status='available', one statement, one decision ⚡ That runs as a single atomic operation. The check and the update either both succeed or neither happens. There is no "between" left for a second request to stand in Even buggy code can't break that rule, because the constraint lives in the database, not in your code. A unique key on the event-and-seat pair means two confirmed tickets for the same seat can't physically exist in the table. The engine refuses the second insert no matter what your application does. The database never really picks a winner by magic. It forces the two requests into a line. One goes first. The other sees the result. Two rules that outlive this specific example: keep your checks inside the write, and keep the final guarantee in the schema. Which has cost you more time, the bug or the incident review after it? Comment LOCK for the full cheat sheet. #databases #concurrency #postgresql #backend #programming

About

Robot
API

Legal

Privacy Policy