Notices by dakkar (dakkar@s.thenautilus.net)

Have a random fox

@hazelnoot@transfem.social oh look, a merge commit

@ryanc@infosec.exchange heatpipes to a big exchanger

@ryanc@infosec.exchange the smell of burnt chips in the morning…

@ryanc@infosec.exchange you read those message in @Computer@dice.camp's voice, right?

@ryanc@infosec.exchange "ryanc, stunt cryptographer" has a nice ring to it

@ryanc@infosec.exchange «I heard you like functions, so I put a function in your function»?

@ryanc@infosec.exchange that's a very precise and detailed way to call bullshit! 😁

TIL: CSS animations allow you to animate replaced content.
You can do something like:.frames > *::before { animation-duration: 2s; animation-iteration-count: infinite; animation-timing-function: steps(10, jump); font-family: monospace; width: 1em; content: '*'; } #a11::before { animation-name: a11 } @keyframes a11 { from { content: 'a'; } 10% { content: 'b'; } 20% { content: 'c'; } 30% { content: 'd'; } 40% { content: 'e'; } 50% { content: 'f'; } 60% { content: 'g'; } 70% { content: 'h'; } 80% { content: 'i'; } 90% { content: 'j'; } 100% { content: 'k'; } }and: to get a little alphabet going. And of course you can animate fg/bg
colours as well.

So you could write a libcaca driver that produces a per line,
with a per pixel, and a lot of @keyframes, to render a
whole video that way.

No, I am not writing that!

@ryanc@infosec.exchange changed to what, though?

@ryanc@infosec.exchange you took the scenic route 😉

@privateger@plasmatrap.com @puniko@mk.absturztau.be @dalekcoffee@oshi.social @Sharkey@shonk.social
little reminder that, currently, switching from Sharkey to Misskey requires every user to manually re-set their passwords (unless we merge !444, at least)
(I'm with you on the forking, for what it's worth: merging from Misskey is sometimes messy, but I wouldn't want to be responsible for all development!)

@ryanc@infosec.exchange

@ryanc@infosec.exchange in the sense that "people will probably not notice the breakage", sure
I'll still try to get them to revert, because it's wrong 😠

@ryanc@infosec.exchange @hrefna@hachyderm.io oh no, it's even more simple-minded: it completely ignores the @context (which contains "firefish": "https://joinfirefish.org/ns#", "speakAsCat": "firefish:speakAsCat"), and only looks for speakAsCat (which is the only property defined in the firefish namespace) in the top-level of the activity

@ryanc@infosec.exchange @hrefna@hachyderm.io thanks for the confirmation, I've also checked with https://tools.w3cub.com/jsonld-to-expanded

so… the firefish devs have made a change that did not break things only because the consumers (mostly Misskey forks) process JSON-LD "wrong", completely ignoring the context.

I have suggested they revert that change, let's see what happens.

@hrefna@hachyderm.io Apologies for intruding, among all the fedi people I know, you're the best JSON-LD "expert" I can think of.

We received this change request https://activitypub.software/TransFem-org/Sharkey/-/merge_requests/492 which mirrors https://firefish.dev/firefish/firefish/-/commit/ddc8f62a16f42c1992be63ab76c915dd3df83d59#f7ac164b4532a445f7f82ce6c2517d6ffc76d89e

Is my reaction (in the comments to the Sharkey MR) wrong? I'm pretty sure that IRIs in JSON-LD work just like namespaces worked in XML… so they don't need to resolve to actual resources, and changing a prefix-to-IRI mapping changes the meaning of the document.
How wrong am I?

ROTFLing at Lenovo trasparent screen (press release, [engadget](https://www.engadget.com/lenovos-project-crystal-is-the-worlds-first-laptop-with-a-transparent-microled-display-230025521.)

@Polychrome@poly.cybre.city and the 2023 reboot kept nearly all the same jokes! and they still work!

@ryanc@infosec.exchange I guess you've already looked at libtomcrypt's ECC fixed point maths code and deemed it "too much"?