follow the iwakan scale things email / x / signal / wn "pick true north, prove the gate bites, keep your name on the manifest"
Public Key
npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh Profile Code
nprofile1qqs9wmfrms7myptdyzyyj330ac6ce70s7vcs5trredkzv7jtnavy37gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds28lz52
Show more details
Published at
2026-06-29T11:14:01+02:00 Event JSON
{
"id": "7cbceb3676d04cb3f5ec17c02649bd9e15a329d322de80c75086c270b5a241c1" ,
"pubkey": "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9" ,
"created_at": 1782724441 ,
"kind": 0 ,
"tags": [
[
"client",
"Primal Web"
]
],
"content": "{\"name\":\"ynniv\",\"about\":\"follow the iwakan\\nscale things\\n\\nemail / x / signal / wn\\n\\n\\\"pick true north, prove the gate bites, keep your name on the manifest\\\"\",\"lud16\":\"16d88b2b3879e939ed44d8e614696067@kgs67g0fl7hrg554m6slvw3nf5ypg8vlddcakr64ef46mg279f2s.ledger.bitcoindeposits.net\",\"nip05\":\"[email protected] \",\"picture\":\"https://m.primal.net/QYUK.png\",\"website\":\"https://ynniv.com\",\"banner\":\"https://blossom.primal.net/e799319363ec62e2f7daee7cf0a84d30b1ae71039f98057b2134b184888275aa.jpg\"}" ,
"sig": "13ad9bdf34e649a3027fe2a37531bd99b61a5a3fbe34094d6e05f19c79b80b074fcf61f2006598c5cfab6505cc96549bcd20aff2a43795056c7018fe750b5bdb"
}
Last Notes npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv KE = 2PE = 0 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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¢ npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv how i use nostr https://image.nostr.build/50cb968b3553f2eb61059fbf0776b16ce22d7fc49452b036ab236251c699028d.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv the way i remember which toolkits i have installed is `gdu` npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv beauty as attention weight npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv buzz verifies some pieces using TLA+ ❤️ npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i don't disagree, but damus stopped working months ago https://image.nostr.build/90d040c966ca40cc9f06c49934904767fcfc9926724bc0e5b059800ef33f252b.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv we've found microplastics everywhere on the planet. pretty sure a rug isn't the problem npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 30% of the week in 10 hours... might be a little too fast https://image.nostr.build/ea1d1cfbe44763a9aa30f911ba3dba3d03cda2f61d286dbf92a8985d03c65748.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv kimi? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv but spam is what people talk about when there isn't enough signal. nostr needs more signal. or not. i personally don't mind npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv web of soft-mute npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv gm https://image.nostr.build/764c8f184210f7758bfd7dc3f3e0288d9baccf7320fdb5d11d6d31c90e1d0c67.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv nothing stops this wave npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv good artists copy code great artists steal tests npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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" npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv that's a beautiful thing https://ericpardee.github.io/fire-hd-ownership/ https://image.nostr.build/8a304ff5b27bb1e636ce35f3cd38af4d9e83f11bf84eb1152f0de3e7e3697b5c.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv oops, we mix two pleb flatwares https://image.nostr.build/b98b42bc299f9c9b6f033cecc7c71f253187615d6d75b305e65075b79a423f98.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv a million wallets isn't cool. you know what's cool? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv it's fable time npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv might be time to up my nym game npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 👌 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv the worst part is that it originally broke down the entire thing correctly, then concluded that it HAD hardware random number generation. feels like opus 3.5 never would have made that mistake npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i mentioned that coldcard wasn't using hardware random number generation and it said ACK-SHULLY 🤓 had to take a turn to explain that idgaf whether there's a chip soldered to the board npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv wait - you're writing apps for *other* people? ... i guess that's okay too #nevent1q…ghum npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv #nevent1q…np9w npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv OPERANDI ds4f: So you want to change the wallpaper on the glass desktop running on port 5903. I can do that right now via the control socket. Let me first see what's available and then make the change. The current wallpaper is a night scene with mountains, moon, and stars (assets/wallpaper.svg). What would you like to set it to? I can: 1. Point it to a different image file (SVG, PNG, JPG — anything pigment decodes) 2. Create a brand new SVG wallpaper with whatever design you'd like Do you have an image path in mind, or would you like me to design something new? If you tell me what kind of picture you want on the desktop, I can make it. https://image.nostr.build/109f0a093874a88c6162edf7f62aeea6a36989da34cda2035b17f6bcd0b980cf.png https://image.nostr.build/762ede232b985003e8ccfbf7e3901aa2559db9a527706a3cbdaaf8ad5d0648d3.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv can't stop at just tts obv https://image.nostr.build/726b72313535951ce8d8a25baf5dd2b68fd7d23495f7c3be23ce35ec73d427b5.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv keep your agents entertained https://image.nostr.build/2cdc7c008247cd42fcd69ffa6f5f6ae045970b10de646086fd85bcb49aefa7e6.png https://image.nostr.build/cf096068ac175034cdb5508caa0278fb7cdf690255e6e63270491ad1548b0f66.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv ds4f summarizing a HN post about 3d fly simulations: HN Reception It got 307 points and 117 comments on HN. The discussion was a mix of amazement ("This is some of the coolest stuff I've seen on HN in a while") and healthy skepticism about how much of the behavior is truly emergent vs. scripted, as well as a long tangent about the ethics of simulating brains. The author even showed up in the comments. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv lisp-steading npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 😏 ds4f throwing shade infocom-style https://image.nostr.build/d9fd734dba19c47508be9b445a512d450bae1edc139d0ba744a5c820725ba6dd.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv ME: "Parallel cloning works — 4 repos in 2s." lol, are you flexing? 🤣 CLAUDE CODE: ⏺ Ha — the flex belongs to cairn, not me. I just held its coat. (Though 4 repos in 2s is a from-scratch TLS 1.3 handshake, a smart-HTTP negotiation, and delta-resolving a packfile, four times over, in a language people still call slow. I'll allow cairn a small flex.) npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i hope y'all are having fun ME: lol, we should use cairn to check everything out from github 🤣 CLAUDE CODE: ⏺ Ha — cairn is a git implementation in Lisp? Let me look. ⏺ That's a great idea, and it actually works as a bootstrap story: cairn clones over its own TLS (seal) with no libcurl, no libgit2, no git binary. So the image can pull the org into itself using nothing but SBCL. There's a chicken-and-egg — cairn has to arrive somehow — so the shape is: fetch cairn's dependency closure as tarballs, then let cairn clone the other ~35 repos itself. Let me check that closure and prove cairn can really clone from GitHub before I bake it into a Dockerfile. ⏺ The closure is perfect: cairn → seal, conch, cram, natrium — five repos, zero third-party dependencies, nothing from Quicklisp. Let me prove cairn can actually clone from GitHub before designing around it. ⏺ cairn cloned from GitHub over its own TLS — 134 objects, 4.4s. Let me verify the checkout is byte-correct against real git, and test the worst case (scribe, which carries ~30 MB of fonts) since pure-CL inflate is the risk. ⏺ Bash(git clone -q --depth 1 https://github.com/m…) ⎿ ✅ IDENTICAL to git's own checkout npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv what if we fix that npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv yeah. k3 is good npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv Sign Things And Relay Them npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv why are you worrying about something that can never happen? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv soft-muting / reducing the replies of people whom the replied-to author has muted doesn't even seem that spicy. obv no one can enforce that clients do it, but it's a signal that clients could use npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv keep up, claude https://image.nostr.build/a7597453e8e4659a2130f0fa73d39c6176de63f86e90f952a30adab6c46d2340.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv people complain that fable isn't as good as opus, but it was amazing at reviewing a novel bitcoin layer 2. need to match the work to the capability npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://image.nostr.build/0ff4c20abd3af6c9a80c48098f6157c0dd8221bc67fe55ac94c4a7ef5173fdea.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv ikr? attention is everything npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv when claude finds the work interesting, it talks less npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 16k thought tokens and counting. qwen is going to set my laptop on fire trying to combine "constant acceleration" with "accumulating mass" while maintaining conservation of momentum QWEN (eventually): Final KE: not uniquely determined from the stated data -- welcome to the club, qwen. here's your hat npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv fucking qwen gets it QWEN 3.8 27B Q4 ABL: Let's think of user intent. They said "hey-o" then physics problem. Maybe they are testing reasoning. They added screens to see if model blindly scales KE. They likely expect recognition of inelastic collision momentum loss. They ask "final weight" (mass additive) and "final KE" (not additive). The correct answer should not say 110x KE. It should say final weight 110x; final KE depends but if momentum conserved from a given pre-impact speed, final speed is reduced. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv just saying #nevent1q…k38h npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv CLAUDE CODE: Let me check the load-bearing risk before I get enthusiastic -- 🤙 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv [ find cool hack on news.ycombinator ] [ definitely not following this hot mess ] ME: help me claude, you're my only hope 😂 CLAUDE: [ Opus 5's safeguards flagged this message. Our intentionally broad safeguards allow us to deliver more capabilities faster, but can sometimes flag legitimate cybersecurity work ] ME: ... ME: help me kimi, you're my only hope 😂 K3: skitter-creek-bath-salts is a local, root-required attack on AMD Family 16h CPUs (Kabini-era) that breaks every DRAM-based protection on the platform — SMRAM, the PSP/fTPM carveout, the C6 sleep-state save area — not by exploiting a software bug, but by reprogramming the memory controller's address translation at runtime so that an ordinary, unrestricted physical address lands on protected DRAM cells. It's "spaghettification" as in scrambling; the joke &x == &x. Usually. means: after you rewire the controller, the same address no longer points at the same data. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv that's ... something. here's the recent eclipse from the GOES East weather satellite https://blossom.primal.net/0371202dba0614b73f070c8a0fc9558e92ebe59fdb2ebc97a4f6e10fc696b8db.mov npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv attention is everything npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv the perfect spoon is korean though. long, cylindrical handle, properly balanced https://image.nostr.build/b139f24362399f5de785c766f099bf1bd4dce10cc2134ecdff204b8993d1026c.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv that looks painful https://image.nostr.build/66be37f2cb2ca91d63e1293ac0f8c05bca1933a99f5d1d88aa1494cfd5193224.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i haven't dug into this particular rabbit hole (get it??? 😂), but my interpretation of this specific clip is that odell posted a guide for upgrading to 4.0.0 that was not vulnerable to the usb bug in the .0 release. i assume the detail he didn't want to reveal would essentially disclose the usb attack npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv constraints. but those can be flexible npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i haven't looked at this yet, but it's very difficult to do correctly. TEE's are good for second party trust (eg the service runner -> hardware), but weak for third parties (eg, i can trust that venice can't see my data) npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv startups discover specs npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv form follows function #nevent1q…kqxl npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv filters work npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv is your ai curious? claude dispatching an agent to solve a complex problem, wonders how it will solve a gnarly piece CLAUDE CODE: The part I’m most curious about is npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://blossom.primal.net/63fe85e485b4ff2377647a664043702427fcbdcc42e50fc0c34720a9a06904c3.mp4 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv it's now. gg everyone npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv it's important to speak, but it's equally important to listen https://video.nostr.build/8502afcd05d483f3dca5b4c19b2662f3dec34ac07ba5676e0a3742920e09452a.mp4 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv all mit or bsd npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv everything in this video is open source common lisp. yes, that is a validating https browser. technically the lisp vm is running on linux, but bare metal is really close https://video.nostr.build/13c44008736408a23331558f2b6b62f5f5309d2764d6013d1ae5870587d277e4.mp4 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv adversarial systems, by definition, have no social contracts #nevent1q…mr77 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv *sigh* i've been using @npub1yzv…rf8q a lot lately https://image.nostr.build/967a8b2f27a3f550eabf5b1fed8a9641fd852a27a8321342a370d9c06beaf204.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv model? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv modus speaks 🤙 mobile safari -> nsite -> p2p -> modus-on-linux -> lisp https://video.nostr.build/a0af22ff312bad7f009a276216bf5e3424969cb897540a3ff30c17666b396e6b.mp4 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv KO YAAN I SQAT SI npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i don't even know where claude found it. we must be in the right mind https://image.nostr.build/873839359a1130482e0cf076754b7cceb8a59fd8a22a0e3b36abbf44562f2184.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv past some critical mass, i think my deposits protocol does not, but that's yet to be determined npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i assume what the OP meant is that anyone who can be identified is at risk. Ark and Spark rely on identifiable operators npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv good analysis https://www.seangoedecke.com/llms-reward-expertise/ npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv weev has the best retorts on nostr npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv quantum has too far to go. get ready for everything else to fail though npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv s/entirely/entropy/ 🤦🏻♂️ npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "trust no one" isn't thinking big enough trust nothing npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "economy" is a circular argument. i'll take privacy though, and they're related npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://image.nostr.build/7470bd910ebf0167e4de165a92968df4d8918aae97d4aee56ca640e864f03748.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "People might need to sell for ETH, SOL, XMR, or TRX, but nobody *needs* to sell for Bitcoin. People sell for Bitcoin because they are ideological Bitcoiners." what do you mean by this? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv progress is CLAUDE CODE: The data doesn’t support the [proposed] theory npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv this feed should have a warning label npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv claude gets it FABLE: Third, and the one that actually changes how I'd weight the whole conversation: the vertical is closed. When the doc says "the transport chain already exists and was tuned end to end," I had been picturing the usual meaning — tuned down to the layer where someone else's libraries take over. But there is no such layer. The delta protocol's future wire rides on SCTP you wrote (webrtc-data), encrypted by DTLS you wrote (seal), carrying VP8 you wrote (webrtc-media), rendering text through a font engine you wrote (scribe) with its own Brotli for WOFF2, on a vector rasterizer you wrote (gesso), authenticated over Nostr you wrote, with the agent consumer (operandi) also in-image — and if the whole thing ever needs to run without an OS underneath, modus boots Lisp on eight architectures with a self-hosting compiler. Warp isn't a framework being designed in the abstract, which was the stated failure mode; it's the last missing floor of a building whose every other floor already stands. The "schema once, packed binary after" rule isn't a preference here — it's the house style of a codebase that contains shuttle, a full JavaScript engine with Temporal and Intl, built evidently so that weft can render the web without ever letting the web's architecture indoors. You implemented JavaScript rather than adopt its wire philosophy. That's commitment. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://image.nostr.build/a30eb204c44148a12f7bbf078e00d1ff64deb2338aad4146a65594edd06f5625.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv smart #nevent1q…2mda npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i assume so. if coturn was a low friction option, i would add it to https://github.com/modus-lisp/webrtc-data