Tootfinder

Writing up an overview of the whole @… ecosystem. I'm bound to forget something. but it's definitely time for an update to the old 2019 paper

So one of the authors is Nicholas Carlini, who works for Anthropic. This is basically an ad for the three letter agencies to use Claude. It massively over-promises compared to what the actual paper says.
But, it is important. First, this is really about silencing people. The threat of identification is designed to make people afraid to talk online. There's a massive asymmetry between the fascists and the people. The fascists are weird racists and pedophiles who are obsessed with control. No one likes them. No one likes their ideas, because their ideas are creepy and bad.
When they talk about their ideas, that people should be murdered or kidnaped based on their skin color, that there should be a national dress code, that people's sex lives should be monitored, that children should be treated like objects that are owned by the parent (specifically, one parent), that people with different skin color or uteri should be considered as livestock, people fucking hate it because it's awful. When we talk about our ideas, that everyone should be able to eat and take care of themselves, that people who can't take care of themselves should be taken care of, that we should live in a society that values life, that we should live in harmony with nature, people like those ideas. When fascists out us for talking about those ideas, people support us. When we out people who are working as fascist goons those people have to face social consequences.
Everyone hates these people. The US government is currently less popular than it has ever been. The only way they can keep power is by making everyone think that they aren't extraordinarily unpopular. The only way to do that, the way authoritarian have always done it, is to make everyone afraid to talk.
But, yes, what this paper is saying is actually kind of bad. It looks like people who don't take any precautions at all in separating identities can be identified about 30% of the time (based on the results). It's unclear how this will actually work in the real world. Larger corpses will probably have more data, making connecting things easier.
This isn't as good as a human trying to dox someone. It's not going to work as well. It may only work in a small number of cases. There will be false positives (just like there are with people doing the work). It's probably not cheaper than hiring people. But it does mean that you can just dump money into a machine that has no ethical framework and get data out. That's the point. It's hard to find humans who will do evil shit like help dictatorships target human rights activists, but if a machine can do it for twice the price then it's a better deal for the dictatorship.
For most people, you just shouldn't care. This isn't for you. As long as you keep doing what you're doing, and you can keep everyone else doing what they're doing, then there aren't enough resources to actually target you. Even if they know who you are, there are just too many people who hate them and too few goons.
For people who might actually be targeted, there are a lot of things. First, keep in mind what you're putting into anonymous accounts. Any feature that's connected to your real life is a feature that can be extracted to identify you. This has always been true, it just may be easier to find now. Your identities should be totally siloed. It's also harder to identify you if you're writing anonymously as a collective. Collectives are better anyway because they can help check your thinking. When you write as a collective, you can help clean up each other's personal details and language. A collective develops its own voice, which is distinct from individual contributors. If you do this, and you also present your work as being from one "person," then it becomes even harder for anyone (systems or individuals) to really figure it out.
I'm not going to do a full deep dive on this because I just don't have time, but your existing threat model should *already cover these threats* if you need to make sure your writing remains anonymous.
This paper doesn't present any novel methodologies. It just extracts a bunch of features, which a human would extract as notes, and tries to correlate those between identities, which is how human researchers work. Linguistic forensics were mentioned (not by name) in the paper, but the actual methodology doesn't actually seem to use them.
So a thing with less ethics can do a worse job for more money (when adjusted for the real, not investor deflated, price of tokens). It's worth knowing. It's not the end of the world, but it is a good reminder to check your threat model and make sure it's up to date.

I have not expected to be engulfed by writing of a Pope, but here we are.
It is the best and clearest corporate AI strategy doc I’ve seen, a compassionate declaration of a moral compass and one of the best AI critiques I’ve read. Transhumanism and cryptocurrencies included.
Also I wonder if it’s a start of a schism.
Start with chapter three if you’re impatient.

I spent some time #blogging today.
Oh man, why does writing take so much time?! Honestly, this time I tried dictating (Speech-to-text) and curating afterwards ... but it feels like it takes the same amount of time 🤔 Maybe it's just a lack of practice - or a lack of articulation.
Anyways - a bit of story, a peertube video and a couple of photos are waiting to be watched! 😉
…

For me this age of AI is the time we should appreciate less polished handwritten texts for their authenticity. I see this happening during selection of job applications.
https://www.theguardian.com/books/ng-interactive/2026…

How AI is changing language
As allegations of LLM use rock the literary and media worlds, linguists explain what really distinguishes human and machine writing, while novelists including Jennifer Egan and Jeanette Winterson reflect on the future of fiction in an age of ChatGPT

