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.

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!