Then it should be Vin Diesel…

The driver is always at blame, even if it was on. They turn it off for marketing claims.

PS: fuck elon

Well, there is no train station at my house. Or Aldi. Or my kids Kindergarten. And I live Germany, where public transport is excellent on a global level (memes about Deutsche Bahn aside).

Cars will be necessary for the foreseeable future. Let’s make them as safe as possible while investing in public transport, they are not mutually exclusive.

PS: fuck Elon.

It not about responsibility, it’s about marketing. At no point do they assume responsibility, like any level 2 system. It would look bad if it was engaged, but you are 100% legally liable for what the car does when on autopilot (or the so called “full self driving”). It’s just a lane keeping assistant.

If you trust your life (or the life of others) to a a lane keeping assistant you deserve to go to jail, be it Tesla, VW, or BYD.

Well, I don’t believe so, but as you said it’s ultimately for a court to test it.

That wording is pointing to reselling the program or the same functionality. Of course if your service is “fast key based data retrieval” it would violate the definition, but something like “low latency gaming notifications” would not, because the value is gaming notifications, something redis doesn’t offer. Same as if your service uses encryption in transit, you’re not just reselling openssl.

Agree on the court, but the wording is super specific. Doesn’t matter if you couldn’t build it without a redis-like component, because of the speed or whatever, it is targeting “offering the program as a service”. There’s even an FAQ on the mongodb (SSPL authors) site regarding this. Unless your program is just a proxy to access redis, you’re fine.

I don’t think that’s correct. It maybe prohibits people from building a service to offer redis to third parties on Windows, but you can run redis in your stack on whatever OS you want, as long as what you are building is not “redis as a service”. So any end-user SaaS that just uses redis as a cache is not bound to section 13.

And even if you built a redis as a service, the operating system is not explicitly mentioned in the license, so it would be for a lawyer to say whether that’s required…

Like what? Heavy metals would precipitate, organic compounds would break down. (I’m not a chemist, just have general science background).

Why would you capture it? It’s waste water, evaporation into the atmosphere should be fine.

I guess if there’s one thing Indians know about, it is sandals.

Dürüm, du Geringverdiener!

Und ohne Blei.

Oida!

Of course you have to pay for a commercial license, it’s in the name. Development, tooling, support, etc, all costs money.

I like the distinction. If you want to profit from open source, make your code open source. If not, pay up.

Redis allows a third option, a commercial license.

To be fair, I know redis and gitea (barely, gitlab is way more popular) and not the other two. Enterprise support and name recognition are quite important for government usage.