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.

scheduled post

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.

https://gitea.coracle.social/coracle/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.

https://github.com/nostr-protocol/nips/pull/2537

Please tag wallet providers so they can implement this and improve wallet security.

@Rizful.com @Alby

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