Ricardo Arturo Cabral Mejía

This is already supported on Nostream.

I might just disable NIP-26 on Nostream at this point. It just gets more complicated and complex for very niches use-cases. Maybe one day I'll get it.

Could we use parameterized replaceable events? We just need a client that supports editing and then the conversation can happen on Nostr.

> I was thinking of doing editable texts using parameterized replaceable events, like this: > > > > ``` > > kind 10 -> article title > > kind 11...

> I don't think it should be a kind 1 as that will cause these things to show up in social clients feeds and make not very much sense. I...

Concept ACK. Should be trivial to implement in Nos2x. But this only provides identity with an app directly on the browser. I would want this to work with the proposed...

> @lylepratt that's a very cool approach, good point re browser APIs not working on mobile. > > > > One issue you could have with a DM based approach...

> >I prefer this approach much more. > > > > You mean prefer it to DMs or prefer it to `window.nostr.authenticate()`? I prefer URI handlers as opposed to DMs....

Relevant perhaps: https://github.com/nostr-protocol/nips/blob/329cd8d8a19fd1dcb12df7eb7a5d640b2a5b6bf8/19.md#shareable-identifiers-with-extra-metadata

> By the way, `lnurl-auth` has gained a lot of love in the past years and many users and websites seem to love the idea, however the protocol has a...