@nprofile1q... @Darren @nprofile1q... Thank you!

@nprofile1q... Do we know that FediDB is only Mastodon instances? I'm suspecting it isn't.

@nprofile1q... @Darren @nprofile1q... Podcast Guru and Castamatic are both also sending boosts to lnaddresses (specifically, [email protected] which is mine). I don't know what they charge, but I don't have too much worry about that.)

Am I doing the RSS bit right? The 'method' bit confuses me.

@nprofile1q... @nprofile1q... I would rather use some of my energy on people that are positive and want to work with others to move things forward. Your “final post on this matter” in Github shows that you are not that person - preferring discord to unity, complexity to simplicity.

If you have “stopped caring”, then could I suggest you close this proposal in GitHub, rather than it be a confusing and destabilising presence to the rest of us who just want to move forward with a solution.

You tell others who have a different opinion on that they are guilty of “abuse” and of selfishness. That is not the view of someone who has stopped caring - it’s a mendacious, ungenerous, divisive view, and worthy of nothing other than a full unreserved apology to those who still do care. Learn some manners.

@nprofile1q... This is a tease! I’ve been trying to find this out for the last three days

@nprofile1q... @nprofile1q... @nprofile1q... I would add that every new payment system we add into this magnifies the complexity in many different ways. If we were starting again, what would we do?

If Bitcoin and sats scares people, then what can we implement *now* that works for micropayments, which is available everywhere? If there is a genuine requirement to move away from Bitcoin then let’s do that - but if we have seven payment systems in a spec, this will be as dead as the SocialInteract tag is, because it was built to require a podcast app developer to support every single social system out there.

We’ve learnt our lesson from SocialInteract, which was a total failure because of massive, unneeded complexity. How do we take that learning and move on?

@nprofile1q... @nprofile1q... I notice @nprofile1q... can’t even be bothered to contribute. Disappointing. Previous experience shows I should have expected it. Let’s ignore him and move on, if he is too precious to work with others. Nobody wins from little tantrums.

A simple “note with payment” pointing to a JSON file - which is all this is - works with literally any currency and any payment system. The only requirement is that there is a note with payment, which there is in virtually any monetary system.

It could be refined to use shorter identifications in the payment note - rss::payment::stream is lengthy, especially when many bank accounts only have short payment note lengths.

What we have - already supported for lightning - is a great step. I don’t see why it couldn’t work for every other platform out there.

Let’s not overcomplicate it with 400 different payment mechanisms and requirements for servers and potential centralisation. How can we build on it without complicating it further?

@nprofile1q... @nprofile1q... Why not choose the one three apps have already implemented?