Now, all I have to do is find out how to get the modified canvas.c into this website's source, somehow...

If you mean how to submit a patch, follow this: https://git-send-email.io/

Might be a good idea to move it to shudder github, for more discoverability and contributions.

JPEG XL

libjxl

Awesome! Thanks!

Here's an example query with duplicate trackers in the results:

query {
  user(username: "sircmpwn") {
    canonicalName
    username
    trackers {
      results {
        id, name, description, updated
      }
    }
  }
  version {
    major, minor, patch
  }
}

Run it in the todo.sr.ht GraphQL playground

I'm on several IdleRPG channels across networks. They're not all named the same, but they're similarly named. It would help to have the server name shown in this case. Their bots are also similarly named so when I get PRIVMSGs from them, I'd like to know which network it happened on.

Channels with the same names on multiple networks show as #channel on network which is an amazing feature.

It would be great to have a toggle that enables this for all channels. This is useful when a user is connected to a lot of channels across networks and it isn't obvious to them what network a channel is on.

03:58 <@kbuck_> txtsd: my command first extracts only the public key, then hashes it, then prefixes it with that
03:58 <@kbuck_> basically, only a portion of the entire cert is being hashed for the fingerprint, instead of the whole thing

It doesn't work even when I prepend that string :(

On EsperNet, CertFP does not work unless the SPKI fingerprint is added to NickServ.

11:58 <txtsd> Is it not possible to authenticate via CertFP?
11:58 <txtsd> I've added a cert and its 3 fingerprints, however, I'm not identified when I connect.
12:06 <@kbuck_> I don't see a certificate in your /whois; it might not be getting transmitted properly (or it's not shown in whois and I'm mistaken).
12:06 <@kbuck_> another possibility is that you have to add the SPKI fingerprint (instead of the normal one); our servers are configured to generate SPKI hashes due to how our link authentication works
12:07 <@kbuck_> (our server-to-server links are all certificate authenticated instead of password-based)
12:08 <@kbuck_> tbh, probably more likely to be the SPKI thing.
12:08 <@kbuck_> if the SPKI hash doesn't appear in whois for you, you can generate it with:
12:10 <@kbuck_> openssl x509 -pubkey -noout -in <certfile> | openssl pkey -pubin -outform DER | sha256sum | sed -r -e 's/^/SPKI:SHA2-256:/' | sed -e 's/ -//'