@dansup you can do this is in a privacy-preserving way, no?
- Instead of asking the user to upload their contacts, get the user own email/phone/pixelfed account handle.
- Upload a hash of the private contact information, paired with clean text pixelfed account info.
- Other people now are able to find each other by simply asking your service "do you know anyone with this hash?", and in case your service answers yes, then your app can say "yes, you should talk with so-and-so@pixelfed.
Generalizing the use case, couldn't we have "PaymentRequest" and "Payment" activity types? And perhaps use the Payment Request Web API to implement the UI as a browser extension?
@josh Small correction: in the EU, the payment network is SEPA. IBAN is just the numbering system for bank accounts.
@alex Regarding "FOSS self-hosted platform", this will be the 378th time that I tell you about https://hub20.io, which started as a "payment gateway and "self-hosted Venmo for crypto", but it has since become extensible for *any* type of payment network and wouldn't take too much work to add FedNow support.
Please don't reinvent this wheel, and take a look at hub20.
This is not as bad as it sounds. You can have all the moderation/filtering/censorship done at the edges. and it also gives more power to the people and makes us all less reliant on moderators.