thought experiment (uber + abuse?)
@adeptomega I'm in no state of mind to tackle #1 right now. #2 I would probably manage by defining a "payment model API' that puts the entire business of determining how money gets managed into a subsystem which must be implemented by the operator of the software much like the CoC or federation list has to be managed by the host of a Masto instance. That allows for different people to control pricing as they wish.
thought experiment (uber + abuse?)
@adeptomega A coop running the software could make the app a benefit of membership and make the payment system a lookup for membership. A taxi service could publish normal fares. A non-profit could add a small percentage as a service fee up to some cap earmarked for infrastructure maintenance. And all three could use the same core software.