This is why we should keep the name at all costs. View quoted note →

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 @BitBlik over @FIPS 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 @TollGate + FIPS) b) the ISP does not even know what's up, because EVERYTHING IS ENCRYPTED. This tech is beautiful. View quoted note →

@fr34aky 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."