Thread

Correct. Currently the metadata is in the keysend payment. Switch to lnaddress and the metadata field is there but much smaller. Oscars idea is to use Nostr to transmit the metadata basically separating the message from the payment. The apps need to implement this and the podcaster/musician needs something to receive it which was Chris's issue when he switched. This is why we've been talking about this issue for 3 years but the AlbyHub change really broke the system since that was what non Fountain apps used so to use those now you need AlbuHub. Oddly enough Franco from Castamatic was on the PC 2.0 show and said the AlbyHub change didn't really impact the amount of people using his app to Boost shows. I don't know how many people do that in his app but that's an important data point. We also had Boost before we had Boostagrams. Lightning payments were sent way before they had a message attached so if we lose them for a few months so be it. The message is a key part of V4V but if you not getting a lightning payment then your not getting a message in my book. Nostr also isn't the only proposed solution to this. Sam Sethi at Truefans.fm is using ActivityPub to try and solve this. Alecks Gates proposed something called metaboost that you add a url to your RSS feed and the metadata is sent there for you to do with what you will. (This is just a proposal)

Replies (2)

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?