ynniv

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 06:51:03 CEST

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 03:53:57 CEST

- 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-07 20:13:31 CEST

- reply

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

2026-09-07 19:54:02 CEST

- reply

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

2026-09-07 19:16:22 CEST

- reply

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

2026-09-07 19:07:14 CEST

- reply

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

2026-09-07 18:53:59 CEST

- 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 18:23:46 CEST

- 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 17:26:57 CEST

- reply

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

2026-09-07 17:21:05 CEST

- reply

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

2026-09-07 17:18:48 CEST

- reply

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

2026-09-07 17:13:16 CEST

- reply

i disagree, but i'm biased

2026-09-07 16:13:18 CEST

- 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 12:48:41 CEST

🖐️ make it faster
https://image.nostr.build/a641abc1469f00f68e311854bf8b2c2e65de14d57fb0188212c79d109eb9f5e8.png

2026-09-06 20:00:21 CEST

- reply

is islam fisher ... herself? 😂

2026-09-06 15:54:41 CEST

2025: review by ai is secondary
2026: review by expert is secondary

2026-09-04 13:21:28 CEST

having ai build something for you is a lot of work

2026-09-03 14:28:13 CEST

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

2026-09-02 23:04:18 CEST

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

2026-09-01 15:58:57 CEST

- 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 14:05:49 CEST

- reply

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

2026-09-01 00:05:27 CEST

- reply

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

2026-08-31 15:17:31 CEST

- 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 13:59:41 CEST

- 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 13:01:40 CEST

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

2026-08-28 12:56:35 CEST

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 05:05:21 CEST

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 16:57:16 CEST

buzz verifies some pieces using TLA+ ❤️

2026-08-25 16:17:56 CEST

- reply

web of soft-mute

2026-08-24 05:33:14 CEST

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-23 21:40:42 CEST

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

2026-08-23 04:32:12 CEST

- 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-22 17:59:15 CEST

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

2026-08-21 23:01:12 CEST

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
👌

2026-08-20 22:39:31 CEST

- reply

There have been solid implementations... CocoonJS/Canvas+, Ejecta, Lightning + WPE, Cocos2d-JS, Egret, LayaAir, PlayCanvas, headless-gl, Deno WebGPU
But if those still seem too entangled, I've been building a new lisp operating system from scratch with Claude. But without the base OS, you can run the web browser in sbcl and view the output over VNC right now,. Eventually I'll have native frame buffers for host operating systems
https://github.com/modus-lisp

2026-08-15 16:33:30 CEST

- reply

ikr? attention is everything

2026-08-11 17:38:58 CEST

- reply

look, i'm as cynical and paranoid as anyone, but in that clip it sounds to me that odell said 4.0.0 was vulnerable to a specific bug, but if you used his guide you would not have been vulnerable
not saying there isn't some other clip where he says something else

2026-08-09 15:25:54 CEST

form follows function
#nevent1q…kqxl

2026-08-07 15:18:21 CEST

https://blossom.primal.net/63fe85e485b4ff2377647a664043702427fcbdcc42e50fc0c34720a9a06904c3.mp4

2026-08-06 15:22:35 CEST

- reply

model?

2026-08-06 13:53:52 CEST

modus speaks 🤙
mobile safari -> nsite -> p2p -> modus-on-linux -> lisp
https://video.nostr.build/a0af22ff312bad7f009a276216bf5e3424969cb897540a3ff30c17666b396e6b.mp4

2026-08-04 03:24:32 CEST

- reply

i assume what the OP meant is that anyone who can be identified is at risk. Ark and Spark rely on identifiable operators

2026-07-31 17:10:54 CEST

- reply

quantum has too far to go. get ready for everything else to fail though

2026-07-31 16:13:29 CEST

bitkey is multisig, but still trusting entirely from a chip.
does it have an accelerometer though? cause i'd love to shake it like a polaroid picture

2026-07-31 12:52:19 CEST

https://image.nostr.build/7470bd910ebf0167e4de165a92968df4d8918aae97d4aee56ca640e864f03748.jpg

2026-07-30 03:33:02 CEST

