nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7 why can’t we skip the fetching part and I just send it to you direct?
@nprofile1q...
we could - there's just the question of how to avoid fake data if anyone can post payment metadata to a public API endpoint
with the rss::payment spec the url to fetch the metadata originates in the payment comment - so there is a direct tie to the actual payment and since apps host the full metadata on a url their reputation is at stake if they fake data
I am open to exploring solutions to this where apps don't have to host the payment urls - and promise I won't mention nostr 😅
we could - there's just the question of how to avoid fake data if anyone can post payment metadata to a public API endpoint
with the rss::payment spec the url to fetch the metadata originates in the payment comment - so there is a direct tie to the actual payment and since apps host the full metadata on a url their reputation is at stake if they fake data
I am open to exploring solutions to this where apps don't have to host the payment urls - and promise I won't mention nostr 😅
1