Theoretisch sind diese pauschalen Klauseln unwirksam. Artikel von verbraucherzentrale.de

Ich würde mit der Praxis sprechen, nochmals erklären das du den Termin ja nicht verschlafen hast, sondern aus in deinem Fall gesundheitlichen Gründen versäumt hast, dich dafür entschuldigen, und sagen das daher die Rechnung nicht bezahlst. Falls die Praxis darauf besteht, wären Krankenkasse, Verbraucherschutz oder Anwalt die nächsten Anlauf- bzw. Eskalationsstellen.

Richtig und wichtig ist auf jeden Fall das nicht zu unterschreiben und auf jeden Fall zu widersprechen das der Termin geführt wurde oder das Leistung erbracht wurde. Falls du dazu auf welche Art auch immer genötigt wirst, kannst du das deiner Krankenkasse melden, die mögen das nämlich gar nicht das nicht erbrachte Leistungen in Rechnung gestellt werden.

Hängt am Ende alles davon ab wie verbohrt die Praxis ist, und wie viel Ärger du dir antun möchtest.

Again, you may quote the FSF, but there are too many users of open source, as well as developers, who got into it for the reasons I stated. I can assure you that they are not doing it so that corporations can profit off their software without giving back.

If you are developing open source, you are not necessarily developing FOSS. If you are developing FOSS, you are also developing open source.

FOSS is well defined by the FSF, and it has been for ages, and to be frank, therefore no one cares for anyone’s personal definition of it.

What I am against is having the cake and eating it, as it’s being proposed with this licensing. Either you do FOSS, or you don’t. Either you do open source, or you don’t. Either you do proprietary software, or you don’t. It’s really that simple, because depending on your project, you take the terms that you see fitting and live with the consequences. The whole goal of this proposal was to be taken more serious as open source developers and projects, and to ensure funding for further development. Cherry picking the best parts of every model, and making irrational demands does not achieve that.

As I said, I’m absolutely on board that open source licensing and open source development being taken for profit by corpos absolutely sucks, and the usual licensing models have not aged well with the much wider adoption and usage of open source, and there is a need for change - as it’s being done e.g. by elastic, redis and others with their dual licensing.

It doesn’t matter how hard you want to call it FOSS, but with this licensing terms you describe it is not FOSS, period. And to be honest, you calling out various people for not getting what FOSS is, while you fully ignore the agreed on definition by people who are actually doing FOSS is you discrediting yourself.

You haven’t found a license like this, because your model is flawed: A licensing like this will disqualify you from any kind of usage in an actual FOSS licensed environment. Personal users, which will not be providing revenue, will not be really affected by this, and are irrelevant for your point. Corporate users, which you will mostly target by this new license probably won’t be able to use your funky new license because they will need to check with legal, and your software will need to have a lot of USPs for someone to bother with that. A 1% corpo-richness-tax will not be approved by any kind of bigger company, because it’s a ridiculous amount from the perspective of your potential customers.

You’re taking yourself way to important. Open source software is not replaceable as a whole, but individual projects are. If you want to earn money with your project, that’s good on you, license it accordingly, but do not try to upsell it as FOSS.

And I fully get your point, and I’m currently working on the same problem in my in-development project, and I’m not sure yet whether to dual-license it, for similar reasons you stated, and live with the consequences of providing OSS, but non-FOSS software, or do FOSS and provide it for actually free.

Edit: Also, the xz backdoor has nothing to do with funding. Any long time maintainer (as in not just a random person contributing pull requests) going rogue can happen in funded scenarios as well.

You’re right, containers are not VMs, and I’ve never claimed that. For the matter of basic unix access control for a beginner they are similar enough to treat them as such. It’s enough of a baseline for basic security for a beginners workload imo. For advanced use cases - absolutely do not treat containers as you would VMs.

Imagine your containers as very lightweight mini-VMs. Would you run everything as root in your virtual machines? Containers aren’t really that different to classical VMs from an operations point of view. You have a different attack surface, but it is still there, and running as a non-root user inside the container reduces this attack surface, and should IMHO be the default. Privileged containers and users may be required for specific purposes, but should not be the norm, if possible.

Kein Anwalt oder ähnliches, persönliche Meinung aus meiner Erfahrung.

Zu Punkt 1. Wenn du kein ALG beziehen möchtest, und dir dir nicht sicher bist ob du bis dahin einen neuen Job findest, solltest du unterschreiben. Selbst wenn sich die Kündigungsfrist verlängert, kannst du in der Regel ja mit deinem neuen Arbeitgeber ein Eintrittsdatum bestimmen, welches dann eben nach den X Monaten deiner Kündigungsfrist liegt.

Zu Punkt 2. Du wirst nicht befördert. Wenn Dein Personalchef das einmal wegen Bullshit abgelehnt hat, wird er das wieder tun. Lass deine Beschreibung aktualisieren, und fordere ggfs. am Ende auch ein Arbeitszeugnis ein. Denk an dich, und nehme alles was dich weiterbringt mit.

The difference is, that Netflix (or Spotify, or whatever) does bring value on its own. I am paying money to comfortably and legally stream content, which itself is paid for and licensed by the streaming provider. From the perspective of a lazy end user, it’s worth it, because you do not need to care about downloading, finding releases, opsec and whatnot. I don’t want to protect Netflix, fuck corporations and subscription services, but password sharing was always only tolerated at most. From the same end user perspective, reddit is just an empty platform. The content is brought in free of charge by the community. And now not only they want the same community to pay, but also for an objectively worse experience? I don’t think that you can compare that.