Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is the nightmail #osc

gibbit_'s profile picture

finn🔆

5,026 subscribers

14,763 görüntüleme • 5 ay önce •via X (Twitter)

#osc
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

There he is! #animaticbattle #osc
0:23

There he is! #animaticbattle #osc

runeia

14,849 görüntüleme • 1 yıl önce

Remember when this video haunted the OSC around a year ago?
0:38

Remember when this video haunted the OSC around a year ago?

Reaper 6000 💀

33,995 görüntüleme • 5 ay önce

are all osc fans like this??
0:49

are all osc fans like this??

goodeguy

15,138 görüntüleme • 1 yıl önce

WHERE THE HELL IS THE BOSS⁉️ 🗣️🗣️📣📣 #bfdi #OSC #tpot
0:20

WHERE THE HELL IS THE BOSS⁉️ 🗣️🗣️📣📣 #bfdi #OSC #tpot

天猫だおよ✨✨

12,248 görüntüleme • 1 yıl önce

made this goofy thing #osc #inanimateinsanity
0:26

made this goofy thing #osc #inanimateinsanity

ARTEMiN ⚡️

53,635 görüntüleme • 1 yıl önce

OSC Hosts start taking drugs part 6.5 - #osc #objectshowcommunity
0:46

OSC Hosts start taking drugs part 6.5 - #osc #objectshowcommunity

Funkler 🐟✦

26,966 görüntüleme • 1 yıl önce

#osc bfdia 18!!1 . . . . IS IT A FETISH OR SMTH TO KILL FRIES NOW BECAUSE WHAT THE FUCK WAS ALL OF THIS FOR???????
0:23

#osc bfdia 18!!1 . . . . IS IT A FETISH OR SMTH TO KILL FRIES NOW BECAUSE WHAT THE FUCK WAS ALL OF THIS FOR???????

stu guy

42,013 görüntüleme • 1 yıl önce

my one fnf post on this account. #inanimateinsanity #osc
1:45

my one fnf post on this account. #inanimateinsanity #osc

dee!

34,774 görüntüleme • 1 yıl önce

i just saw the funniest osc video ever oh my gosh please look at this
0:20

i just saw the funniest osc video ever oh my gosh please look at this

RyeBreadRyan

51,247 görüntüleme • 1 yıl önce

#inanimateinsanity #osc knife-solute territory (idk what to call this)
0:39

#inanimateinsanity #osc knife-solute territory (idk what to call this)

deebie weeebie

15,046 görüntüleme • 1 yıl önce

Hi please dont the potatoes #bfdi #OSC
1:21

Hi please dont the potatoes #bfdi #OSC

dude

15,326 görüntüleme • 3 ay önce

i just wanted to animate this audio #inanimateinsanity #osc
0:26

i just wanted to animate this audio #inanimateinsanity #osc

Elijah🌻Shop: OPEN!

11,601 görüntüleme • 4 ay önce

WALKIN’ ON THE SUN #iwiosc #osc
0:22

WALKIN’ ON THE SUN #iwiosc #osc

finn🔆

18,384 görüntüleme • 1 yıl önce

gift for the fooler #animaticbattle #objectfool #osc #osctwt
0:49

gift for the fooler #animaticbattle #objectfool #osc #osctwt

{M0RTi!!} ANIMATIC'S #1 FAN/SPOUSE

23,734 görüntüleme • 1 yıl önce

OUT IN THE OPEN INTRO #osc #bfdi #osctwt
0:30

OUT IN THE OPEN INTRO #osc #bfdi #osctwt

pik . pilled

21,520 görüntüleme • 1 yıl önce

THANK YOU for saving the OSC CHANT! #VidCon
0:20

THANK YOU for saving the OSC CHANT! #VidCon

Michael Y. Huang

21,209 görüntüleme • 1 yıl önce

