Thread

Replies (2)

Actually, this is the problem. You can do it, but there’s several huge disadvantages right now and I don’t think most people realize it. Important Metadata podcasters need to credit supports is missing, just not even captured. And importantly to me if you’re self hosting a node, it gets even worse and anyone in the split doesn’t get any metadata. When you receive the boost, you have no idea the total amount, and the most situations you won’t even know who sent it. It depends on all of the systems between. It currently only works in very limited situations. I’ve been testing this the hard way with some of my shows, and it was a mini disaster. Even though I’m a big proponent of using lnadress I had to roll back to using my node address/keysend for now because of all of the shortcomings with the current implementation. Being able to properly credit people who support the show is a vital and important part of the value for value cycle - that is fundamentally broken right now with the current lnadress implementation. If the current implementation sees wider adoption, it will destroy boost for podcast. I don’t say that lightly, you probably know how critical this is for my shows. I think some key insights that I have here that maybe others are missing is that I run multiple shows at scale that are funded by boost. Multiple episodes of my shows are often in the fountain top charts each week. I’m not bragging. I’m just pointing out, it’s significant us. We self-host our entire infrastructure. And we build tooling around boost, so that way we can properly credit those who supports us. And I’m a big supporter of other v4v podcast and as a listener, I boost a lot . So I really been looking at this for all angles since about December. If I could go on the podcasting 2.0 show every week and yell that we have a problem here I would! I think a lot of people are missing this because they’re not quite as deep into the technicals . Technically lnadress is supported. But it’s a disaster in its current implementation and limitations. It also reinforces centralization because just look at the practical implementation so far. Fountain is the easiest and most complete implementation. Even using Alby Hub the experience is sub-par. You will get the stats. And your SOL if you just want to run your own node and lnadress.
↩ replying to Chris Fisher
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?