• 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle




  • Fair points.

    I strongly associate FOSS with right to repair, in my mental models. To me these topics walk hand in hand, and when I extrapolate from FOSS concepts I also end up extrapolating from right to repair concepts.

    Yes, you can obscure slices of the system through non FOSS software. In which case, the thin layer of FOSS indeed wouldn’t solve it. I’m assuming FOSS end to end, where the owners of the car can choose whatever they want for their car. And I’m sure many people would follow their trusted mechanics advice about flashing the FOSS OS in their 50k car. That’s what farmers are fighting for in the US, for their hundreds of Ks tractors and trucks.

    There’s another layer of struggle under FOSS. And if we could have legislation passed that requires companies to release their e2e firmware under FOSS licenses, that screen wouldn’t be a problem, and we’d be likely to be able to use the same CarOS just like we can use the same Linux kernel in so many different pieces of computing hardware.

    Unfortunately, legislators are in the pockets of car manufacturers and their financeers, too. So you’d need a revolution to get that kind of stuff passed, unfortunately.


  • Free software does not imply that you have the ability nor knowledge to flash any new software

    It does. Free software interfaces, unlike proprietary, are open standards. Either of that’s cabling or wifi interfacing, a free software interface is common knowledge, which could be used to produce devices allowing for what I mentioned.

    Ford doesn’t need to provide their own software for you to flash your own ui, rtos or whatever you want to the car.

    If it was free software, yes, they would have. Therefore, the importance of free software.

    it just means the software is usable elsewhere for free

    By the things you say, you probably don’t even understand “free” software means libre software. I’d suggest you go for a nice Internet research journey in the world of free and open source software: https://itsfoss.com/what-is-foss/







  • 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.


  • 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.



  • 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.




  • I do. But that’s the point of dogwhistling. Plausible deniability so that people pointing at it can be called insane.

    The message on the post was “you can even make fun of children suffering anymore, screw politically correct people”. That’s very common right wing politics.

    You will also notice someone mentioning 14 seconds video in the comments. I’m sure it’s a, coincidence, and not fascists exchanging pleasantries. The complaint was the same though, about the “fun police coming after people”.

    That’s the subjacent message that was spread, this time. Apparently moderate right wing, reinforced by dogwhistling, plausibly deniable.