eliza🌻

i put balatro on my oscilloscope

as far as i can tell there is no way to actually say “i want more/less of this” and influence the model’s behavior in any way 🙃

the iOS “Prioritize Notifications” AI thingy appears to always mark notifications from the spammiest group chat i’m in as “priority” and has never prioritized a notification i actually wanted to receive

i would much rather talk *about* computers in public

do you ever just think about how there is an OpenAPI API for the OpenAI AI API

“great, i will simply not fuck with any aspect of the audio setup, and hope that it remains exactly this way for another ten minutes”

my coworkers Dave, John, @smklein.bsky.social, and i have been pregaming this one all morning on Matrix, btw :)

🍄🍄‍🟫🍄

(mutex was used in these examples for simplicity but really, it’s anything that synchronizes in a LIFO way)

(the practical case in which we encountered this was not actually a mutex-qua-mutex but the queue of waiting senders for a MPSC queue, which disguised the underlying issue a bit more)

yeah, the underlying problem is inherent to a LIFO mutex. what i think is more novel here is just that it is a way that Rust’s async primitives give you a neat little way to have acquired a lock in a suspended coroutine without realizing you haven’t released the lock

i think Dave used the term “deadlock” a lot, and discussed how this is due in part to fairly queued locks, but he may not have specifically said “priority inversion” anywhere in the text 🤷‍♀️

the intent is not to claim to have discovered a totally novel category of bug but simply to be able to discuss how a priority inversion can result from the interaction of these commonly used constructs in a fairly non-obvious way

we agree that it is an instance of priority inversion! the name “futurelock” is intended to give a name to a *specific combination of Rust constructs that results in a priority inversion*. we felt this was useful so we could discuss this specific bug in the abstract while e.g. reviewing future code

Join us on Monday at 5p Pacific to discuss! discord.gg/QrcKGTTPrF?e...

the most positive thing i can say about this hackernews thread is “no one has mentioned LLMs yet”

OH: “real XML has never been tried”

photograph of my grey and black tabby cat Casimir lying on top of a Unifi Pro Max 16 ethernet switch

the switch cuddler

‪they’re gonna be running a trillion simulations of my consciousness on a Dyson sphere made out of neutronium, and they’re all gonna just be trying to find an ebay listing for this thing that comes with the rails‬

“oh sick, this shit is gonna be so cheap on eBay some time after the Singularity!”

screenshot of a youtube video titled “INSIDE a 1.44TB HBM3e NVIDIA HGX B200 Al Server from ASRock Rack” where the top comment is “Cant wait to buy this on ebay in 10 years for 500 dollars”

this youtube commenter understands me on a deep and profound level

does everybody know about my favorite website, the embroidery tips page that forgot to close its <h3> tags

at least these say the name of a company on them

My "All postmortems are blameless, but this one is especially so" T-shirt has people asking a lot of questions already answered by my shirt.

photograph of a cardboard box with “Adaptec SAS expander, DO NOT EAT!” written on it in sharpie

i’m good at labeling things

We take it for granted today, but a single 6W embedded NPU can do more tensor operations per second than a peasant in the 1400s could perform in his whole lifetime

not to be confused with, uh…Oceanportal

screenshots of similarly white-labeled products from the 1984 film "Repo Man"

same energy

screenshot of ebay listing for whitelabeled enterprise SSDs that just say "SERVER 2.5" SSD" on them

you will certainly not regret purchasing the Store Brand Enterprise SAS SSDs

the hardest thing about shopping online for used enterprise storage equipment is that you have to make sure to not accidentally buy a FibreChannel thing by accident