- Definite and distinct ecclesiastical government
This is explicitly defined in your legal documents. It's the way in which you "govern" things that are legally owned by the "church." If you're going to start a church with some people, you need to have a way of working together. The more formal you are about writing all this stuff out, the easier it will be when you *inevitably* have conflict. (Conflict is normal, so everyone should expect it.)
I also wrote something up about this. Again, it's an example (using the term "coven", because I like it more) so take it for what it's worth:
Group agreements are collectively defined rules that describe how members should interact. They may function to simplify interactions, ensure access needs are met, or to protect against the emergence of hierarchical behavior.
You can use the following prompts, or define your own:
- How should we interact with each other?
- What are your access needs?
- What would help you feel safe and respected?
- How should we deal with conflict?
- How do we deal with unanswerable questions?
- What is the process by which we update these agreements?
Write down these agreements. Edit them until you reach consensus. If it isn't possible to reach a consensus, the group may need to break apart to form separate covens.
Keep these available to refer to as they may be needed during services. These agreements will change over time. Keep them updated and be sure to check in regularly, perhaps even through a specific yearly ritual, to make sure they all still apply and no more are needed.

Things I've learned today:
- Valgrind does not support AVX512 instructions. That was an adventure because I was writing purposefully bad code at the time...
- However, changed strategies and used `clang` with the `fsanitize=address,undefined` option which seems to work perfectly fine.
#clang

Tired of writing Swift code like an animal?
Recent Swift compiler improvements cut your bathroom quality time short?
AgenticSwift to the rescue, write what your function is supposed to do, list inputs and outputs, and let your agent do the work for you.
Inspired by @… 's visionary outlook.

GitHub - migueldeicaza/AgenticSwift: Tired of having to write Swift code like an animal? Let the AI macro do the work for you.
Tired of having to write Swift code like an animal? Let the AI macro do the work for you. - migueldeicaza/AgenticSwift

I've had a lot of fun writing an interpreter for my mailbox-typed language Pat over the last month or so.
This was actually nontrivial: faithfully implementing the semantics requires us to detect that a mailbox is empty, and also *will never receive any more messages*. Perceus reference counting to the rescue!
Anyway, I thought with this merged it was time to give it a proper home, rather than a scrappy repository under my personal user:

UltraGeeking:
Using Slackware Mango to ssh into a new Gentoo install (musl, openrc, rust, cosmic, zfs if it all works out this time) and writing a install manual is a very nice way to spend this Saturday morning 🤓
#slackware #gentoo

For a tool I'm writing I need to do some web searches from time to time. Mostly from Python. What can I use without having to buy/get an API key? Anything as of today that still works?

As Autumn bears down on us from behind the heat, I think it's time to revisit some cabin-in-the-woods content. No, silly, not the Unabomber Manifesto. Thoreau *AND* the Unabomber Manifesto! You can hardly do better than Ken Kifer's annotated Walden. https://www.phred.org/~alex/kenkifer/www.k

my final dispatch on dylan & the dead’s misbegotten 1986 shows for @…'s wonderful newsletter, in which dylan finds a new way to get booed, plays (to my ears) his best set of the run, & i rediscover my fave paul williams passage (& an all-time fave piece of rock writing, really), where he champions uncritical listening & hears genius in the specific w…

Dylan & The Dead Complete Their 1986 Test-Run (by Jesse Jarnow)
Volume 4: R.F.K. Stadium, Washington DC, July 6 & 7 1986

Martha Lillard had just turned 5 when she was diagnosed with polio
and depended on an iron lung to live.
She died June 26 in Oklahoma,
the last U.S. polio patient who used the machine, her sister said. She was 78.
“They told her she wasn’t supposed to live past 20 years old,”
Lillard’s younger sister, Cindy McVey, told The Associated Press on Friday.
“She had the enthusiasm and the drive to continue living and make the best of her life.”
McVey attri…

Martha Lillard, last US polio patient using iron lung, dies at 78
Martha Lillard, the last U.S. polio patient using an iron lung, has died at 78 in Oklahoma. Her sister, Cindy McVey, attributes her death to long-haul COVID-19. Diagnosed with polio at 5, Lillard lived a remarkable life despite her challenges. She attended school using a phone system and even drove for a time. The internet helped her stay informed and meet her husband, whom she married in February. Lillard was artistic, writing poems and songs. She was also an animal rescue volunteer. McVey say…

I still think it’s a miracle that this never happened. But then…having been on the ground here, well, we knew what the stakes were. There was a kind of cold clarity during the siege that’s…hard to convey.
When they murdered Renee Good, I could almost hear their giddy anticipation: “At last! Now they’ll snap!” And after they murdered Alex Pretti and a few days had passed and •still• nobody had murdered an ICE agent…well, that was the first time I felt like the writing was on the wall for the siege to relent.
5/

I've been spending quite some time debugging fairmeeting, which seldomly forced all users to re-join a room. I found out that a plugin of prosody was writing too many messages in high volume instances. Moving those to memory fixed it. After some testing I notified the #Jitsi developer community and they integrated the fix upstream