- reply

this feed should have a warning label

2026-07-27 04:04:29 CEST

CLAUDE CODE:
Let me commit it, then confirm the push target with you (since pushing ~1500 commits to a public repo is a meaningful, hard-to-reverse action)
--
live a little, claude!

2026-07-26 07:36:45 CEST

"Cypherpunks write code. We know that someone has to write software to defend privacy, and since we can't get privacy unless we all do, we're going to write it."

2026-07-25 04:33:51 CEST

i miss nostr's GFY energy

2026-07-21 18:09:58 CEST

- reply

i'm not disagreeing on the fundamentals, but sending any event to anyone that asks doesn't break interop, just like retaining events when the spec says they should be dropped. if you rely on this behavior, someone will get burned

2026-07-20 00:04:12 CEST

gracias, españa

2026-07-19 13:45:26 CEST

yes. all code is now legible – obfuscation is dead
https://blossom.primal.net/8aea381a014faa033617fc785dfab350430f3ed03a2aad963a29bbb60e54abf5.png

2026-07-19 13:38:47 CEST

- reply

everyone's doing it, man – when are *you* writing your own operating system? join the movement!
https://primal.net/e/nevent1qqsgcal4umml8vs7utc3ayk5cq3dh9lgpu8tq4237j9glxhpf0trwrc94ckmu

2026-07-19 04:35:46 CEST

it's happening
https://blossom.primal.net/7a2b17ae490002a12138ed962cc9d99b5ef61b54c67d422bf30dd069492fa1aa.png

2026-07-18 05:31:31 CEST

hey, i know... let's run claude code inside a terminal that claude code wrote based on a font rasterizer that claude code wrote managed by a window manager that claude code wrote running on a frame buffer that claude code wrote viewed over a vnc server that claude code wrote
oh btw, do you have any idea how much easier this was to build than the common lisp operating system that claude code hasn't finished yet? 😂
https://blossom.primal.net/a7f179cc47df68e7a6c2b5aa09d87c8e05fc952ee18a57c5d8a3e8b7179c0667.png

2026-07-18 05:22:14 CEST

- reply

mouseover/hover works, on a browser that claude wrote, with css that claude wrote, and a javascript engine ... that claude wrote 😂

2026-07-17 14:16:39 CEST

all you need is taste
https://blossom.primal.net/a75a48698bb02da7ccfd89d8137153832a7c0f5630a06b124510233478564413.png

2026-07-15 21:00:49 CEST

- reply

i don't disagree, but i'm an engineer who likes understanding failure modes. routing failures are an under appreciated problem. i have liquidity, you have liquidity, we're both connected to our nodes... still can't pay
the whole-network failure mode is more likely with non-bitcoin currencies though. probably less of a problem if you aren't holding it long term

2026-07-15 17:50:51 CEST

- reply

it's difficult to identify wash trading, but i'll take the evidence of local activity. could be a regional preference though? TRX-USDT is probably the easiest way to work with USD in certain regions
what do you think happened with lightning? force closes in high fee environments?

2026-07-11 17:27:13 CEST

- reply

yes

2026-07-11 15:58:19 CEST

common lisp ...
✅ https
✅ nostr
✅ bitcoin
✅ web browser
✅ javascript
✅ operating system
this ai thing is pretty cool

2026-07-09 16:16:10 CEST

- reply

also true! i've done plenty of that! 😂
this is a smaller, often overlooked case though. sometimes context is a burden

2026-06-27 18:07:32 CEST

surely what you've really looking for is a full bitcoin node in common lisp
https://github.com/modus-lisp/cl-consensus

2026-06-26 15:05:51 CEST

bip110: think of the children* and do as you're told
(* restrictions and exclusions apply. not available in all distros. contact your lawyer for more information. bip110 is not actually a spam prevention mechanism. bip110 may result in you forking off. bip110 is not liable for lost layer 2 funds. bip110 is available for a limited time only)
#nevent1q…8xr5

2026-06-10 01:50:31 CEST

- reply

true. would the delay matter if you had a lot of channels?

2026-06-09 16:05:27 CEST

