Here's the bash script I created for publishing NIP-23 content. Maybe it's useful to someone else:

nostr:naddr1qvzqqqr4gupzq8meqkx80g3yuklzymy0qfx2ekk56aqc2ht4ak03z3em4r4cdcwtqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqrserqv3495crgtfjxskk6ctjddjx7amw946x7ttwdaehgusuhsm2s

I'm only aware of a single issue right now, which is that nak doesn't seem to like commas in tag content. Other than that, it works just fine for me.

By the way, if you have a personal home page or profile page, you can also add your npub to it this way. The link can be to any Nostr address/ID.

Standardizing it in a NIP is good, but doesn't help with people using it wrong.

It's funny (and sad) that both of the issues in the original post there just stem from using Markdown wrong, and have nothing to do with Nostr or interop. Newlines without double spaces mean nothing in Markdown (for good reason, so you can format your source document better), and the image syntax is just plain wrong.

Clients should obviously at least implement Markdown rendering according to the Markdown spec, if they're not using a library that does it for them.

This is a small thing, and the demo case is kind of silly (because there's an open-with-nostr button under the articles it's currently working for). Nevertheless, if you publish articles on the Web as well as on Nostr, would you consider adding this HTML element to your pages?

https://nostr.kosmos.org/@raucao/link-rel-nostr

Also, if you're working a Nostr client that renders previews for linked content of any kind, you might want to parse that element and adapt your UI for Web pages that tell you about Nostr versions of their content.

Also please do let me know if you think I'm doing things wrong, or if you have any other kind of feedback. Thanks!

Yes, I'm not overly happy with that either. I wrote my own article rendering for public HTML pages on our relay and there were quite a few edge cases from inconsistent usage to work out, too. Some clients repeat the title in the content for example. Lots of small issues like that. :/

OK, so Habla lost a draft of mine (and its whole relay page/loading is broken for me now) and I wasn't able to load it in any other client for long-form content either. The NIP-23 ecosystem in general is just rather messy and buggy.

So I ended up creating bash scripts to export all my drafts to Markdown files, with meta data in frontmatter format, as well as publishing updates from those Markdown files via nak.

(I hope the Deno folks release Fresh 2.0 soon, because I'm waiting to port Substr to it and actually add a decent, non-buggy publishing UI.)

(I mean zap wallets *and Nostr clients*.)

Wallets that support zaps should offer notification settings for threshold amounts, as well as zaps without a message for example. It's a very simple feature to implement.

Here's an example from Kosmos account settings:

It's almost as if their DIDs aren't actually D.

Not really relevant, because broadcasting the tx works fine. So it's only about what other full nodes are willing to accept from me.

Great idea! 👏

Just FYI, your git host is throwing 429s for me after only a few requests. I know, AI scrapers are terrible these days, but the current request limit is too low for not shutting out real users.

Nice! 👏

Where to submit PRs for content?

Not even relay.

Also, all the popular blockchain services' nodes seem to have `minrelaytxfee` set above 0 these days (either from default or explicitly).

Apparently, absolutely nobody wants to relay a zero-fee tx from my node. Where have all the plebs gone?

Can't wait for the cosigning to finally be reliable. 👌

Europeans against tariffs 🤡

Isn't that what Common Law is?

Everything Everywhere

Ever heard of Volkswagen, the official nazi car?

(Not even mentioning concentration camp labor for Mercedes, Bosch, etc.)

As soon as I discover one that doesn't do data (incl. not anymore), the scissors come out. Can save your future self a lot of time.