this post was submitted on 16 Aug 2023
30 points (85.7% liked)
Fediverse
28555 readers
455 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I like this idea so much. The problem is quality control.
Uber Eats here in UK really struggles to delivery an accurate order. And where there is a problem the driver blames the restaurant, the restaurant blames the driver, and Uber or the restaurant (it's frequently not clear where to begin) may or may not issue a refund and perhaps an apology, but that doesn't solve the problem which is you don't have the food you were promised and that you paid for. No one takes responsibility for that.
Who in a decentralised system can or should take responsibility?
Amazon, for all their many faults, claim to be trying to make the most customer-centric company on earth. A lot of their early success came from a stellar returns policy, shouldering responsibility for products they dispatched, as well as excellent prices. Not so much now, but certainly during their incredible retail growth period.
How do you code for that in a federated system? And, if you can, how do you compete in a wider marketplace with an Amazon monolith?
The customers. :) Ear me out:
The main reason why there is so much problems with deliveries (way more with UPS, DHL and the likes than Uber Eats deliverers, in my own experience) is because we're not their customers, in their heads. They're paid by the merchants (UPS/DHL/etc are paid by your shop keeper), or they're paid by the platform (rider is paid Uber Eats/Deliveroo/etc), but the end customer is just part of the constraints, for them, especially since the customer doesn't even choose who will deliver their package (you don't like UPS? Too bad!). Give the customer that choice, and make them pay directly for the delivery to the deliverer, and I guarantee all those problems will go away. This is why I said we need a decentralized reputation system : so that the customer can see the reputation of local delivery service before selecting them.
When the problem is with the shop, well, this is already sort of dealt with. We already have reviews systems and we already select our shops, so it does happen that shops behave poorly, but not for long. Although, users have to be educated about verifying reviews, and developers have to implement countermeasures and stay on top of the review cheating game.
And to avoid problems with the platform, we have the interoperability of standards like ActivityPub : there is one global network (like the fediverse, or the web), and multiple programs are implemented to use it. They have a incentive to work well because there is competition, something that centralized platforms eliminate altogether.