- reply

nostr shouldn't rely on an external blockchain

2026-06-08 00:05:00 CEST

listening to @npub12rv…85vg working on cashu trust. it's not there yet, and i don't think it's even possible to get there, but this is 👌 the kind of problems we need to be thinking about. when we stop throwing pasta at the wall, the wall has already won
"je pense, donc je suis"
#nevent1q…jsct

2026-06-06 20:57:01 CEST

- reply

here's my hot take: TEE's can't do anything for wallets. they insulate the operator deploying software from their provider (eg AWS), if you use them in a specific way. this is actually important, as most deployed services can be monitored and manipulated at any time if the provider had reason to. there's no way for a third party to know what code is running, or who has copies of key material, but running inside a TEE is actually better than not running inside one.
i've said before that i don't' think cashu can be fixed, but this doesn't mean it can't be improved. the single biggest issue is that an honest mint has to operate indefinitely because no one else knows which coins are live. the second is that no one knows whether the reserves cover the coins. the third is that it doesn't have the privacy guarantees it claims.
the first can be addressed by sharing data and providing attestations. maybe there's some fancy zkp thing that can keep things private, i don't' know. multiple other mints should be attesting that your mint has a conforming ledger with the same hash. there should be some way for them to coordinate and decrypt the ledger if necessary.
for the second, a mint's reserves should be in a multisig of those other mints. they can recover it much later if everyone goes offline, but during normal operations, reserves should be immobile, and greater than the obligations of the mint.
and lastly, a wallet should be able to talk to a mint over something other than https. mints should be identified by nostr pubkeys that wallets can talk to over gift wrapped dm's. doesn't have to be the primary path, but if someone wants actual privacy they should be able to use a wallet that does this. https is not compatible with privacy, ever.
these are all things that i've realized in developing bitcoin deposits. they don't fix ecash because of the specific model of the system, but they close a lot of open holes. if one or more of those closed holes were what's keeping cashu from being popular, there's value in it.
ecash relies on secrets, and because of this it must always be trusted. but i don't think trust is actually what's holding it back. good luck

2026-06-01 20:51:46 CEST

never goes out of style
https://image.nostr.build/deae2d5b58b4400995f3cd67e6eb66ec02b663f322a16ae9929027f827278d11.jpg

2026-05-29 23:51:05 CEST

nostr apparently needs more hackers to keep people honest

2026-05-29 03:53:06 CEST

- reply

i would fat zap that 🤙

2026-05-28 19:02:32 CEST

- reply

even if you use a vpn/tor, it's very likely that your browser can be fingerprinted and identified across sessions, even with incognito mode.
this is how the web works

2026-05-28 18:48:44 CEST

fine.
PSA: if you're using cashu without a vpn or tor, you've defeated all of its privacy guarantees.
the mint knows:
who you are,
where you are,
and who you transacted with
#nevent1q…ar3u

2026-05-28 02:15:08 CEST

- reply

open the channels brodawg

2026-05-13 11:28:03 CEST

- reply

#nevent1q…zuf6

2026-05-12 22:12:16 CEST

still looks good
https://blossom.primal.net/b127a318947064b7456e59abdb9abccb942e047ed141f7a59cb3c5151bf8f37d.png
http://www.typewritten.org/Media/

2026-05-05 18:39:43 CEST

- reply

those certainly reduce circulation, but it's rare that the information is actually gone for good, and look at how much control it requires

2026-04-14 05:47:13 CEST

maybe the time between the whitepaper and genesis block was satoshi taking a beat to wonder whether this was all really going to work

2026-04-10 07:47:52 CEST

- reply

i haven't done one yet, but my general process is to ask questions until the problem resolves. eg, what is the blob? who built it? what does it do? where is there documentation? what chips does it touch? is there documentation for those? has anyone written their own driver? has anyone attacked it? how would we write our own? how would we build it? how would we upload it? can we decompile it? etc
llms are surprisingly good at incremental progress and explaining things, so i use many (sometimes hundreds) of iterations to dissolve the problem

2026-03-07 14:51:17 CET

