Any idea where to find the source? Wondering how it's set up.

pKVM is upstream in mainline Linux.

AOSP, https://android.googlesource.com/platform/packages/modules/V...

GrapheneOS, https://github.com/GrapheneOS/platform_packages_modules_Virt... & https://x.com/tuxpizza/status/1900431745146888488

Would certificate pinning also remove the first option? I wonder if we are moving to a system where inspecting your own traffic isn't a viable option anymore, am I missing a workaround?

If you control the machine you can always defeat pinning, given enough effort. But for an IoT device, yeah, we're already there.

I mean that's something you need to do every time a DB is involved. Not really an argument against ETAGS.

Of course there's a conflict of interest. It's their right to promote their solution but I would never take their word for it.

Sometimes I wish I had the kind of education that allows you to interpret Terms of Use, Privacy Notices and other legal mumbojumbo in a way that answers my questions. It's great practice if you like cryptic crosswords though.

Is that the correct video for CPS?

Yes, via an old joke. See https://wiki.call-cc.org/chicken-compilation-process#cps-con... .

Do you have a writeup of the technical details? How does this exploit (without reading the code and reverse engineering it)?

I'm not the author, but there's a brief explanation on the GitHub README:

(https://github.com/zacharyreese/DualQRCode)

The generator creates two separate QR codes with high error correction (Level H) and combines them into a single image using pixel splicing. Each cell that differs between the two QR codes is split in two, creating a pattern that can be interpreted differently based on the scanning angle.

I'm curious what the compressed text looks like. Anyone have an example?

If it is within cooee of state of the art the compressed text should look like a pile of random bits.

If it looks like anything at all other than randomness then you can describe whatever it is that it looks like to get more compression.

Binary goo, barely distinguishable from random data, if at all. The arithmetic coder will make sure of that.

It's the nature of compression: Any discernible pattern could have been exploited for further compression.

I really like "archive" and "tag" overviews. I don't want to scroll through every post in full as a way of finding an entry that interests me. Not really a blog but Hackaday on mobile is really bad at this. It's kind of hard to filter for interesting stuff without having something specific to search for.

Yes, also having some "related" posts is nice.

Here is my way for jekyll, which I copy-pasted-adapted.

https://blog.pwkf.org/2022/08/13/adding-navigation-tags.html

Do you have a repo for your Guile solutions to AoC? Would love to see it.