I have some gold for you today. .clipping is one of the most interesting rap projects that I know of. The interplay between "rhyme-rhythm", "accent-rhytm", "musical-note-rhythm" is simply impeccable. The timbres used in their beats are unorthodox in the best way possible. The drum machine built from garbage is just a bonus. #musicstr #music #tunestr #rap #hiphop

@Gigi are you aware of any tools for kind 1111 discussions tied to highlights (or better: tied to any kind)? Highlight feeds in Boris are quickly becoming more interesting than my kind 1 feed and it would be great to be able to get some conversations going.

Testing custom emojis on @Nostrich :Kneading: :Pawraisewhilesitting: :Pawraised: :Kneading: :Tailaroundlegs: :Tailquiver:

Reading Pillars of Propagation again. This will become a classic. View article →

My @npub1k3g0...stj3 over @npub1y0gj...00ly has been running for a couple of days (now at https://npub1ekuzl82ewlx7s9xdz9uq6lmadt9slv8n9m47z5fxkp7k57vpfvysuhxzvu.fips:8080/) and it seems like it's working really well. The speed is not exactly what I would call blazingly fast, but it's still magical that you can run a web service with no permission from a domain registrar or a hosting provider. Well, you still need an ISP, but a) it's only a matter of time, as FIPS is transport agnostic (imagine @npub1zzt0...ljrv + FIPS) b) the ISP does not even know what's up, because EVERYTHING IS ENCRYPTED. This tech is beautiful. View quoted note →

@npub1yptp...a52w Some feedback on fips2go: when bootstrapping on a cellular network, I'm getting errors like '2026-09-23T13:41:28.632354Z WARN fips::node::lifecycle: Failed to send handshake message link_id=link:2 error=send failed: Address family not supported by protocol (os error 97)'. My clanker says this: "On a DNS64/NAT64 mobile network (IPv6-only carrier), every handshake send fails with `os error 97` (EAFNOSUPPORT) and the node ends up with 0 links. On any normal IPv4/DNS network the same config links fine. Root cause looks like an address-family mismatch: the UDP transport is bound to `0.0.0.0:37259` (AF_INET) but the peer endpoint is a hostname (`$name.fips.network:2121`), which DNS64 resolves to a synthesized AAAA. The resulting `SocketAddr` is AF_INET6 and `sendto()` on the AF_INET socket fails. `udp_bind` is in `ConfigStore.RETIRED_KEYS`, so the bind family can't be changed from the UI."

Decentralized commerce needs decentralized infrastructure. A time will come when Bitcoiners will be forced to build in places that are harder to reach for the state apparatus, away from censorship, ID checks and takedown notices. A central piece in all of that transitioning away from traditional internet domains that can be shut down easily. Luckily, achieving this has never been easier and it will take years before the machine catches up with us. As a little demo, you can check out a @npub1k3g0...stj3 instance served over @npub1y0gj...00ly from my personal PC: https://npub1d97zuys7eg0ehdsnrf8t3cs2xy0xfvrj4ukrx64hdrrda6r76nfsc0n7qr.fips:8080/ No domains, no static ip, no rented hosting, just a goddamn computer standing under my desk. To reach it, ask your clanker how to set up FIPS (from this repo: https://github.com/jmcorgan/fips) service and .fips name resolution on your machine. After it is done, you can just use your standard internet browser. And if you wanna reach it from an Android phone, just grab fips2go (

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

from Zapstore, add your internet browser to the list of FIPS-enabled apps and voila! Expect intermittent availability, from time to time I step away from the computer and shut it down :)

Are there any high-quality curated lists of nostr clients grouped by NIPs they implement?

The future is meshed. View article →