LLMs have no salience, so if there's some oblique concern in the work you're doing that is important to you, they won't catch it — and you won't either if you delegate the work.
hodlbod
hodlbod@coracle.social
npub1jlrs...ynqn
Christian Bitcoiner and developer of Coracle and Flotilla. Learn more at flotilla.social.
there's nothing nostr loves more than arguing over how to pronounce "nostr". We're so back?
my kids trapped a squirrel in the backyard and now they want to eat it
in bed but staying up
running and climbing
crack me open, there's more of me inside
shoot me with your breath
what am I?
Vibing typescript support into
so I can maybe write beautiful code again sometimes
GitHub
GitHub - squint-cljs/squint: Light-weight ClojureScript dialect
Light-weight ClojureScript dialect. Contribute to squint-cljs/squint development by creating an account on GitHub.
Nothing makes me feel more like a meat proxy more than when my clanker finished 3 hours of work and I respond by misspelling "commit"
Re-wrote caravel from rust into haskell today just for curiousity's sake. Line count dropped by 30% which is cool.
Flotilla 1.15.0 is out, along with a new version of caravel that brings everything zooid used to do into a single monolithic binary. This makes hosting community-oriented relays much easier — there's now only one service to manage, and it's all written in rust.
Changes:
* Redesign threads with a board view, search, and related threads
* Suggest existing answers while composing a thread
* Schedule posts for later
* Show a note's stats, with a histogram of interactions
* Manage members and invites from one dialog
* Jump from a search result to the exact message
* Store events in an on-device database instead of loading a cache into memory
* Read an article from outside your spaces on a page of its own
* Upload space and room images to the space's media server
* Log in to a space without waiting on relay authentication
* Fix replies counted twice, threads scrolling themselves to the bottom, and feeds leaving gaps in cached history
Coming soon: a better thread layout, related threads, and thread search. Here's how Squalk looks on the next version of Flotilla.


Are there any relay implementations that accept events with created_at in the future and hold them until they're in the past? Bonus points for serving them to the event's author so users can see a queue of scheduled notes.
Just put together a small project for helping heal the nostr network. This is a follow up to my `canoe` project, which is a personal relay that actively replicates events across your inbox/outbox relays.
Snorkel is a daemon that crawls the network, replicating a random pubkey's events between their outbox/inbox relays every few seconds. It's less reliable, because a lot of relays block unauthenticated users (like nostr.land), but it should really help with deliverability and lost notes.
It's intended to run in the background with reasonably low resource usages, syncing ~100k profiles per day. If you want to run one, it's a good way to contribute to healing the network for people with poor relay selections, or who haven't migrated their events.

Coracle Git
snorkel
snorkel
Just opened a PR to NIP 47 which allows apps to invalidate NWC URLs. Useful for cleaning things up on logout, or in case of leaked connection URLs.
Please tag wallet providers so they can implement this and improve wallet security.
@Rizful.com @Alby
GitHub
Add logout to nip 47 by staab · Pull Request #2537 · nostr-protocol/nips
NWC connection URLs are useful not only to connect clients, but also to implement subscriptions. In the case of a leak though, it's very bad fo...
Post Mortem:
The server I run Flotilla, zooid, and other things on got hacked this morning at about 5 AM Pacific. I had disabled the gitea action runner for pull requests, but not for users' own repositories. The attacker triggered two workflow runs (called "exploit" and "probe") in an action runner container which had the docker socket mounted.
At about 8 AM this morning I purged the attacker's two accounts (which was a mistake because it destroyed forensics), and gave Claude ssh access and asked it to clean things up. Gitea has been moved to a dedicated host with the action runner container configuration fixed and registrations disabled. The rest of the services have been manually moved to a fresh host.
There's no evidence that the attacker exfiltrated any sensitive data, installed any software, or executed any supply chain attacks (no packages were published, no updates released, and I keep signing keys elsewhere). This appears to have been an automated attack targeting poorly-secured gitea instances.
I'm treating the server as completely compromised, and have rotated all credentials and moved everything to new servers.
The main things for you to know:
- If you host a relay with me, it's possible the attacker had access to your space's chat messages.
- Hosted relays' secret keys were compromised. These were never shared with tenants, have been rotated, and never published any metadata. They were only used to map self-published events to a relay url.
This attack has made me reflect on the security characteristics of two things in particular:
- Nostr private keys can't be rotated. I stored low-value keys on disk rather than remotely, let alone using multisig. This is a very different threat model than people are used to. I am going to look into a developer-oriented way to store private keys for production use.
- NWC connection strings can't revoke themselves. One of my users had entered their connection string into caravel to enable automatic payments. I've contacted them and encouraged them to revoke the connection, but it's not something I can do myself. I am going to look into adding a self-revoke protocol to NWC (and NIP 46).
@Alex Gleason armada's relay is prohibiting PoW on gift wraps:


