AI makes building easy, so the product isn't the moat anymore. Defensibility shifts to GTM, networks, data, and speed. Big companies can't match a founder's urgency. Bullish for early stage.

A friend raised a point today that put me back on my heels, though I suppose it should be obvious by now: “It looks like customer facing companies will have to choose their market in the US, and it has been cut in half. Gonna be tough to capture the entire US anymore.” American consumers must be approached as a bifurcated market: you see Red, or you see Blue. Two different realities.

My default position is that it's all propaganda, either way, but it delights me to see the priesthood of medicine dismantled. https://xcancel.com/HHSResponse/status/2008955963470950858

gm, good people. ☕ Have a great week.

I forked hugo2nostr and added some features I needed: • Multi-site support - manage multiple Hugo sites from one config (I publish essays and notes to different sites) • Image uploads - auto-upload to nostr.build with NIP-98 auth, cached so you don't re-upload • Preview command - see how your article will look before publishing • Shortcode processing - converts Hugo shortcodes to markdown PR submitted upstream.

GitHub

GitHub - shawnyeager/hugo2nostr: Publish Hugo blog posts to Nostr as kind:30023 long-form articles. Multi-site support, image uploads, preview command.

Publish Hugo blog posts to Nostr as kind:30023 long-form articles. Multi-site support, image uploads, preview command. - shawnyeager/hugo2nostr

Thanks to @Emre Yilmaz for the original project.

After a weekend of experiments, I can't find a single client that renders long-form in a rational way other than @primal. Happy to be proven wrong.

Does anyone have insight into how to purge ghost "reads" from @primal? My profile shows 3 reads, two of which I deleted long ago, and one was a misfire from today.

There's no place like home.

NIP-46 wins this round. I am humbled.

gm, good people. ☕

Reminiscing about the abusive ex from your 20s and the good times you had, despite it all. Reminiscing about X. Same energy.

Working on hugostr — a CLI tool that publishes Hugo blog posts to nostr as kind:30023 events. It uses NIP-46 (remote signing) so users can sign events with their phone (Amber, Primal, et al). The flow and where I'm stuck 1. User runs hugostr publish content/post.md 2. CLI displays a QR code with nostrconnect:// URI 3. User scans with Amber, approves the connection 4. CLI shows "Connected!" ✅ 5. CLI shows "Requesting signature..." then hangs forever ❌ 6. Amber never shows a signing prompt Technical details - Using nostr-tools library (v2.19.4) with BunkerSigner - Relay: wss://relay.nsec.app - The initial NIP-46 handshake completes successfully - When calling bunkerSigner.signEvent(), it should: 1. Publish a kind:24133 event with encrypted sign_event request 2. Amber receives it, prompts user, sends back signed event 3. But step 2 never happens - Amber doesn't see the request What I've tried 1. nostr-tools BunkerSigner - connection works, signing hangs 2. NDK's NDKNip46Signer - same issue 3. Checked relay connectivity - pool.publish() works in isolation 4. Added reconnection logic after connection - no change Suspected causes 1. Pool/WebSocket connection state gets corrupted after the initial handshake 2. Subscription filter issue (Amber uses since = now()) 3. Something specific to how nostr-tools manages the post-connection subscription What would help - Anyone who has successfully used NIP-46 client-initiated flow (nostrconnect://) from Node.js with Amber - A working reference implementation to compare against - Insight into common NIP-46 pitfalls Halp? #asknostr

#tunestr

gm, good people. ☕

Worthwhile long read.

The AI revolution is here. Will the economy survive the transition?

The man who predicted the 2008 crash, Anthropic’s co-founder, and a leading AI podcaster jump into a Google doc to debate the future of AI—and,...