#xcb — Public Fediverse posts

Excited to announce that our paper with TU Wien on the first plaintext recovery attack against XCB-AES (IEEE 1619.2) has been accepted at #CRYPTO2025!
👉 https://ia.cr/2024/1554
#IEEE #Standardization #XCB #XCB_AES #cosic #kuleuven

So I just wrote myself a kb language layout indicator for #x11 to complement my #twm setup and #tmux status panel while at it. This #c thing seems quite useful. Yay me :toot:

#freebsd #linux #unix #hobbyhack #noob #xcb

I was using #XCB, I tried raw stuff to the #framebuffer and OMG 1000x faster! AND I can rip shttons of useless code out of my cloud client thin antibrowsers! #OldGuyCoding #Programming For the record, years ago I wrote a raw gui device driver for gui, it took me a few days, SDL took me MONTHS GET OFFA MY LAWN!

I was using #XCB, I tried raw stuff to the #framebuffer and OMG 1000x faster! AND I can rip shttons of useless code out of my cloud client thin antibrowsers! #OldGuyCoding #Programming For the record, years ago I wrote a raw gui device driver for gui, it took me a few days, SDL took me MONTHS GET OFFA MY LAWN!

I was using #XCB, I tried raw stuff to the #framebuffer and OMG 1000x faster! AND I can rip shttons of useless code out of my cloud client thin antibrowsers! #OldGuyCoding #Programming For the record, years ago I wrote a raw gui device driver for gui, it took me a few days, SDL took me MONTHS GET OFFA MY LAWN!

I was using #XCB, I tried raw stuff to the #framebuffer and OMG 1000x faster! AND I can rip shttons of useless code out of my cloud client thin antibrowsers! #OldGuyCoding #Programming For the record, years ago I wrote a raw gui device driver for gui, it took me a few days, SDL took me MONTHS GET OFFA MY LAWN!

I was using #XCB, I tried raw stuff to the #framebuffer and OMG 1000x faster! AND I can rip shttons of useless code out of my cloud client thin antibrowsers! #OldGuyCoding #Programming For the record, years ago I wrote a raw gui device driver for gui, it took me a few days, SDL took me MONTHS GET OFFA MY LAWN!

Asking another way. #xcb 20 frames a second, no need for an 8meg local buffer, go! Be aware this would drop my thin client #antibrowser from 8.2Mbytes to 200Kbytes. Ideally I'd like a /dev/fb without sht on top like we had in late 90s, but I know that won't happen again

By using #xcb to get rid of fonts and then having to allocate memory for the screen buffer (WTF I can't use some memory I can guarantee is *somewhere* but not mine?!) my footprint for my #antibrowser thin client goes from a start of 160kbytes to 8Mbytes, this is not good, it is still less than bloated Chrome's 300Mbytes. Before, I scribbled at 1 or 2 frames a second, but couldn't do better. I need that 3rd option! decent frame rate and direct-er screen buffer access

What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients https://www.youtube.com/watch?v=Esv6xHwZRYc

Welp enough time wasting! gotta rip out #shm from #xcb and judging by the sample app I found, I should go from 2 frames/sec max to possibly hundreds at least for small area changes