Conversation

Notices

1. Embed this notice
   Adam Katz (adamhotep@infosec.exchange)'s status on Thursday, 22-May-2025 01:53:42 JST Adam Katz

   • HTTP 1.1/418 Old Teapot Typewriter Font
   • Ryan Castellucci (they/them) :nonbinary_flag:

   @ryanc @rmd1023 ah, that makes sense; you can't exactly dither at that resolution

   • Embed this notice
     Ryan Castellucci (they/them) :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 22-May-2025 01:59:38 JST Ryan Castellucci (they/them) :nonbinary_flag:

     in reply to

     • HTTP 1.1/418 Old Teapot Typewriter Font

     @adamhotep @rmd1023 I could fall back to 256 colors, but detecting 24bit vs 256 color mode is... annoying.

   • Embed this notice
     Adam Katz (adamhotep@infosec.exchange)'s status on Thursday, 22-May-2025 06:00:00 JST Adam Katz

     in reply to

     • HTTP 1.1/418 Old Teapot Typewriter Font
     • Ryan Castellucci (they/them) :nonbinary_flag:

     @ryanc @rmd1023 You can apparently just issue both colors, 256 then 24bit. Noncompliant terminals should issue the 256-color code and ignore the 24bit code while compliant terminals will issue both and therefore override the 256-color version. The only gotcha is that this should increase bandwidth costs by 139% if I've done my math right.

   • Embed this notice
     Ryan Castellucci (they/them) :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 22-May-2025 16:35:38 JST Ryan Castellucci (they/them) :nonbinary_flag:

     in reply to

     • HTTP 1.1/418 Old Teapot Typewriter Font

     @adamhotep @rmd1023 you can actually do \e[48;5;124;48;2;65;0;0m caving a couple characters, and the service already uses silly amounts of bandwidth