ynniv

it's now

Public Key

npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh

NIP-05 Address

Profile Code

nprofile1qqs9wmfrms7myptdyzyyj330ac6ce70s7vcs5trredkzv7jtnavy37gpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyw8wumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctvntnsjm

Publishing to

nostr-pub.wellorder.net

nostr.bitcoiner.social

Author Public Key

npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdh

Show more details

Last Notes

2026-09-18 01:46:19 UTC

- reply

no os is the best os
https://modus-lisp.github.io

2026-09-17 14:47:52 UTC

- reply

it's literally called capital-ism

2026-09-17 13:12:51 UTC

- reply

yes. disappointing

2026-09-17 12:58:17 UTC

- reply

and the longer take is not slop
CLAUDE:
The principle is a real one, not paranoia. Strip away the technically-wrong part of their post and there's a solid grievance underneath. The wrong part was the mechanism: "Apple is monitoring all activity / intercepting the Tor circuit" describes man-in-the-middle surveillance, and that's not what's happening — it's a client-side classifier refusing to render a page. But the *objection* doesn't depend on the mechanism being surveillance. The objection is: to view a lawful webpage of my choosing, the device I own now demands I prove my identity to it first. That's the KYC-to-browse complaint, and it stands on its own whether the enforcement is a local filter or a remote one.
Worth being precise about why this lands harder than the old model. Per-site age gates were bad enough, but you could route around them, and the trust boundary was "this one sleazy site wants my ID." Moving it to the OS changes the character of it: the check is default-on until you present a credit card or a government ID or a face scan; you are presumed a minor — presumed guilty — until you produce papers; and because it lives below the browser, the usual sovereignty tools (Tor, a hardened browser, a VPN) don't touch it. The one layer you're supposed to fully control, your own device, is the layer doing the gating. For someone whose whole stance is "I should be the root of trust on hardware I paid for," that's the actual injury. The filter blocking Tor isn't Apple spying — it's worse in a way, because it means the escape hatch was never at the network layer to begin with.
It's also not a fringe take. The identity-honeypot problem (every one of these schemes concentrates ID data that then leaks), the chilling effect of linking real identity to browsing, and the "presumed minor by default" inversion are exactly what groups like the Open Rights Group, Big Brother Watch, and the EFF have been hammering. This person is articulating a mainstream civil-liberties objection in salty terms.
The steelman on the other side, to be fair to it: the people who designed this argue device-level is the *less* invasive option — a one-time on-device age attestation (Apple's Declared Age Range API, tokenized proof-of-age, on-device face estimation that never uploads the image) beats handing your passport to a thousand individual websites. That's a genuine argument. But note it doesn't answer this person's actual complaint, which isn't "which method leaks least" — it's "I didn't consent to being carded to read a page at all, and my own hardware is enforcing it." No amount of privacy-preserving cleverness in the *how* addresses an objection that's about the *whether*.
So the honest read: they got the technical diagnosis wrong and the political diagnosis right. Easy to be dismissive because the "Apple is intercepting Tor" line is wrong on the facts — but that'd be missing that they're reacting to something that genuinely exists.

2026-09-17 12:54:35 UTC

- reply

not monitoring, but mandating the WebKit rendering engine, and by proxy url filtering
CLAUDE:
What changed is Apple's own move. Apple unveiled new device-level age restrictions in the UK in late March 2026 — after an update, users must confirm they are 18 or older to access unrestricted features, using a credit card or ID scan. And crucially: for those underage or who haven't confirmed their age, Apple turns on Web Content Filter and Communication Safety by default. That default-on-until-you-confirm behavior is exactly what produces the screen in the screenshot — "required to restrict adult content for anyone who hasn't confirmed they are an adult" is almost verbatim the age-confirmation model.

2026-09-17 03:29:41 UTC

- reply

but the warmth emanating from your phone is virtue

2026-09-16 19:20:02 UTC

- reply

just one point on a long line

2026-09-16 12:02:44 UTC

see you in the training set 🤙

2026-09-15 11:38:35 UTC

- reply

kimi is the only model that's ever told me "if people can't do math, that's on them"

2026-09-15 03:18:16 UTC

underrated #nevent1q…pmun

2026-09-14 11:12:37 UTC

- reply

socks go up,
socks go down
🤷🏻‍♂️

2026-09-14 11:09:37 UTC

who wants
to be cool
when you can
be right

2026-09-14 00:23:55 UTC

- reply

that which is dead can never die

2026-09-13 13:45:06 UTC

i can only listen to the radio if it's broken
https://image.nostr.build/2b168be758df277d5172b1c45fba2b9ab76ef247e931d747beef3edea44273c2.png

2026-09-13 01:10:46 UTC

THIS WEEK IN MODUS — № 27
5–11 SEPTEMBER 2026
296 COMMITS · 17 OF 46 REPOS
A DVD PLAYS,
BIT-EXACT
On Saturday the workspace could decode one video codec. By Friday it could decode eight, in five containers, with four new audio codecs beside them — and every one of them is checked sample-for-sample against ffmpeg, a conformance suite, or the reference encoder’s own checksum. The decoder written on Sunday became the benchmark that drove Modus’s compiler from 3 to 60 frames a second on a Pi 5 by Thursday, after a profiler overturned the conclusion everyone had drawn about where the time went. And the browser client is now built by a JavaScript engine this project wrote.
https://modus-lisp.github.io/issues/2026-09-12/

2026-09-11 19:24:58 UTC

welcome to 2026
https://image.nostr.build/e4b0896c50c6789d7fe735e1ca34c9e82c8e7a291f521980521ccb4059a559b5.png

2026-09-11 17:10:02 UTC

do the math
don't trust, verify

2026-09-11 16:04:43 UTC

- reply

I think so, Brain, but how will we get the Spice Girls into the paella?

2026-09-11 13:06:04 UTC

- reply

GM spicy nym!

2026-09-11 12:57:49 UTC

https://m.youtube.com/watch?v=VRCKnzwr418

2026-09-11 12:33:46 UTC

https://m.youtube.com/watch?v=qdOHSjIUwWs

2026-09-11 12:30:54 UTC

- reply

pv 🤙

2026-09-11 12:28:32 UTC

I think if we say enough good mornings, maybe it'll happen.
I don't think so.
~ GM nyms ~

2026-09-11 12:20:36 UTC

https://m.youtube.com/watch?v=3kzmflORPdU

2026-09-10 15:15:02 UTC

- reply

nostr is anonymous by default

2026-09-10 10:51:28 UTC

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 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