Nostr Web Client

Ok so just taking a snippet of what you're addressing here. Let's assume lnaddress is widely adopted across the ecosystem, that still leaves us with the Metadata issue. Is that accurate?

Just brainstorming but seems like from there the solution has to be client side... lnaddress payments do allow for a text field. The client could potentially autofill this with the essential Metadata such as sender, client, show, and track/timestamp when generating the invoice. It would take a meeting of the minds from major clients to implement but could be done i think?

ChadF and 33 others 3mo ago

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)

Reply to this note

Please Login to reply.

Discussion

BITwise 🐳 >>= RIGHTish 3mo ago 💬 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?

ChadF and 33 others 3mo ago

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"

Sir Libre 3w ago 💬 1

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

ChadF and 33 others 3w ago

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.

BITwise 🐳 >>= RIGHTish 3mo ago 💬 1

Metaboost sounds like it would work well with nostr. Assign an npub pointed to a specific relay and Metadata simply posted as notes. Metaboost simply acts as bridge or client for users to pull the nostr data. View as native client or bridge to node.

ChadF and 33 others 3mo ago

Oscar's proposal lets apps post the metadata to relays to then be pulled down.

I'm working on zaps.podtards.com that post to nostr:npub1k34lqqeqa90e269gtw4r5z3h0hgejj9hnf8lpkmc2jzq5tl2ru8qqkwhjf.

Works with Alby since the addresses in the feeds are keysend but I'm working on adding other stuff to help the 2.0 devs see this in action.