Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

this is the nightmail #osc

gibbit_'s profile picture

finn🔆

5,026 subscribers

14,763 Aufrufe • vor 7 Monaten •via X (Twitter)

#osc
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

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

Sad 6000 ☹️

34,258 Aufrufe • vor 7 Monaten

There he is! #animaticbattle #osc
0:23

There he is! #animaticbattle #osc

runeia

14,849 Aufrufe • vor 1 Jahr

made this goofy thing #osc #inanimateinsanity
0:26

made this goofy thing #osc #inanimateinsanity

ARTEMiN ⚡️

53,635 Aufrufe • vor 1 Jahr

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

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

( MOVED ACCOUNTS )

27,555 Aufrufe • vor 1 Jahr

#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 Aufrufe • vor 1 Jahr

#BCFC this is at the Royal Academy in London & filmed by one of London Blues OSC members #KRO 💙🤍🐧#FEA
0:30

#BCFC this is at the Royal Academy in London & filmed by one of London Blues OSC members #KRO 💙🤍🐧#FEA

ESONEULB

74,501 Aufrufe • vor 26 Tagen

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

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

dee!

34,774 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 7 Monaten

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

Hi please dont the potatoes #bfdi #OSC

Safarie🍃

21,640 Aufrufe • vor 6 Monaten

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

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

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

24,234 Aufrufe • vor 1 Jahr

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

30,311 Aufrufe • vor 4 Monaten

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

THANK YOU for saving the OSC CHANT! #VidCon

Michael Y. Huang

22,187 Aufrufe • vor 1 Jahr

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

OUT IN THE OPEN INTRO #osc #bfdi #osctwt

pik . pilled

21,520 Aufrufe • vor 1 Jahr

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🌻Comms: (Open Sep 1st)

20,458 Aufrufe • vor 1 Jahr

I COULDN'T RESIST ANIMATING THIS AUDIO #ii #inanimateinsanity #iisilverspoon #osc #objectshow
0:32

I COULDN'T RESIST ANIMATING THIS AUDIO #ii #inanimateinsanity #iisilverspoon #osc #objectshow

Shorthalves

52,731 Aufrufe • vor 2 Jahren