How do I discover your BOLT12 from a human-readable/memorable name now? Is there a spec for that? Should we add a simple entry to Webfinger perhaps?

Good to know, thanks. Would it be enough to have it in a namespace on one of the two?

The docs are here: https://jsr.io/docs/publishing-packages

I would try one of the manual options first, but it's also easy to do from a GitHub Action later: https://jsr.io/docs/publishing-packages#publishing-from-github-actions

Nice!

Would love to see it on JSR, since it's all TypeScript anyway.

I'll never understand how someone can walk around without cash and trust their card, or even worse their phone, to always work. But the same goes for businesses not accepting cash, of course.

Not sure if I did this right, but I'm accepting issues and PRs for the Nostr Links extension via Nostr now:

https://gitworkshop.dev/raucao@kosmos.org/nostr-links/prs

Original repo here:

https://gitea.kosmos.org/raucao/nostr-links

Just a note on CI solutions:

For https://gitea.kosmos.org we use Gitea Actions, which is compatible with GitHub Actions, like you describe.

https://docs.gitea.com/next/usage/actions/overview

It works nicely, and the configuration allows to configure both hosted and external runners per repo, user, or org. (Meaning you don't have to allow just any user to run arbitrary payloads on your infra, but you can allow only trusted or paying users to do it.)

Being compatible with GitHub Actions brings baggage, but also convenience and less migration work, of course.

Sorry, you didn't. The type should be `application/nostr+json`, not `application/json+nostr`, as per https://datatracker.ietf.org/doc/html/rfc6838#section-4.2

Nice!

The HTML is currently missing link rel elements for feed discovery. Something like this:

``

Incidentally, I also just proposed adding alternate Nostr links to Web content with Nostr representations, as well as to feeds, and some people seem to like it, so you could also add those:

nostr:nevent1qvzqqqqqqypzq8meqkx80g3yuklzymy0qfx2ekk56aqc2ht4ak03z3em4r4cdcwtqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqyzc7r4lzx43w2ajv0ajy9l2gpqysagu84mscydt03t5sm6vdlh206hpt4hq

(For RSS, the elements need to be namespaced, for example `

Hmm. In my implementation, I just do a single query to fetch articles for an npub, and then order them by `published_at`. It's very simple and works pretty well.

I was actually wondering why you don't just configure an npub and maybe a tag for filtering if necesaary.

That depends on the implementation of discovery mechanisms. My extension would probably miss injected elements after page load at the moment.

The argument parsing with the commas was only broken in tmux for me, but works fine with the latest nak now. I have no idea why or how that would happen.

I'm also using front matter for publishing NIP-23 content. If someone else implements that in a proper tool, maybe we can use the same keys:

https://nostr.kosmos.org/@raucao/2025-04-24-markdown-to-nostr

Not yet. I'm not sure it even warrants a NIP, since it's basically just using the HTML spec as intended. But maybe there should be one.

I also just added the link rel elements to my Atom feed. So if you have a feed reader with both RSS/Atom and Nostr support, and someone adds a URL for the former to your reader, it could now detect the Nostr alternative and offer the user to subscribe to that instead.

Also interesting if some of the feeds you're already subscribed to (maybe for much longer than Nostr even existed) started adding alternate Nostr links in the future, so we could slowly migrate to a more decentralized system.

Maybe something for noflux, nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6?

nostr:nevent1qvzqqqqqqypzq8meqkx80g3yuklzymy0qfx2ekk56aqc2ht4ak03z3em4r4cdcwtqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqyp6mc5gd2lqqkadluhrzgu0rv36gt0x0vfqx0lrtsx045egek3egxv2dqcs

Will merchants continue to pay between 3 and 9% fees to the debit card oligopoly with that?

Turns out that nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 fixed the issue with the commas a while ago. So if you just use the latest version of nak with this, then all is good. 🥳

nostr:nevent1qvzqqqqqqypzq8meqkx80g3yuklzymy0qfx2ekk56aqc2ht4ak03z3em4r4cdcwtqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqyz6thvhv52t96kvevssj2adqel9h45szyhw7cejzed4g88qfrnv8u9s57qv

Oh, also, you can even add them to RSS and Atom feeds, like so: https://nostr.kosmos.org/@raucao/articles.atom

For RSS, the elements need to be namespaced. I would use `

Nice!

May I ask you have a look at https://nostr.kosmos.org/@raucao/link-rel-nostr and consider adding the link element to your generated HTML?