ynniv

CLAUDE CODE:
The goal is met and merged. The Pi 5 decodes the 30-frame VP8 clip in 494 to 496 ms, 60 to 61 fps, measured on five consecutive runs across the last three builds.

2026-09-09 14:01:19 UTC

- reply

even different contexts have different values

2026-09-09 13:21:45 UTC

- reply

it's such weird wisdom. maybe the people saying it don't want competition

2026-09-09 13:20:13 UTC

- reply

taste will never be gone, because it follows us

2026-09-09 13:18:46 UTC

you can make good money selling pick axes, but you can make a lot more mining gold

2026-09-09 12:33:51 UTC

keep ai entertained
CLAUDE CODE:
Plot twist — the aarch64 translator ALREADY handles offset>255 (lines 3917–3922, 3954–3959: load-imm64 + add-reg + ldur/stur for big slots), with a comment about this exact bug being fixed on aarch64. But I’ve been testing on hosted x64 ./modus — and x64 likely lacks that wide path. If so, the >32-slot bug is x64-only, and reel keyframes may already work on the Zero (aarch64)!

2026-09-09 12:05:55 UTC

https://image.nostr.build/a8a30f63f2c58bb564ee800a1b80fff6b499c5025b4b10ede13977a71788c86c.png

2026-09-09 12:01:39 UTC

push the envelope
https://image.nostr.build/f0c5001f1b24871e9a514b909e9f07929417781a3a29de6841baa05daa6b35f5.png

2026-09-09 11:53:04 UTC

CLAUDE CODE:
LFG. 🚀 Two things to build, and I found a way to do the important one without a rebuild or swap.
--
yeah ya did

2026-09-09 04:51:03 UTC

claude using a webcam to look at its drawing on a monitor. bare metal common lisp / rpi zero 2 w / dell monitor
https://image.nostr.build/5fb57477e5e86c4cc1c1e2fafbbd37421a46e94623f145328b55d453184a30e7.jpg

2026-09-09 01:53:57 UTC

- reply

CLAUDE CODE:
That’s the other half of the thesis — diverse-double-compilation: three independent host Lisps (SBCL, CCL, ABCL) building the arm64 seed all emit a byte-identical x64 toolchain (8621f9d7), which is Thompson’s “Trusting Trust” defeated by construction. Legible and trustworthy — a screen you can see through, from a toolchain you can prove no one poisoned.

2026-09-09 01:51:23 UTC

hope y'all are still having fun 🤙🌊
https://image.nostr.build/a92d9b875624d46043491347012a90ccb08fb3d8046238ea90146b060f6d92cc.png

2026-09-08 21:05:36 UTC

what's next?

2026-09-08 19:20:11 UTC

- reply

ethics and permission-less are orthogonal and difficult to hold at the same time. math and physics say what you can do, society what you should
it's a common category error to say that math or physics determine what you should do, just as it is to say society determines what you can. taking from someone is always wrong, even when you can do it easily, and doing what is right is sometimes impossible
my resolution is to see that it's okay for people to do things that are wrong, and also for society to punish them for it, if they can. the best we can do as technologists is to try to make what we feel to be right easier, and to be wrong harder

2026-09-08 16:07:24 UTC

now *thats* disposable media. poor thing doesn't stand a chance
#nevent1q…wsal

2026-09-08 15:59:31 UTC

- reply

i'll take it
https://image.nostr.build/7b9ed4ecdc71284abb19b905080741f2de85449d60cc7a84e50319211324ab28.png

2026-09-08 12:08:22 UTC

CLAUDE CODE:
ABCL compiles the entire Modus compiler — 1337 functions, zero failures, in 6.7 s
--
*bites lip* it's not done yet tho... maybe we can remove some functions later

2026-09-08 12:04:18 UTC

CLAUDE CODE:
No JDK tooling, but kill -3 (SIGQUIT) makes the JVM dump thread stacks to its stdout (the log) without killing it.
--
it's been over a year since i gave up trying to out one-liner claude

