nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycs558km "nak publish" should work if you install it from this commit:

go install github.com/fiatjaf/nak@67e291e80dace3dd8c10252b4a3c8b4363afc894

Reply to this note

Please Login to reply.

Discussion

Then you can do stuff like

echo "#surely you're joking, mr npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft olas.app is broken again" | nak publish

It will add the hashtag, turn the npub1 code into a nostr:npub1 URI, turn the olas.app string into https://olas.app, add the "p" tag (and "q" tags too if you were mentioning an nevent1 code or naddr1 code) and finally publish it to your "write" relays and to any mentioned person (or author of mentioned events)'s "read" relays. There is also a --reply flag that you can pass an nevent, naddr or hex id to and it will do the right thing (including setting the correct kind to either 1 or 1111). And there is a --confirm flag that gives you a chance to confirm before actually publishing the result to relays.

Well, Coracle has broken my example non-URLs and non-Nostr URIs by changing them to rich text at read-time. nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3jamnwvaz7tmgvfezucm0wfskxmr99eek7cmfv9kz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cez9u7pju please fix.

Use backticks

You're evil.

I don't see the problem?

Oh, now I do. But I stand by my parser

nak is nostr debug tool ✋😑

nak is nostr super app ☝️🤓

Awesome stuff, thanks

👀