Don't worry, there will always be an IRS for us plebes.

Not behind, ahead. Just you wait.

The US government doesn't (to my knowledge at least) have copyright protections so MIT wouldn't be possible. BSD 0-Clause is just better because e.g. Austria doesn't allow you to cede copyright to the public domain and CC0 directly mentions the public domain in the terms of the license.

Uh no … the US is behind on this and payment platforms and invoice creation and a ton of other shir

Correct. They're bad. And if someone releases code under CC0 that has patented stuff in it you may be liable for using their patent without permission because CC0 says in section 4a,

No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.

Compare that to MIT which is considered to implicitly grant patent rights by saying you may deal in the software without restriction. Apache specifically gives you explicit patent rights in section 3.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

So the problem is that CC0 in it's public license fallback specifically says that it does not grant patent rights.

CC0 is a trap for software. Please avoid it. Please encourage others so avoid it.

To the extent of my knowledge, the only public domain dedication with permissive license fallback that is approved by both FSF and OSI is the WTFPL. Which is also a crayon license. Public domain is a weird concept and not all jurisdictions have it and not all jurisdictions allow you to manually put things into it. This is why they need the permissive license fallback. You're better off using a well known and well understood permissive license.

I'm not sure you got what I meant, which was that the US may end up dragging others in its wake. Time will tell. I just know it's not just the US that has seen a rise in right wing politics.

And so, yeah, I said it kind of tongue in cheek, but I'm concerned it's the start of a trend. But hey, maybe there's an asteroid inbound.

Interesting, SPDX does not list 0BSD as FSF approved, but FSF does approve it. This isn't the first problem I've seen with SPDX's list. They say CC0 is FSF approved but FSF only says it is approved for things besides code.

Various Licenses and Comments about Them - GNU Project - Free Software Foundation

(www.gnu.org)

SPDX License List | Software Package Data Exchange (SPDX)

(spdx.org)

Here the second right most party just let the coalition fall

Can you elaborate a bit, as far as where here is and what coalition? I have ideas but I don't wanna make assumptions. And obviously that's is you feel comfortable doing so, not trying to blow you up. But I'm interested in what's happening elsewhere you know? And I am just not sure I trust the news.

In NL Geert Wilders let the coalition fall but it was one of the worst coalitions we have had

Thank you for the through explanation! That was very helpful

Not just that. The tax preparation industry has gotten tax more complex and harder to file in the US

You get the government you can afford. The tax preparation industry has been able to buy several governments