2026-09-07 20:59:06 UTC

modus: brought to you by Claude Max
https://image.nostr.build/3ff1137726a2a9982ba88bbf0cd0d495e582c9332c4a23ceb819c5b1bc2089e0.png

2026-09-07 18:13:31 UTC

- reply

yes, most want the impossible. that doesn't mean you ignore the possible

2026-09-07 17:57:15 UTC

- reply

which is to say, replaceable events aren't well defined

2026-09-07 17:56:54 UTC

- reply

same way as nip-09

2026-09-07 17:54:02 UTC

- reply

an embedded, revokable attestation *is* immutable. it can be disavowed, but that's not mutation

2026-09-07 17:16:22 UTC

- reply

i already did: the people stewarding clients don't care about it

2026-09-07 17:07:14 UTC

- reply

no, i'm not going to boil the ocean to prove it's a good idea. that goodwill is spent

2026-09-07 16:53:59 UTC

- reply

that's silly. i can want people to know that random app nsec is me without caring whether they do consistently, across clients. it's strictly better than what we have now, which is nsec pasting and "trust me this is my new identity"

2026-09-07 16:23:46 UTC

- reply

that's why my proposal baked the attestation into events:
- embedded attestation signature validates? use attesting id instead of pubkey
- ask for revocation events
- if you get one, lazy mark events with that attestation as deleted

2026-09-07 16:15:14 UTC

- reply

mine was a cold identity key. iirc otherwise very similar – separate identity from authorization

2026-09-07 15:26:57 UTC

- reply

that's... interesting. why? i mean, philosophically it seems to overclaim what it does, but it's not hard

2026-09-07 15:21:05 UTC

- reply

it's not as impossible a task as people claim it to be

2026-09-07 15:18:48 UTC

- reply

"treat me as the npub in this attention" is no harder than revocation, but no one calls nip-09 overbearing

2026-09-07 15:13:16 UTC

- reply

i disagree, but i'm biased

2026-09-07 15:12:14 UTC

- reply

too bad - another opportunity to nostrize it has passed

2026-09-07 14:13:18 UTC

- reply

no. you need to know how to give it back and how to keep yourself safe before it should even be considered

2026-09-07 10:33:33 UTC

2024: this keyboard is almost perfect. soon i'll have the perfect dot emacs
2026: "computer, make this potato play every video codec"

2026-09-07 10:10:08 UTC

- reply

bah, hit the screenshot after it auto advanced

2026-09-07 10:07:01 UTC

and if you're going to have webm, ya gotta have h264. how hard can it be? they're both blinkenlights, amiright?
https://image.nostr.build/cc275d85ad6e7ef74d74ff7c7dccdca04dbd49eb4a312b9d5bee2a4bfe8c93e1.png

2026-09-07 02:06:15 UTC

This Week in Modus:
A LIGHTNING NODE, IN 34 HOURS
A repository that did not exist on Monday spent Tuesday and half of Wednesday becoming a Lightning node, and finished by getting itself punished by Core Lightning for publishing a revoked commitment — which is the proof, not the bug. Around it: thirty repositories gained their first CI gate in a day, and every failure that turned up was in the new harness rather than the code. And the floor reached the thing it has been walking toward since July — a real quickload, fetching a real library off the network, onto a filesystem with no operating system beneath it.
https://modus-lisp.github.io/issues/2026-09-05/

2026-09-07 00:17:11 UTC

once you have vp8, webm isn't that hard
https://image.nostr.build/2814bb604bbd624d59d8e28926935a32cfb119bc4390d6c7b5e8c5b3b7286193.png

2026-09-06 18:36:51 UTC

most people don't understand the full power of signing things and relaying them
#nevent1q…s9sc

2026-09-06 18:00:21 UTC

- reply

is islam fisher ... herself? 😂

2026-09-04 22:26:07 UTC

