@francosolerio

I think thats it since it does work. I've had this issue before testing other stuff.

@ChadF @francosolerio is the problem for you specifically when you're using the Alby web browser extension? If yes, have you asked Alby about it?

It'd be great if we had a list of what LN wallets support sending metadata with lnaddress transactions.

@mitch @francosolerio

I think it depends on the receivers wallet but I'm not 100% sure on that and honestly need to read up on all of this.

I've only tested the Alby extension with BoostBox in my app so far but I think I have it working so I can try others.

Strike and Primal so far seem to handle receiving these well so far. Primal is kind of nice because it shows up as a click able link in the wallet.

@francosolerio @ChadF hmm I suppose it would make sense if the ability to receive a memo with an lnaddress is configured on the recipients LN node itself? And since Alby lets people connect their own node, there would be no guarantee that an “Alby wallet” accepts a memo with an LN-Invoice? Are you bringing your own node by chance?

@merryoscar could you help shed some light on the lnaddress memo behavior? Is it controlled by the LN node? I’m probably getting some of my terminology wrong…

@francosolerio @ChadF hmm I suppose it would make sense if the ability to receive a memo with an lnaddress is configured on the recipients LN node itself? And since Alby lets people connect their own node, there would be no guarantee that an “Alby wallet” accepts a memo with an LN-Invoice? Are you bringing your own node by chance?

@merryoscar could you help shed some light on the lnaddress memo behavior? Is it controlled by the LN node? I’m probably getting some of my terminology wrong…

@mitch @francosolerio @ChadF

The ability to receive a comment alongside a payment to a Lightning Address is configured by the Lightning Address server - it's defined here - https://github.com/lnurl/luds/blob/luds/12.md

To include the comment you pass it as a query string parameter in the pay request like ?comment={rss::payment...}

Most Lightning Address providers support this feature - Fountain, Strike, Primal, Alby etc

@ChadF what receiving wallet did you test with that wasn't accepting the comment param?

@merryoscar @mitch @francosolerio

Oscar

Fountain and Alby but with Alby I was sending to myself so that might be why that's having issues but it's still sending the payment so that strange.

Here's my Fountain walllet from the test.

Reference - OHGini2GJ9DP0y2wq9MV

This is using episode 1 of my test feed. https://podcastindex.org/podcast/7405721

@mitch @francosolerio @ChadF

The ability to receive a comment alongside a payment to a Lightning Address is configured by the Lightning Address server - it's defined here - https://github.com/lnurl/luds/blob/luds/12.md

To include the comment you pass it as a query string parameter in the pay request like ?comment={rss::payment...}

Most Lightning Address providers support this feature - Fountain, Strike, Primal, Alby etc

@ChadF what receiving wallet did you test with that wasn't accepting the comment param?

@merryoscar @ChadF @francosolerio that clears it up a lot. Thanks!

@ChadF @mitch @francosolerio

I've just deployed a change that should fix the issue you're seeing - as long as you include the feed_guid in the rss::payment metadata - the fountain wallet should show the matching episode

Would you mind sending another test?

@merryoscar @mitch @francosolerio

Still nothing DMwEzrS3U3mTHoKPnrNl

These also don't show up when sending from Castamatic.

Here's the ref from Castamatic.

rb4YsBiPpBb62sY1BJBu

@ChadF @mitch @francosolerio

It's working with your streaming payments from castamatic:

{
"action": "STREAM",
"split": 78,
"app_name": "Castamatic",
"app_version": "12.0.4",
"sender_name": "ChadF",
"recipient_name": "longy",
"recipient_address": "longy@fountain.fm",
"value_msat": 35000,
"value_msat_total": 52000,
},

Can you try another test boost to your fountain wallet and I'll report back with the logs?

@merryoscar @mitch @francosolerio

Boosted my test episode from Castamatic since that's working for streams.

ZuJNUkKNZH0Zvv8BiCcP

I also just Boosted that episode I was listening to.

@ChadF @mitch @francosolerio

"action": "BOOST",
"split": 10,
"message": "Fountain test boost. ",
"app_name": "Castamatic",
"sender_name": "ChadF",
"recipient_name": "Fountain",
"recipient_address": "chadf@fountain.fm",
"value_msat": 10000,
"value_msat_total": 100000

You should see this as a boost in your Fountain wallet with a link to the episode?

@merryoscar @mitch @francosolerio

I do see a little bit of it at the end of the label.

@ChadF @mitch @francosolerio

aah ok but the link to the episode is not displaying - could you do me another quick favour and add merryoscar@fountain.fm to the splits and send another test - then I can quickly debug it - it might be an issue on the app side rather than backend in which case we'll need to get a new version out

@ChadF @mitch @francosolerio

aah ok but the link to the episode is not displaying - could you do me another quick favour and add merryoscar@fountain.fm to the splits and send another test - then I can quickly debug it - it might be an issue on the app side rather than backend in which case we'll need to get a new version out

@ChadF @mitch @francosolerio

ok looks like it's parsing the episode now - you should see this too in your wallet for that latest boost

the only thing that's not displaying is sender_name and app_name - this needs to be fixed on the app side which will require a new app version - but we can get this live in the next ~48 hours

Do you see the episode content card in your fountain wallet?

@merryoscar @mitch @francosolerio

I see that now.

@ChadF @mitch @francosolerio

great - here's what it will look like in the next fountain app version 1.4.9 that should be live in the next 48 hours - it includes app_name and sender_name: