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-29T09:14:01Z 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 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i couldn't find an anonymous TURN server (paid or otherwise), so i'm running my own coturn to connect phone to agent over webrtc. it's essentially a nostr relay with higher bandwidth and low latency npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv tired: proprietary apps wired: webrtc expired: keyboards npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv STUN/TURN? npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv if the spooks are derailing you, you're doing something right? still, a long way to go npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv modus is common lisp. -- Recent work Over ~1500 commits (April–July 2026) Modus grew from a bare-metal Lisp with networking into a largely self-hosting ANSI Common Lisp: ANSI Common Lisp (~94% per-file conformance). Full condition system (handler-case/bind, restarts, signal/warn/cerror), CLOS with standard method combination and call-next-method, the reader and printer with format (50+ directives), pathnames and file I/O, a numeric tower (bignums, ratios, single/double floats, complex), and ~400 standard functions. One evaluator (WS3). Production eval and load compile each form to MVM bytecode and run it — the self-hosted MVM compiler runs inside the image, and the original tree-walking interpreter has been deleted. The vendored ASDF driver evaluates end-to-end on this path. Runtime JIT (WS4). MVM bytecode is translated to native code at runtime (executable memory + call relocation) behind the same evaluator seam. Full self-reproduction (WS5). A Modus binary compiles its own source to a native ELF and reproduces itself (modus → modus2 → modus3) with SBCL out of the loop. GC hardening. Conservative-root validation via an object-start bitmap, a heap guard band, zero-initialized allocation, and optional Bartlett page-pinning — closing a class of heap-corruption crashes. SBCL drop-in compatibility (in progress). Unmodified pure-Common-Lisp libraries load and run from source — e.g. natrium (SHA-256 FIPS-exact) and alexandria — with the bordeaux-threads dependency tree loading unmodified. New platforms and features. Bare-metal ThinkPad T420 (E1000 SSH, EHCI USB, VGA + PS/2 console), UEFI x86-64, ARM32, byte-packed (unsigned-byte 8) arrays, and a hosted modus CLI with SBCL-faithful flags. npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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! npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv it's git pushing day npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv when you're banging rocks together after the fall, you'll want to view pdf's of how to do it correctly. you're welcome https://github.com/modus-lisp/folio npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "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." npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv CLAUDE CODE: Merged: main fast-forwarded from 9208409 → d372f28 (+1,071 commits — the full WS3/WS4/WS5 lineage, ending at the gated, bit-exact self-hosting fixpoint). npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv all you need are verifiable goals – everything else is efficiency. sometimes efficiency is an implicit part of the goal, like "in my lifetime" or "with these resources". sometimes it's not, or it's trivially low, like "show up on time". intelligence increases efficiency by orders of magnitude. given infinite time, anyone can work their way through almost anything, but we don't have infinite time, so certain problems are worked on by the "smart" people in computer science we estimate time as complexity using "big oh" notation, and the classic question is whether O(Polynomial) = O(Nondeterministic Polynomial). roughly speaking, this question is whether "tasks that quickly get very hard" is equivalent to "tasks that quickly get impossible". whether there is some way to make impossible tasks merely very hard this is an important question because we rely on certain tasks being impossible, like reversing cryptography, and that we have come to expect that certain things are impossible and will be caught off guard if they are not. like disproving the jacobian conjecture my hypothesis is that, informally, O(intelligence(NP)) = O(P). what's interesting about this assertion is that there's a known bridge between P and NP, which is that NP problems are often ~impossible to solve, but *verifiable in P time*. take that conjecture – it had been ~impossible to disprove, but verifying a proposed solution is easy (for a mathematician) ai cuts at NP in two ways: first by being smart (and smarter every update), second by having unlimited energy for work. ai doesn't sleep, or need sabbaticals. ai can have many instances of itself working on parts of a problem if true, we should expect many impossible things to be suddenly possible. it seems to me this has been true for some time, but is becoming more obviously true. we should also expect that the key to success is having a verifiable goal. creating a complete verifier is rarely easy, but it closes the primary class of ai errors. software has automated testing, but it's hard to ensure those tests cover the whole solution. poor verification is why people dismiss "vibe coding". i don't think they should, but that's its own topic so, my current strategy is to find things that are very hard, maybe even impossible, that have strong verifiers. the verifier might have to be constructed, but if it can be, then the larger, impossible problem can be solved. if not today, maybe in three months. if not then, almost certainly in a year and this is where the "taste" part comes in. it's up to us to pick which impossible problems we're going to work on. ai can never replace this, because ai doesn't share your taste. you could then say that all you need is taste, but i've said that before and no one paid attention because they didn't know you also need a verifiable goal npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "21 million" is, at its core, just ngu. tired npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv thank you kajoozie. and a fine GYF you you as well! npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i miss nostr's GFY energy npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv sad but true. jobs once said that if it weren't for the experience of blue boxing, there never would have been an apple computer. not sure how to keep that flame alive. my kid has been fuzzing screen time though npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv jobs said that they sold quite a few, actually. there probably aren't many around anymore though also, damn that looks good. most blue boxes were hand wraps with cheap momentary switches npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://m.youtube.com/watch?v=S0VihLYBcVU npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv unilateral exit is a mistake npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv claude's there https://blossom.primal.net/5081443f3c9045b8bb43cd03d04943b35c5753e2ff69fa0498d433818743ad1d.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i don't think it is. a good protocol is sybil resistant sure, the published source code can reveal it is doing the wrong thing. but you don't know what a relay is actually running, who is running it, who pwned it, or who captures bytes on the wire npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "If you haven’t got your health, then you haven’t got anything." npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv yes, but how would you ever know? compliance is discretionary npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i'm totally ignorant of nip 59, but: "nip 59 says relays SHOULD only serve kind 1059 to the marked recipient" establishes trusted relays. trust is a mistake that gets you burned npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "For in six days the LORD made heaven and earth… and on the seventh day he had no more tokens" - probably npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv gracias, españa npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv hopefully able to run on an rpi soon, source-verifiable down to the bootloader npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv amusingly, that was 21 days ago #nevent1q…un84 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv got some zhuangzi / epicurus there npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://blossom.primal.net/10ee1ac7fea40de403ed795edc718508f5498b8a02a1cfe060da340ad48d29e3.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv "it is basically international fascism in a can" i ❤️ nostr #nevent1q…53cj npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv ask not what the singularity can do for you ... npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv everyone's doing it, so why am i? modus is still different. the goal isn't "vibecode an operating system", but to create an operating system that's easier to defend than attack the fabric of cybersecurity is complexity. simpler systems are easier to defend because complexity creates opportunities. people often joke that emacs is an operating system, and that tells you something about the power of writing things in lisp modus also acknowledges the issue of "trusting trust", ken thompson's classic demonstration that source code isn't enough when you have to use a compiler that can itself be compromised. modus is architected to enable wheeler's diverse double-compiling: multiple existing compilers (sbcl, ccl, ecl) can be used, on multiple cpu architectures, to compile modus, and those modus binaries (gen1) can be used to create a final modus binary (gen2) correctly executed, all similarly configured gen2 binaries will have the same exact bytes. what this means is that to taint the modus binary, an attacker would need to compromise every compiler, on every architecture, that was used in the chain. and, they would have to target a system (modus) that didn't exist yet modus is multi architecture for the same reason: once you have established that one device is trusted, how do you trust a second one? you compile an operating system that runs on it, using the device that you already trust. if one is intel and the other arm you have a problem, unless the system running on one can produce an image for the other i am a defender. almost all of the time that sucks, because it's far easier to break systems than to defend them. but now we have this ai thing, and it dramatically increases your productivity. it lets you do things that you would never have the time or money to do on your own. all you need is taste so i'm building a system. i call it an operating system, but when that includes a bitcoin node, a web browser, ssh client and server, vnc server, etc, it's clearly more than "an os". and the philosophy of this system is security. "processes" are code running in message-passing actor isolation like qubes. the browser prefers page loads happen in their own data space unless you tie them together, like incognito and firefox's containers and it's bare metal, as much as it can be. it runs on an rpi zero 2 w, which requires some blobs. it's possible to use your own open source boot loader (existing). eventually i want to replace the broadcom wifi blob, but for now i run it without wifi. risc-v hardware would make this unnecessary so that's modus. fable remarked that "Pre-2024 this scope was insane for a small team. With agents it's merely audacious, and the thesis is self-demonstrating: the stack exists because the method works.". i call it lifeboats for the singularity nevent1qvzqqqqqqypzq4mdy0wrmvs9d5sgsj2x9lhrtr8e7renzz3vv09kcfn6fw04sj8eqyt8wumn8ghj7un9d3shjtnedehxja3wvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgqvyjkrsj8mj0urnpuc5kw96296xqj922qzwskgunzgxzqhrwlftuw66ezt npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv yes 🔥 #nevent1q…zr6p npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv yes. all code is now legible – obfuscation is dead https://blossom.primal.net/8aea381a014faa033617fc785dfab350430f3ed03a2aad963a29bbb60e54abf5.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv nevent1qqsvjynz87hsf43pacugh70zfw482clgpcc5zl8l5pl6c86awyhyh0s3y3u6f npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv everyone's doing it, man – when are *you* writing your own operating system? join the movement! https://primal.net/e/nevent1qqsgcal4umml8vs7utc3ayk5cq3dh9lgpu8tq4237j9glxhpf0trwrc94ckmu npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv it's happening https://blossom.primal.net/7a2b17ae490002a12138ed962cc9d99b5ef61b54c67d422bf30dd069492fa1aa.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv habitat of the modern elite developer https://image.nostr.build/df3c622da68481ad636b5daf2ac756002b3f58adbc528eb62a0e8621c16ac147.jpg npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 🌳 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv of course, you could still ssh to a linux host ... using the ssh client that claude built npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv this only works because the stack is running on linux/sbcl. when we move to bare metal lisp it won't be able to run linux binaries, because it isn't linux npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 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 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv 🤙 vibe the change npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv mouseover/hover works, on a browser that claude wrote, with css that claude wrote, and a javascript engine ... that claude wrote 😂 npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv i'm just opening apps that don't have close boxes and dragging windows that don't focus around and browsing poorly rendered websites at 2 fps BECAUSE I CAN this is ridiculous 🤣 claude wrote a lisp desktop and the scroll wheel works 🔥 https://blossom.primal.net/37652d6690fde7159c7f4837adb5d626673caefcdd596eb2bfd4055ea2180fdd.png npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh ynniv https://image.nostr.build/44aa58c90d90624c01ab5cb96fa02b342f782849241ac75802216361b970d760.jpg