Michael Dilger

Those comments are already in there multiple times: > A repost is a kind 6 event that is used to signal to followers that a kind 1 text note is...

I had not thought of all of those since half of those are not things I intend to support. But this list makes sense. I was calling purple page relays...

This is all good except for the "who recommended." I don't think it is important. And it makes each list entry taller meaning fewer fit on the screen at once....

Ok I added spaces to the event kinds by updating nostr-types. I also redefined the name functions to be: - `metaname() -> Option` - the name from the embedded Metadata...

> How do we want to reconcile that? I think I will make the `process.rs` code reject them early, so we don't save handlers that don't pass the validation. Then...

> @bu5hm4nn > > > Handlers also have metadata just like profiles: > > Are they actually used? Yes. Many of them have it.

Ok I added code to show who recommended the handler. I think it runs fast enough to just show it everywhere.

You always have to publish all your recommendations per-kind. So if there are lots of buttons instead of switches, each one publishes that entire kind (all the rows?). The backend...

Maybe also (or better), when we display a URL that is a link into another client, give an option to just go to the note directly instead. So at the...

Patterns I have collected so far: https://primal.net/e/{note1} https://njump.me/{nostr-bech32} https://nostrudel.ninja/#/n/{nevent} https://npubkey.github.io/posts/{nevent} https://yakihonne.com/uncensored-notes/{nevent} https://snort.social/{nevent} https://coracle.social/people/{nprofile} https://coracle.social/notes/{nevent} https://iris.to/{note1}