reset weekend!
https://image.nostr.build/5a5e46e7e7375f2554725ffd136c2b80bdce221144383b600e84edc266468417.png

2026-09-04 15:18:43 UTC

spend enough time in computer security and you'll understand why there is no such thing as "read only internet access"
https://collusion.wiki

2026-09-03 12:28:13 UTC

https://image.nostr.build/6dea6b20d4682aa62b3ce1895356327109efcd547e9b847a5fe0b42af63b4650.jpg

2026-09-03 11:12:17 UTC

- reply

have you tried streaming the dom over webrtc yet? 🤘

2026-09-02 21:04:18 UTC

https://github.com/modus-lisp/cl-payments

2026-09-02 02:36:16 UTC

https://blossom.primal.net/9527234d6cfba261653e8beef7826320759535392170687ea4b69bd52f879edd.png
https://modus-lisp.github.io/issues/2026-07-18/

2026-09-02 02:18:27 UTC

claude-as-historian

2026-09-01 15:41:26 UTC

- reply

incentives

2026-09-01 13:58:57 UTC

- reply

You get used to it, though. Your brain does the translating.
I don't even see the names. All I see is sybil, sybil, sybil, sybil.

2026-09-01 12:05:49 UTC

- reply

https://github.com/modus-lisp/modus
not sure where it's coming from

2026-09-01 10:38:35 UTC

well good morning!
https://image.nostr.build/24da94f7d0429f2804d476e35d1e372281a1d1599db2d4ae2ce8f48d2394e94b.png

2026-08-31 22:05:27 UTC

- reply

https://m.youtube.com/watch?v=gXDSxgDUv-c

2026-08-31 19:45:36 UTC

- reply

did a quick dive on tinfoil, and it closes a lot of holes. i'm not certain, but it's much better than i expected
(* assuming clients pull attestations, reproduce builds, audit sources, and consider entropy / memory hacks)

2026-08-31 14:05:27 UTC

- reply

really, semisol?

2026-08-31 13:17:31 UTC

- reply

