why should it be federated? I didnt heard of any restaurants that got blocked. I only heard about the crazy fees. Plus even Mastodon/Lemmy didnt solve how to easily manage your instance.
I think federation makes it easier for customers to circulate between regions and find providers for regions that their original platform doesn't cover, using the same client. Or by adding multiple backends to the same client. They could trigger a single request for service in multiple providers, increasing the likelihood that someone will pick it up.
The fees would be defined by the operators. If an operator starts to gouge drivers/customers, it should be easy to kick them away and start a new one since the tech barrier and app barrier are removed.
I think the people working with the fleet, and service providers are the main stakeholder and the app has to be built for them. Customers are almost a second class citizen, in this model. For mastodon/lemmy, it is built for the end user first, which makes moderation tool lag behind too much.
It's an interesting idea. I'm guessing the largest hurdles would be: trust, funding, and legal. A large part of it I think depends if it's being run altruisticly or as a business.
Uber/Lyft and others have come under intense legal scrutiny all over the world. The drivers typically need to purchase & obtain a license to be able to drive, and come into agreement with local taxi operators.
What motivates the drivers to drive, ie is this a job or are they volunteering? Does each ride cost or are the rides free? If the rides are free, are the drivers doing it out of the goodness of their hearts, or are donations covering the rides? If rides aren't free, who is processing those payments? Who decides what drivers get paid and what customers get charged?
Lastly, as a ride-operator, how do I build trust with my drivers? As a customer, how can I trust the instance I am with? If something happens in a ride, is there someone I can contact? Can I get refunds? What if something even worse happens, who is on the hook?
For not depending on altruistic action, I like the opencollective model. Both for self financing but as a platform too. If you use their platform to provide paid services, you share revenue for development. And then development/processing is charged from the collective fund through open recipes.
I expect most drivers to already be legal drivers. And the main point is to empower organisations that are already in place. Legally, I suppose the difference is that this is actually a technology project, with technology goals? The legal responsibility would be of actual operators.
Drivers drive as a job. Fees defined by the operator. Processing through payment modules. I was thinking each would need their own stripe API keys, for example. Split is also defined by the platform.
Trust would be built through moderation and finance. Operators can make some screening of customers and drivers, to increase trust between both groups.
I expect operators to provide support for any problems, since they choose the drivers explicitly. Including refunds. They got full control over finance.
If anything worse happens, I'd expect the operators to be in the hook. This is their service, actually. They have finance, they have actual full control.
If someone makes online stores with WordPress and doesn't delivery their goods, or deliver harmful goods, I don't imagine WordPress can be held accountable.
I'd love this if for anything so that platform co-ops in different cities could be more universal from a users perspective, plus more brand recognition (which platforms that need people on both sides live abd die on).
Something like this is what I imagine as a "bening version of the web3". I'm not an expert (by far) on any of this, but from my limited understanding, the biggest obstacle in practice is the payment method. If we are talking about online payments, that (AFAIK) makes the legal aspect much harder. Leaving the payment outside the platforms may work, but that would make some parts much harder (traceability, accountability).
Personally, I like much more your version of the future that this one
Source: dumb future: "@briankrebs They're coming for…" - Hachyderm.io
Well, yeah. That is where payment modules would need to be developed by region.
Possibly some umbrella solution like "insert your own stripe api key".
But also you shed some light over finance management between operator and providers, thank you! I think this should provide outstanding balances, and some functionality for marking/confirming payments, but banking itself probably has to be done independently.
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Community icon from opensource.org, but we are not affiliated with them.