Notices by JP (froztbyte@mastodon.social)

@inthehands on ios safari (in priv mode), changing the string blanks the canvas. left it a few seconds incase it was maybe rendering slow, but didn’t seem to be

18.7.8, if that helps

good morning fedi

since it’s friday and to get a bit of awareness of it going: over at awful we’ve started a slop-free jobs board! you can find the info at https://awful.systems/post/9584343

It’s brand (and possibly spanking!) new, so please consider giving this some retoots to get the name out

leaks from the gc: LLMs = expanding blob of pee in the pool

why does this come to mind?

oh, you know... water.. marked..

@davidgerard @aral @usernameswift @ajn142 he also apparently may be some kind of advisor in a danish public professional IT advisory group: https://bsky.app/profile/prosaole.bsky.social (as found by @fasterandworse )

username under that profile has parallel-posting: https://old.reddit.com/user/prosaole/

skeeter profile pic and google scholar image match pretty closely, although aging appears to be at different epochs

@soatok what is it about these types that make them fuck up exponents like it’s a hazing ritual? nevermind them then doubling down with their fingers in their ears, going “nuh-uh-uh can’t heaaaaar youuuuu”…

@firefoxwebdevs I mean realistically, we have about:config at home, and y'all are already not respecting that

why the future "KILL SWITCH" carrot? it just comes across like a Musk promise

@whitequark I’ve found at *least* 3 different ways to have that journey with podman

it’s not the kind of exciting I want in my computing

@ryanc ay allowed then? ;D

@whitequark @exchgr isn’t it just damned _great_ what the various walled gardens fought to make happen? :|

@whitequark @hailey Nod, I figured/presumed it was that. For most such cases in the last 10y, pike’s mistake is the reason for that

@whitequark @hailey single-dash word-args, I didn’t know you’re a committee of that variety of shellcrimes! :o

but yeah that looks pretty reasonable

@whitequark @hailey do you already have revert-to-previous-$x rollback type stuff covered? hypothetical attack: "dodgy commit makes it into repo somehow" (overprivileged CI or a jiatan situation or whatever it may be)

you can't necessarily wait for the commit to be undone, but you would want the post-commit published content made unavailable as soon as instructed (whether by human or other trigger)

@whitequark @hailey (also, soz, know you didn't ask me but have had to poke at this in other contexts before so my brainmeat is primed to think about it regardless)

@whitequark @hailey ah I was confused by freeze in the previous toot, then realized you meant "freeze operation" (vs something more like "change hold") - would distinguishing/disambiguating between those be useful?

given that output is pretty strongly tied to git activity I feel like most of the abuse handling scenarios that'd apply would "need" to be driven by detection automation, but is a split useful for something else?

@whitequark @hailey Yeah the potential for that turning into phish and reflectance attack fuckery is pretty high, adds a pile of abuse burden

@whitequark oh that’s a pretty cool find, nice

@skinnylatte these are words I almost never say: I want to sign up to your newsletter

@whitequark hah that's kinda incredible, and hella poignant

@whitequark @f4grx @ge0rg can confirm for both this and other compounds

The Drug Alone ain't the whole story

@whitequark @ge0rg in the same way that digital protocols designed by RF (and/or telecoms) engineers tend to, I’d guess