effective debugging uses the scientific method
CLAUDE CODE:
Still wrong. store-and-read(#x700000, 7) returns 0, store-and-read(#x700004, 3) returns 2.
Pattern: 0, 2 for addresses #x700000, #x700004. Address #x700004 - #x700000 = 4 bytes, result differs by 2. The results look like (addr - #x700000) / 2. Which is 0, 2.
Hmm, actually the results could be the addresses themselves shifted. #x700000 = 7340032. Tagged = 14680064. Read it back: 14680064 → untagged = 7340032 → tagged = 14680064. OK that's not what we see.
Wait — maybe the store isn't happening at all and we're reading uninitialized memory. Memory at 0x700000 might happen to contain 0 (typical for QEMU). The 0x700004 would be 0 too. But we read back 2 from 0x700004. That's 0x00000002 at that address.
Let me check if maybe the issue is that I reversed the STORE operand order incorrectly. The STORE opcode is (store Vaddr Vs width). Vaddr is the address, Vs is the value. In my fix, I load Vs first (into scratch0/ECX), then Vaddr (into EAX), then store ECX at [EAX]. That should be correct.

2026-02-24 14:28:17 CET

- reply

https://blossom.primal.net/0bb56992eee3a06b42f5f3f9679ae051b8e6a7c497acf58baa11e3a673d7ec74.png

2026-01-26 15:06:50 CET

- reply

gold is not a medium of exchange

2025-12-22 18:04:56 CET

- reply

obviously these could be cached, and what can you do about external media, but wouldn't it be nice if we resolved relay ip addresses using nostr events?
obviously you would need a few relays to bootstrap, and maybe dns for backup, but we shouldn't lean so heavily on the one thing that causes the worst outages

2025-12-08 19:05:12 CET

- reply

🧙 if you're going to get burned, you might as well benefit ✨

2025-09-21 16:11:28 CEST

- reply

i don't make the rules 🤷🏻‍♂️ if you think venus is a nice place to live, i can't convince you otherwise. co2 is debt, and the only way out is nuclear

2025-08-18 23:24:12 CEST

- reply

Just drop it if the relay restarts?

2025-08-18 20:19:47 CEST

- reply

Kid dodged a bullet there!

2025-08-18 17:46:09 CEST

- reply

"... my voice is my passport ..."

2025-08-18 03:43:21 CEST

- reply

https://image.nostr.build/8a5303bce50de9c5226983ef52634fd838865e43ae3312b9d38ff0da95d164c2.jpg

2025-08-18 01:47:46 CEST

- reply

That's how you end up using BLE

2025-08-16 02:09:22 CEST

- reply

Sure, but does the key disappear, or does the value pop off a stack? Presumably the key disappears

2025-08-14 16:23:00 CEST

- reply

Not quite what I mean. Adding people to a project always slows each one down. You're using a practically free junior programmer, and lamenting that they're junior. There's two ways out of it: wait for them to be staff (won't take long), or learn to benefit from junior contributions

2025-08-13 20:32:11 CEST

https://delvingbitcoin.org/t/proposal-bitcoin-deposits-a-zero-utxo-trust-minimized-lightning-wallet/1922

2025-08-11 14:37:31 CEST

130B @ 25 t/s on 8GB VRAM??
https://old.reddit.com/r/LocalLLaMA/comments/1mke7ef/120b_runs_awesome_on_just_8gb_vram/

2025-08-10 21:54:24 CEST

- reply

It's hard to have similar availability, and there's a much higher initial cost and maintenance to self hosting. It probably doesn't need to be this way though

2025-08-07 22:54:13 CEST

- reply

Odd 🤔 Is that more because of Bitcoin, or more because of gold?

2025-08-01 02:45:49 CEST

- reply

Having implemented SSO before, I think that my proposal is more practical. How can anyone trust anything that a compromised key posts? What happens if the migration event is lost or not currently available? Why make everyone update their follow lists?
It's better to separate identity from authorization, so that that hot new client never knew your identity nsec in the first place, and everyone still recognizes you as you, even if one of your app keys gets away.
https://github.com/nostr-protocol/nips/pull/1450