Got flash banged by OpenCode recently? Yeah, that was me. Here's what happened: OpenCode/OpenTUI detects terminal theme mode (light or dark) by querying OSC 10/11 for the terminal’s foreground/background colors and deriving the mode from those values. OpenTUI also enables DEC Private Mode 2031 to receive theme-change notifications. When that mode is enabled, terminals can send CSI 997 when the system theme changes. OpenTUI treated the 997 payload as authoritative and let it override the OSC 10/11-derived result. That turned out to be wrong. In some terminals, the 997 payload is simply unreliable: it can report light while the queried terminal colors clearly indicate a dark theme. That’s what caused the flash bangs. The fix seemed straightforward: stop trusting the 997 payload as the actual theme mode and use it only as a trigger to re-query OSC 10/11, then derive the mode from the returned foreground/background colors. That works great. Except OpenTUI had also started using OSC 11 to set the terminal’s default background color, so the terminal gutter around the drawn TUI matched the app background instead of the terminal’s own default background. This was introduced recently in OpenTUI. That created a new problem: if you use OSC 11 to override the terminal background, then later query OSC 11, you are just reading back your own override instead of the terminal’s real theme background. No problem. Reset the terminal background with OSC 111, query OSC 10/11, derive the mode, then restore the renderer background again. Oh wait. Turns out Ghostty has a bug. Once this background reset/override path is used, later OSC 11 background reporting can get stuck and stop tracking system theme changes correctly. Even though theme-change notifications still fire and OSC 10 foreground updates continue. This would cause further issues where the OSC 10/11 derivation would be wrong again. So for now: no using OSC 11 to set the terminal background color just to fill the gutter. TL;DR: OpenTUI must treat CSI 997 only as a hint that the terminal theme may have changed and rely exclusively on OSC 10/11 color queries for actual theme mode detection, while avoiding terminal background mutation via OSC 11/111 because that breaks correctness in some terminals like Ghostty.
0:44

Got flash banged by OpenCode recently? Yeah, that was me. Here's what happened: OpenCode/OpenTUI detects terminal theme mode (light or dark) by querying OSC 10/11 for the terminal’s foreground/background colors and deriving the mode from those values. OpenTUI also enables DEC Private Mode 2031 to receive theme-change notifications. When that mode is enabled, terminals can send CSI 997 when the system theme changes. OpenTUI treated the 997 payload as authoritative and let it override the OSC 10/11-derived result. That turned out to be wrong. In some terminals, the 997 payload is simply unreliable: it can report light while the queried terminal colors clearly indicate a dark theme. That’s what caused the flash bangs. The fix seemed straightforward: stop trusting the 997 payload as the actual theme mode and use it only as a trigger to re-query OSC 10/11, then derive the mode from the returned foreground/background colors. That works great. Except OpenTUI had also started using OSC 11 to set the terminal’s default background color, so the terminal gutter around the drawn TUI matched the app background instead of the terminal’s own default background. This was introduced recently in OpenTUI. That created a new problem: if you use OSC 11 to override the terminal background, then later query OSC 11, you are just reading back your own override instead of the terminal’s real theme background. No problem. Reset the terminal background with OSC 111, query OSC 10/11, derive the mode, then restore the renderer background again. Oh wait. Turns out Ghostty has a bug. Once this background reset/override path is used, later OSC 11 background reporting can get stuck and stop tracking system theme changes correctly. Even though theme-change notifications still fire and OSC 10 foreground updates continue. This would cause further issues where the OSC 10/11 derivation would be wrong again. So for now: no using OSC 11 to set the terminal background color just to fill the gutter. TL;DR: OpenTUI must treat CSI 997 only as a hint that the terminal theme may have changed and rely exclusively on OSC 10/11 color queries for actual theme mode detection, while avoiding terminal background mutation via OSC 11/111 because that breaks correctness in some terminals like Ghostty.

kmdr

29,509 görüntüleme • 1 ay önce

don't stop dancing animatic is done yall eat up #inanimateinsanity #osc
2:03

don't stop dancing animatic is done yall eat up #inanimateinsanity #osc

Elijah🌻Shop: OPEN!

19,301 görüntüleme • 1 yıl önce

The Weezer guys ! - #animaticbattle #itft #bfb #tpot #osc #objectshowcommunity
1:06

The Weezer guys ! - #animaticbattle #itft #bfb #tpot #osc #objectshowcommunity

( MOVED ACCOUNTS )

21,053 görüntüleme • 2 yıl önce