While there may be other implementations, some of which may even be more efficient, I'd explore Oscar's solution as utilizing nostr also activates a significant potential fan base and that's not to be an overlooked advantage.

Also, in open protocols, optionality, to a degree, is important. Would implementing lnaddress mean deprecating keysend? Why not both?

Reply to this note

Please Login to reply.

Discussion

I think it does but I don't see people giving it up. It's your RSS Feed after all.

I want both and that would solve things but apps need a way to support that also.

I want to say "hey I prefer keysend but here's my lnaddress as well"

So I haven't read all of this hell thread so bare with me. (I will read it all eventually)

Next week's episode of the v4vmusic podcast will be entitled "The Case For Keysend" where I will address much of what is being discussed here.

Albeit with my own bias, of course. 🙂

I am not a nostr hater nor am I an lnAddress hater, but I do believe we should be using the right tools for the right jobs.

https://v4vmusic.com/?album=cmixpr0vk00f0od0igxv4g9q2

That one is 3 months old btw. It’s just Oscar’s proposal for the Nostr-metadata solution that I added some commentary to that I like to repost every now and then.

StableKraft.app supports that proposal btw minus some of the zap receipt stuff but all Boosts in SK that post to nost have the PC 2.0 GUIDs in them and even show up in Fountain.

I realize I’m adding to the hellthread even more here but the root post for this is Oscar’s proposal so it’s a nice time capsule.