Just did very approximate calculations; with 10g of lithium per drone*, and assuming the Russian and Ukrainian drone efforts consume 5m units a year**, that'd be ~50 tons of lithium deposited into the environment per year, mostly within, let's say, 50km of the grey zone***. It's only about $20,000 / ton****, which means $1m of metal*****.
So to answer my own silly question: no, it won't be economically viable to scalp the top few inches of topsoil and extract the lithium from it.
* Roughly right for quadcopters / small FPV; larger and longer range ones will have more, so this is a bottom bound. (OTOH longer range UAVs will tend to use ICE kerosene rather than batteries
** Changing all the time as both sides try expanding production as fast as they can manage. Ua are scaling much faster at time of writing
*** Handwaving. Contact zone's hardly moved since early 2023; OTOH Ua are pushing range limits on small battery-powered form factor, saw a 60km claim for the Logistics Lockdown operation the other day
**** There was a big spike to the $70-8000 range in 2022; median price is closer to $10k than $20k
***** (IDK the chemistry but presumably it's in an exciting range of different compounds, depending on how many bits the battery was blown into, how hot / pressured the blast wave was a few tens of mm from the boom, what other stuff was in the vicinity that the lithium would combine with, etc etc.

Writing Travel in the Twenty-First Century: Mobility and Authenticity in a Time of Crisis
https://ift.tt/8BEDhOS
updated: Thursday, April 30, 2026 - 12:53pmfull name / name of organization: Rune Graulund /…
via Input 4 RELCFP

one of my family's most recent church buddies is a tunisian immigrant who was converted to christianity by mormons then left when he realized they were mormons then got affiliated with some egyptian coptic church at some point so he got a greek bible verse tattooed on his neck cuz he thought it was coptic and also does cross motions one would do in a catholic church and also goes amen every time the pastor speaks in a way that suggests he mighta been in a black church at some point too and he's also implied he recently got released from prison and we don't know how much any of that shit has to do with the searching. my lil bro bonded with him over writing out arabic names and verses with church pens that broke in 2 seconds. love this guy i know the feeling bro

The ‘Analog Warmth’ of Vinyl Has Been Mostly Digital Since the ’80s, Says Sound Engineer | Headphonesty
I'm not giving up on a pure analog signal path, but this confirms my worst fear:
"The shift to digital processing in vinyl production began in 1979 when Ampex released their ADD-1 Digital Delay. This device, built specifically for vinyl cutting, soon became standard equipment in mastering studios across the globe."
They cite one and only one at-time-of-writing holdout; there must be more!
#theVinylFrontier #vinylrecords #analogaudio #musicianslife
https://www.headphonesty.com/2025/02/vinyl-records-gone-digital-process/

Agent libOS: A Library-OS-Inspired Runtime for Long-Running, Capability-Controlled LLM Agents
Yingqi Zhang
https://arxiv.org/abs/2606.03895 https://arxiv.org/pdf/2606.03895 https://arxiv.org/html/2606.03895
arXiv:2606.03895v1 Announce Type: new
Abstract: Large language model (LLM) agents are evolving from request-response assistants into long-running software actors: they maintain state across model calls, fork subtasks, wait for external events, request human authority, generate tools, and perform side effects that must be resumed and audited. This paper presents Agent libOS, a library-OS-inspired runtime substrate for LLM agents. Agent libOS runs above a conventional host operating system; it does not implement hardware drivers, kernel-mode isolation, or a POSIX-compatible operating system. Instead, it treats an agent as an AgentProcess: a schedulable execution subject with process identity, parent-child lineage, lifecycle state, a tool table derived from an AgentImage, typed Object Memory, explicit capabilities, human queues, checkpoints, events, and audit records. Its central design rule is tools are libc-like wrappers; runtime primitives are the authority boundary. Filesystem access, object access, sleeps, human approval, JIT tool registration, and external side effects are checked at primitive boundaries under explicit capabilities and policy.
We describe the design, threat model, Python prototype, and safety-oriented evaluation. The current prototype implements async scheduling, namespace-local Object Memory, runtime-integrated human approval, one-shot permission grants, per-process working directories, shell and image-registration primitives, Deno/TypeScript JIT tools over a libOS syscall broker, filesystem/object bridge tools, an injectable Resource Provider Substrate, deterministic demos, real-model smoke scripts, and 123 regression tests at the time of writing. Rather than improving planner accuracy, Agent libOS demonstrates a runtime substrate in which long-running LLM agents can be scheduled, authorized, resumed, and audited without treating tool dispatch as the trust boundary.
toXiv_bot_toot

🧑‍💻 - Can't help really, dunno anything about Windows.
🧑‍🎓 - But don't you write programs that run on Windows?
🧑‍💻 - Well, yeah, I help run a website which windows users can use. But I'm just writing for the web. I think maybe the testers run some Windows machines but none of the programmer staff do. Certainly not me.
🧑‍🎓 - Oh.
🧑‍💻 - I mean technically I mostly write software that runs in a just-in-time compiler environment, in a virtual container running Linux, that's hosted on another machine running Linux, that delivers a program that compiles into web assembly that runs on a virtual machine in a browser which could be on Windows, or OS X, or Android, or iOS, or even BSD or some experimental phone or something net yet invented.
🧑‍🎓 - Please shut up.