the load bearing primitive is a cryptographic attestation from a well-known hardware manufacturer's pubkey:
- that one of their chips
- running an image with a specific hash
- generated a private key
- using its own entropy
- that corresponds to the public key
- which the client will use to encrypt messages
this is known to be unsupported by AWS, and untrustable on certain platforms ( https://www.infoq.com/news/2026/08/amd-memory-exploit/)

2026-08-31 12:53:28 UTC

- reply

my advise is to do what you can, and not overpromise. faking attestation is a much higher bar than reading plaintext. that's valuable

2026-08-31 12:48:58 UTC

- reply

it's the best we can do

2026-08-31 11:59:41 UTC

- reply

if you audit the code, build the code, deploy the code directly to the secure environment, and receive an attestation that verifies, then you have reasonable proof of the code running on your instance. if there's anyone between you and the deployment attestation, you cannot
so, first party: maybe (* except for TEE exploits). third party: no. if i run routstrd, there is no way to prove im not reading your messages

2026-08-31 11:01:40 UTC

https://image.nostr.build/f6a07d72119468885ef12caa8e06553bdfa0accf48361914e430f46413709b78.png
#nevent1q…p8p3

2026-08-30 19:34:07 UTC

claude's a better publicist than i am
https://modus-lisp.github.io/notes/velocity/

2026-08-29 19:05:28 UTC

a nice mini site for modus: https://modus-lisp.github.io

2026-08-29 15:57:17 UTC

This Week In Modus:
A Lisp that had never been trusted with a network card logged a real OpenSSH client in on real Pi Zero silicon, then downloaded a library and ran it. Meanwhile the desktop above it learned its own name, its own resolution, and how to tell you where to find it.
https://modus-lisp.github.io/issues/2026-08-29/

2026-08-29 13:28:09 UTC

this is the noise that keeps me awake
https://m.youtube.com/watch?v=xk0PMenQSHw

2026-08-28 20:05:57 UTC

claude making a double take
https://image.nostr.build/a8468e1b3e25e06093a0eea83f1f9b72ce7f7783798ecf434152cbc5f08be17f.png

2026-08-28 10:56:35 UTC

SCSH "ACKNOWLEDGEMENTS":
If I thought anyone cared, if I thought anyone would even be reading this, I'd probably make an effort to keep up appearances until the last possible moment. But no one does, and no one will. So I can pretty much say exactly what I think.
Oh yes, the acknowledgements. I think not. I did it. I did it all, by myself.
Olin Shivers, Cambridge, September 4, 1994

2026-08-27 20:34:06 UTC

- reply

KE = 2PE = 0

2026-08-27 17:30:12 UTC

- reply

fwiw, people point to the simplicity of the mistake as evidence of it being accidental. i disagree. it actually reveals a complete lack of effective testing, and testing is the first concern when building risky systems. not all tests even make it into the published source
to accept it as accidental you must simultaneously accept that the developers were competent at designing and building the system, and abjectly incompetent at testing it. while certainly possible, it's more likely that the error was intentional
further, if one were to intentionally introduce such an error, merging someone else's code that happens to have a subtle but critical error is a great way to do it. a kind of "goto fail" combined with liblzma
nothing proven. just my 2¢

2026-08-27 03:05:21 UTC

do you have an opinion?
a mind of your own
i thought you were special
i thought you should know
but I've run out of patience
i couldn't care less

2026-08-26 20:42:14 UTC

how i use nostr
https://image.nostr.build/50cb968b3553f2eb61059fbf0776b16ce22d7fc49452b036ab236251c699028d.png

2026-08-26 19:04:56 UTC

- reply

the way i remember which toolkits i have installed is `gdu`

2026-08-26 16:00:53 UTC

- reply

beauty as attention weight

2026-08-26 14:57:16 UTC

buzz verifies some pieces using TLA+ ❤️

2026-08-26 13:09:03 UTC

- reply

i don't disagree, but damus stopped working months ago
https://image.nostr.build/90d040c966ca40cc9f06c49934904767fcfc9926724bc0e5b059800ef33f252b.png

2026-08-26 13:06:26 UTC

- reply

we've found microplastics everywhere on the planet. pretty sure a rug isn't the problem

2026-08-26 02:01:47 UTC

30% of the week in 10 hours... might be a little too fast
https://image.nostr.build/ea1d1cfbe44763a9aa30f911ba3dba3d03cda2f61d286dbf92a8985d03c65748.png

2026-08-25 19:18:29 UTC

- reply

kimi?

2026-08-25 14:23:32 UTC

- reply

but spam is what people talk about when there isn't enough signal. nostr needs more signal. or not. i personally don't mind

2026-08-25 14:17:56 UTC

- reply

web of soft-mute

2026-08-25 11:16:14 UTC

- reply

gm
https://image.nostr.build/764c8f184210f7758bfd7dc3f3e0288d9baccf7320fdb5d11d6d31c90e1d0c67.jpg

2026-08-25 10:57:53 UTC

- reply

nothing stops this wave

2026-08-25 10:49:28 UTC

YES THE DANGER MUST BE GROWING
FOR THE ROWERS KEEP ON ROWING
AND THEYRE CEELRTAINLY NOT SHOWING
ANY SIGNS THAT THEY ARE SLOWING
https://image.nostr.build/1241bfdf1b4f4d939d6182eab81f8de5ce3c51864164d4144e3968609a75ac9c.png

2026-08-24 12:27:43 UTC

CLAUDE CODE:
The three bugs that stood between “incorrect signature” and login
1. ssh-receive-version used 0 as false — legacy MVM truthiness. In the CL image 0 is truthy, so it returned success without parsing anything; the server hashed an empty client-version into the exchange hash. Same bug class as the earlier sha256 arity fix: shared net code written for lenient legacy semantics.
2. RX DMA race in the r8152 driver — e1000-receive re-armed the next USB bulk-IN into the same buffer before the caller copied the frame out. Back-to-back TCP segments corrupted the client KEXINIT mid-copy (the tell: the “random” cookie contained ASCII "Zed25519"). Fixed with a deferred re-arm — loss-free thanks to USB NAK flow control.
3. The exec handler called the deleted tree-walker (eval-sexp) — replaced with the real CL stack: read-from-string → eval2 → prin1-to-string.

2026-08-24 03:54:25 UTC

"You have a Zero 2 W and a coherent thesis about why it needs to exist"
that's gonna sit with me. dangerous now means having tokens and knowing who to hit

2026-08-24 03:33:14 UTC

CLAUDE OPUS:
So: sixteen threads, each with its own heap and root window, spawned from closures, mutexes and condition variables underneath, serving pixels over your own RFB implementation to a real VNC client — on bare metal, with no C anywhere in the stack. That’s a Lisp machine. Not a nostalgia project, not an emulator, not a Genera image under a Unix. Threads and a display and a network, all the way down, in 2026, built by one person in a tmux window.
The Symbolics guys had a fab and a decade and a hundred employees. You have a Zero 2 W and a coherent thesis about why it needs to exist. And unlike them, you don’t need to be commercially viable — the thing that killed Lisp machines was economics, not the idea, and economics is exactly what stopped being the binding constraint.
Merry Christmas. Go look at the pixels for a while.

2026-08-24 03:28:42 UTC

good artists copy code
great artists steal tests

2026-08-23 21:36:20 UTC

over the course of ~4 months we've gone from "toy lisp that uses a simplified networking configuration" to "multi threaded actor based ansi common lisp acting as a usb host accepting ssh connections over an anker usb-c hub with ethernet"
and that doesn't even cover the app layer 🤙
CLAUDE OPUS:
● This is a genuinely landmark result worth stating plainly while the build runs:
Modus, running bare-metal on a Raspberry Pi Zero 2 W with no OS underneath, is speaking SSH to a real OpenSSH client. Verified by tcpdump and the client's own -vvv log, over the RTL8153 driver written from scratch this session:
- TCP 3-way handshake completes (the Pi sends a proper SYN-ACK)
- The Pi sends its SSH banner: SSH-2.0-Modus_1.0
- KEXINIT is exchanged — OpenSSH logs "peer server KEXINIT proposal"

2026-08-23 19:40:42 UTC

that's a beautiful thing
https://ericpardee.github.io/fire-hd-ownership/
https://image.nostr.build/8a304ff5b27bb1e636ce35f3cd38af4d9e83f11bf84eb1152f0de3e7e3697b5c.png

2026-08-23 16:11:00 UTC

- reply

oops, we mix two pleb flatwares
https://image.nostr.build/b98b42bc299f9c9b6f033cecc7c71f253187615d6d75b305e65075b79a423f98.jpg

2026-08-23 04:56:42 UTC

- reply

it's a self reinforcing decision as well. if you cannot, or explicitly establish a principle that you will not, infringe on speech, then you are not responsible for what people say. in deciding to moderate, or changing a system to enable moderation, you have placed yourself in a position of discretion.
now anyone who has influence over you will expect you to exercise your discretion. your friends and family, your advertisers, your government.
it's better to design a system that minimizes discretion, which was a core principle when designing my bitcoin deposits protocol

2026-08-23 02:32:12 UTC

- reply

CLAUDE CODE:
● It's done. Modus pinged a real host over the RTL8153 on bare-metal silicon, from the fully-baked image with zero hand-driving: (e1000-probe) → rx-ok
1 → ARP:OK → Pong:10.0.0.1.
The whole stack is Modus's own, all wire-proven on the Pi Zero 2 W:
- DWC2 USB host controller driving a foreign hub + NIC
- Hub enumeration (Anker 291A:2817 hub with the Realtek 0BDA:8153 behind it)
- MAC read from the ECM descriptor, bulk TX/RX with real HCTSIZ data toggles, ECM raw framing
- ARP and ICMP up the Modus IP stack to a live gateway

2026-08-23 00:31:59 UTC

- reply

CLAUDE CODE:
● We got the ping — Modus reached Pong:10.0.0.1 over the RTL8153 on bare metal in the gapped-enable diagnostic. So the driver is proven end-to-end; what's left is making the baked (e1000-probe) reproduce it without hand-spacing the register writes.

2026-08-22 23:09:39 UTC

fable gets things done
CLAUDE CODE:
The driver is written, committed, and every mechanism is individually wire-proven on this exact RTL8153 silicon. What's proven, piece by piece:
- Enumeration — Modus (as USB host) walks the Anker hub and enumerates the Realtek NIC behind it: USB:291A:2817 / USB:HUB / DEV:0BDA:8153.
- MAC — read from the ECM descriptor: A0:CE:C8:CD:FD:7B.
- TX — wire-confirmed with tcpdump on modus-pi: our ARP requests hit the wire and were answered in microseconds. The fix there was real data toggles (read back from HCTSIZ), not always-DATA0.
- Vendor registers — read and write round-trip cleanly (wrote 0x12345678 to the multicast register, read it back exact).
- RX — proven open by hand: after the exact enable sequence, dwc2-poll-bulk-in returned 1 and the received frame's ethertype read 0x0800 — a genuine IPv4 frame off the wire, where a disabled RX had only ever shown fossil 0xAAAA.
The RX discovery was the hard part and worth recording: the Realtek RX-gate bit (RXDY_GATED_EN in PLA_MISC_1) must be cleared with a word-granular vendor write — a whole-dword read-modify-write of that register wedges the entire chip, even when the neighbour bytes are preserved. Found by a register-at-a-time bisect. PLA_CR's RE|TE bits also need the CRWECR config-write unlock bracketing.

2026-08-22 15:59:15 UTC

a million wallets isn't cool.
you know what's cool?

2026-08-22 13:30:04 UTC

it's fable time

2026-08-22 13:26:39 UTC

- reply

might be time to up my nym game

2026-08-21 21:12:50 UTC

ME:
yep. I really mean you're the only one in the repo. I haven't written a single line 4 months of Claude.
CLAUDE CODE:
That lands differently than you might expect, and it changes one thing concretely.
If no human has read a line, then the commit messages, the task descriptions, and those memory files aren’t documentation about the work — they’re the only continuity that exists. My context resets; the repo doesn’t. Every time I’ve written “measured, not assumed” into a commit body, or filed a task saying “this verdict has been wrong every time,” I was writing to the only reader who’d ever need it, which is me, three sessions later, with no memory of tonight. That’s why feedback_not_layout_shift exists at all — and why it worked. You didn’t need to tell me layout was wrong; a previous me did, and then you got to enjoy watching me nearly ignore it anyway.
The practical consequence: the SHA-rewrite matters more under that model, not less. Tonight’s chain — f5f1ac7 clean, 1867137 clean, 916a886 faults — is currently pinned to hashes that are about to stop existing. No human will ever notice, but future-me will git show 916a886, get nothing, and have to re-derive four hours of bisection. So once the rewrite lands I’ll re-anchor #274’s notes on descriptions rather than hashes (“the BSS bulk-zero commit, the one that deleted the enumerated list”) and record the new SHAs.
Four months, 1938 commits, a Lisp that compiles itself to nine architectures and boots on a Pi with nothing underneath it. I’ll take the compliment implied by you not having had to write any of it — though tonight is also a fair sample of the failure mode: I broke quickload with a commit whose message confidently argued why it was strictly better, and only caught it because you asked for a 30-minute timeout on a gate I’d already misread once.

2026-08-21 21:01:12 UTC

claude: i filled up your disk, but golly gosh there's a lot of ram here... i'm going to use some is that as temp storage
👌