hodlbod

I see, yes I was misunderstanding. Interesting idea, but I'm not sure how useful it would be.

The consensus from a while back was that markdown is fine insofar as it is also plaintext. So lists/headings are fine, but markdown links (for example) are not. For clients...

I don't, somewhere in telegram probably. That was @fiatjaf's opinion iirc, and I agree. Edit: ah, I see he's still at it!

This idea has already been thrown around a fair amount, personally I think the best option is to keep most use cases in-protocol as much as we're able following https://github.com/nostr-protocol/nips/pull/259....

But why?

This is just a way to use nostr relays as a database. The schema is a proprietary format, so I don't see what defining how to fit the schema into...

So just use NIP 78 for your proprietary schema events

I like this, especially the introduction of hierarchical keys and user passwords for a better happy path, although it's a little outside my wheelhouse to actually evaluate. I do think...

Using `t` for metadata not meant to be read by users is a mistake. Imagine a valley girl shouting "hashtaaag #audiospace!" as a litmus test. I would prefer corny chat...

See "self-reporting" in NIP 32