souperk

Do you have any other taxi related experience or knowledge you would like to share? You seem quite knowledgeable.

Also, do you think local taxi groups/companies/coops could benefit by hosting their own instance in a federated Uber like platform?

Actual ride sharing, like, independent people using things like bulletin boards to both get to work together at a mutual benefit, is a fantastic practice. But when you try to make it some big service you basically get a half assed replacement for taxis that shift the financial burden onto drivers and cut prices as a result.

That was the reason I started looking for a ride-sharing service in the first place. I was in Larissa, the morning after the Tempi train crash occurred. I was about to ride to Athens with my car and I realized that the only train track of the country was going to be out of order for months (still is). So, I decided to offer my seats for free to anyone interested, I made a post on a fb group about ride-sharing, but by the time someone reached out I had already left.

That's when I realized that user experience matters, that person was actively looking for a ride when I posted, but they missed my post. So, e-mail notifications was the 2nd feature I developed.

You could basically give drivers 100% of the profits minus hosting costs/development costs (dev might fall away depending on the model).

I would assume that drivers are hosting their own instance, and they get to decide both (a) how much they charge and (b) what portion of their profits they donate to the devs (especially modifications they need).

Money, ratings, reputation, identity stuff are all better solved with blockchain than with federation in my opinion. You don’t want to have to check the repuation of each instance, every instance might handle ratings differently etc… It would be a mess. Rather you’d want to only be worried about driver reputation.

I think this is already happening with taxi services. Here in Athens, there are a dozen of services you can call to order a taxi, and people (at least younger generations) are aware of most of them and use them depending on their preferences.

Also, another layer of passenger protection could be the instance they use. Instance admins could filter the driver instances they federate with, allowing only drivers with specific criteria. An issue I see here is that the federation criteria would be much more strict, potentially marginalizing people or making the barrier of entrance more difficult.

Absolutely, I would consider instances that are run by cooperatives, probably with some segregation between drivers and passengers.

Other examples of instances could be:

• LGBTQ only passengers (or drivers) - I have friends that are afraid to take taxis because they don't trust cis-men taxi drivers.
• Female only passengers (or drivers) - pretty much the same issue
• Localized instances - Jurisdictions are hard to manage.
• Unions

lol I never stopped to think about it. Now that I have, I am terrified.

Some quick thoughts:

1. For Uber like services, I always assumed drivers and passengers are going to reside to separate instances that each tends to their needs. So, driver instances could negotiate with passenger instances and come up with fair pricing.
2. Each driver could enter their rate and have their instance automatically bid for them (assuming they are available) when a new ride is requested. The passenger (or their instance) gets to decide which driver to use.

Disclaimer: I am not trying to make any money out of this. I just hate big corps and like coding.

What you could do is an open source platform that integrates all car pooling services and gives you the best option.

Interesting take! So far, my carpooling MVP has been about bringing people in contact, assuming they can handle money transactions on their own. As you mention, jurisdictions are going to be a huge problem, which I wouldn't dream of handling on my own.

Here in Greece, the most popular media for carpooling is a Facebook group, where people can post either offers or requests for trips. So I tried to think of an MVP that could provide help those people while (a) not having to use Facebook and (b) have an improved user experience.

The wolf, realising the error of his ways, decided to change his diet and become a vegetarian, befriending all the pigs.

Aren't wolves like unable to process plant based foods? Like, they eat grass in order to vomit or something?

Human babies need a buff, they're functionally useless for far too long.

Capitalism now wants to extract value from babies??

Now I am kinda wondering if we could somehow fuzz it...

Spotted the software engineer

ADHD 2.0 on goodreads for anyone interested.

Also, I am wondering if Taking charge of ADHD (2nd edition) is any good. The first edition has mixed reviews on goodreads .

btw, I am scared of books, I haven't been able to complete a bunch of them without intense dedication. Any tips are appreciated.

Sounds to me like the equivalent of a product manager asking for blockchain features in order to save a failing startup.

As always I would say there is a huge "it depends".

For context, I am part of a small team of engineers, working on a relatively new product, we have continuous deployment setup for our release branches. We prefer many small PRs, think at least a PR a day per engineer.

I am responsible for setting up a new e2e test suite right now, so it's possible I reconsider later on. But, there are a couple lessons learned from our previous iteration.

1. Our pipeline was slow (20-30 mins), flakiness was a no go. Decreasing pipeline time increased tolerance for flakiness.
2. Flakiness on the pipeline translated to flakiness on the production instances. When we started caring for those our sentry got much more happy.
3. We didn't have the time to go back and fix issues, so we stopped having nightlies. If it's important enough we should block merging on main and fix it.