What’s the difference?

It works on my machine, most of the time.

You can make solutions popular with a shit ton of money. Doesn’t necessarily make them good solutions.

There’s https://redbean.dev/, but it’s not quite what you mean.

It runs on the browser with a local host reference to a lua server with access to c libs.

Javascript has airbnb style guide, enforceable through eslint. There’s also react related eslint extensions to give you a lot of best practices to follow.

There’s also prettier, which is just about formatting.

Booooo

ci(

I’ll leave the regex to validate an ipv6 address as an exercise to the reader.

They’re better off for life if you donate the money you’d spend with yt once for each, once per month. Many will have their turns.

Paying for Netflix isn’t fine either.

Let me agree.

When things feel out of control, focus on small things you can control: sleep at the time you decide to, exercise the time you decide to, meditate the time you decide to, get pen and paper, write down everything that comes to your mind, be aware of when your mind go to places you don’t want it to, volunteer and support those that are close to you selflessly. And then maybe you get closer to finding yourself.

But if you have the means, professional therapy, for sure!

I don’t think 42 upvotes represent how historical is that speech. Am I being too optimistic?

Actually, half of the point is to reduce seniority with cheaper unexperienced grads.

Claim supported by companies still hiring full speed for lower level positions, and not replacing attrition with similar levels of experience.

Olive and Ollie.

Articulating the obvious is extremely important.

Federated activitypub music app feels possible, too.

Single client, multiple providers, much music! Such wow!

I feel media is harder to get some critical mass, though. Peertube struggles to get users, for example.

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.

Exactly! And I would expect taxi unions from different regions to generally cooperate to build a network of customers.

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.