running feather
Possible unintended consequences of a panopticon crony capitalism machine brain: the unleashing of tens of thousands of individuals who need to become entrepreneurs in order to survive
View quoted note →
Announcing Dipity!
TL;DR, it's a bluetooth mesh chat app built for local communities, not protests. You can get it on zapstore, google play, and soon the apple store (Lord willing).
Last summer, I was sitting at a coffee shop chatting with a friend about creating a bluetooth mesh app, inspired by Manyverse (a scuttlebutt app). The local-first architecture is what originally got me interested in this whole space, and yet I'd never tried building on it.
Less than a week later, Bitchat came out, which took the wind out of my sails.
Since then, Bitchat has seen meteoric growth, topping app store charts and making international headlines. Which is great! But I also have a few problems with it.
First, its primary metaphor is chat, which might be useful for some cases (like protests), but is near worthless for slower-paced async communication — think concert announcements, garage sales, lost and found, etc.
Second, it's vanilla nostr — messages are signed, and geohash rooms are accessible from anywhere. There are no real barriers to communication across space.
James Carey (no, not that one) talks in his book "Communication as Culture" about time-binding vs space-binding media. Time-binding media create continuity over time, while space-binding media create continuity over space. The trade-off of each is discontinuity over the other axis. We see this is the rise of "horizontal" identities (race, class, gender) over "vertical" identities (nationality, regionalism, home town pride) in tandem with the rise of space-binding media like the internet.
I want to see if I can fight the inherent tendencies of digital media to accelerate communication and erode local identities by using it in a new way.
Dipity is anti-efficient; it uses bluetooth and nostr with a new signature scheme to promote verifiability across only two hops. (In theory, this could be short circuited by placing a relay in between, or by passing along proofs, but assuming buy-in from users, the network can suppress illicit gossip.)
The goal of this is to create a local-only, human-scale gossip network that supports the formation of organic, rooted communities.
I don't know if this project will work, but I think it's interesting and worth a try.
Until the iOS version is out, I don't recommend trying to onboard your local community, since network effect is key (unless your locale uses Android exclusively). But please give it a try and let me know what you think!
Dipity for Android — Zapstore
A community board that trades posts with phones nearby over Bluetooth, built on nostr.
I'm getting more done than ever, but pride in my work is at an all-time low. The average quality of the work I do has improved dramatically over the last 6 months. Many of the engineering disciplines I neglected or never learned happen automatically now.
It used to be I would sweat to make something I was proud of, because I believed it was worthwhile to do so. The bad parts were bad, and many, but eclipsed by the purposefulness of the work that drove me to do it. And the good parts were good, because they were real — because I cared enough to discover them.
I'm not espousing the labor theory of value. I'm not talking about some essential, ineffable "good" in craftsmanship. What I'm saying is that sweat is an essential ingredient in producing something with a soul: something that people can love. People don't love commodities, they love singular things. The commodification of software is killing the love of it.
In other words: other people loved the garbage I used to craft more than the garbage I now produce.
Nowadays, all the parts of my work that used to be low quality are high quality, because Claude is a better programmer than I am. But the parts of my work that used to be good haven't survived. I might be trying to do something worthwhile, but because I haven't actually engaged with the problem I can't make anything better than slop materialize. The glory has departed.
Flotilla has greatly profited from me using AI to code, because the good parts only I could build were already there, and there was a lot of bad stuff that needed to be fixed.
But the way I feel about other projects that I haven't gone through that journey with is that they are garbage. Total trash. They are as valuable as the tokens I used to generate them. Because there's nothing really there. There is nothing to love. There is nothing singular. They are disposable, fungible.
When people refer to themselves as "idea guys" it means they suck at doing real work. But their ideas can only exist if someone takes the time to make their ideas a reality. But in the New Age of AI, idea guys can finally realize their genius, without being held back by a bunch of narrow-minded technicians!
But I think it will turn out that there wasn't actually any genius there in the first place, and everything that was of value about the original idea was actually discovered during the process of building it by the people who did the work to make it a reality.
Software as an art, or a craft — as a thing which is an object affection — is dying. This is fine, the affection was probably misplaced in the first place. A new kind of software — the stuff we create for ourselves, that no one else will ever see — will probably absorb some of that affection. The rest will be commodified.
I think this goes for every industry, by the way. An accountant can feel proud of his spreadsheet, a plumber of his solder, a salesperson of his pitch, even a developer of his agent harness. He can love the work of his hands and have affection for it. It can be singularly valuable to someone, and a conduit of love between the people concerned.
Does an assembly line worker feel affection for the parts he stamps out, or the people who receive them? Is oil extracted with heart? Are the foundations of skyscrapers filled in with love? Does the dollar store worker bask in the sunshiny faces of the children purchasing their very own extruded plastic disposable pseudo toys?
Maybe they do. I do think that wherever humans use tools, there will be affection. It reminds me of the nose art pilots used to paint on their bombers. "This is my rifle. There are many like it, but this one is mine."
Maybe means I should buy a mechanical keyboard, I don't know. DAU and MRR probably engender warm fuzzies in some types of people, but I'm not one of them.
Commodities are not necessary for a good life. A community can live without commodities, and survive. If everything were hand-made, pride and affection would ubiquitous - and its absence would be traceable to a character flaw in the worker. If every meal came from an animal who had a name instead of a number, every meal would embody gratitude and grief like no store-bought meal could.
I yearn to live that life and check out of this Terry Gilliam-esque Hotel California life, I say as I glance out the side of my eyes at the people I know who have just bought a couple dairy cows and moved out to some acreage, and keep typing.
Am I a coward for wanting to stay where it's comfortable and secure? Where my skills (or what's left of them) are in demand? Is my heart too bound up with the bounty of the market that I have become a commodity myself?
Or am I a whiner for being so sad about losing the drudgery of programming? For not wanting to live on a diet of petrochemical-derived macro-nutrients? For not wanting to spend hours a week in a car driving to an office where I work by myself?
"Better a handful with quietness Than both hands full, together with toil and grasping for the wind."
Fresh off the presses: I wrote a new personal relay implementation that will fix nostr.
Instead of syncing notes from your web of trust (expensive, no one is looking for them there) or blasting notes to the network (pointless, borderline abusive), it looks for your outbox relays and fetches your notes from them. This means that after years of home relay fragmentation you can finally get all your notes in one place. Even better, if you run two instances they will actively copy your notes between them without any configuration other than a normal 10002.
Use the outbox model. It works.

Coracle Git
canoe
A personal relay that supports the outbox model and automatically syncs with your other relays.
I messed up the joke by forgetting to post the picture
View quoted note →
View quoted note →