Oscar Merry on Nostr: nprofile1q…0mp2c nprofile1q…f7xwn nprofile1q…53ram Bumi is right that we need a ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqu889jx72l4rn6vsva3jqxyhtekq4qhanwh296lz30ajpsrlhuvfqe0mp2c (nprofile…mp2c) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrsuf7xwn (nprofile…7xwn) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0fp3ehl8utp98zgk6lx87uwkfxm9zq6z9varapeuluz9cdf3zfvse53ram (nprofile…3ram)
Bumi is right that we need a new way to share the boost metadata because if we choose this path we won't have the keysend TLV records.
My suggestion is to use Nostr Payment Events - I have added an example of this to my demo so you can see the kind of event an app will generate when a boost is sent - https://pay-a-podcast.vercel.app
But I don't really mind how we share boost metadata going forward.
The main thing is that keysend is not well supported.
Bumi is right that we need a new way to share the boost metadata because if we choose this path we won't have the keysend TLV records.
My suggestion is to use Nostr Payment Events - I have added an example of this to my demo so you can see the kind of event an app will generate when a boost is sent - https://pay-a-podcast.vercel.app
But I don't really mind how we share boost metadata going forward.
The main thing is that keysend is not well supported.