@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?
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?
1