Just saw the discussion around the Haier Home Assistant takedown and thought it would be good to materialize the metaphorical blacklist.
It might be a good idea to do the exact opposite I.e. make a OSS whitelist. It will be much easier to maintain given the scale of applications/services/products.
Although I agree, it’s tough to make a whitelist than a blacklist, as the latter requires only 1 bad decision, the former is tough to assess (how many good decision to be on the list, ex Microsoft support lots of open source projects, should they be added?)
It’s probably a good idea to have a stronger definition and mission. Here are a few scenarios you should consider.
- FSF defines anything that’s not copyleft as hostile. That’s most companies. I personally don’t think I can tell my users what to do with my software other than remove my liability so I vehemently disagree with Stallman.
- Mongo wrote the SSPL and MariaDB wrote the BSL. Both licenses are seen as regressions. I personally respect the MariaDB case and have been harassed by too many Mongo salespeople to say the same about them.
- Platforms like AWS are the reason companies like CockroachDB and Elastic implemented restrictive licenses.
- IBM has been gutting open source through its acquisition of Red Hat. This is a common story; Oracle has been screwing *nix longer.
- Protecting trademarks causes a lot of consternation from users. The Rust Foundation is the most recent example of this I remember blowing up the FOSS community.
I like your idea a lot. I think it needs some definition to be very successful!
FSF defines anything that’s not copyleft as hostile. That’s most companies. I personally don’t think I can tell my users what to do with my software other than remove my liability so I vehemently disagree with Stallman.
I’m not planning on counting that as hostile behavior. Organizations can choose a license for their software (and I can choose not to buy/use it). This collection is mostly focused on companies that hurt existing Open Source software. Such as sending a cease and desist to an unofficial plugin/extension or closing down software that was originally open source.
IBM is so good and so bad. Their machines are so open. Their software is not.
FSF defines anything that’s not copyleft as hostile. That’s most companies. I personally don’t think I can tell my users what to do with my software other than remove my liability so I vehemently disagree with Stallman.
Citations please? Using a pushover license instead of copyleft is not hostility but a missed opportunity. Copyleft is about a community safeguarding itself and making sure the software can’t be used in proprietary applications as much as possible.
Are you not familiar with Richard Stallman? Here’s one piece.
We in the free software movement don’t think of the open source camp as an enemy; the enemy is proprietary (nonfree) software. But we want people to know we stand for freedom, so we do not accept being mislabeled as open source supporters. What we advocate is not “open source,” and what we oppose is not “closed source.” To make this clear, we avoid using those terms.
Your own citation disproves the hostility claim. To answer your question, yes I was a student associate member of the FSF. Nowhere did I learn to treat non copyleft licenses as “hostile.” In fact, they are so prevalent that considering it hostile/harmful would be fruitless. They are still free licenses at the end of the day (at least the ones that dont violate the four freedoms)
Edit: actually we are hostile to some open source licenses, like the ones that prohibit commercial use to any group or individual! That’s a huge no-no.
Your pull quote expresses hostility to not FSF idealism. I get that you drank the koolaid and believe you get to tell anyone who uses your product what they can do with it. That’s just telling a cook what they have to do with their ingredients just because they bought from you. It’s okay.
What??? It’s literally just a group distinguishing itself from another. Both Open Source and Free Software work together against a common enemy.
It’s good to distinguish different groups that have different methodologies, motives and goals to avoid friction. This essay is actively trying to avoid hostility.
you get to tell anyone who uses your product what they can do with it.
Horseshoe theory but for copyleft and copyright. What a fucking joke. I thought you had good intentions but now I know you’re unwilling to see another perspective.
You don’t seem to understand the implications of GPL and you’re real interested in pushing an org that propped up a pedophile. Based on your comment history, you’re either a troll or you really are into some objectionable shit.
I don’t have a problem with FSF or copyleft. I do have a problem with people that don’t understand either.
i feel like the MPL is fsr superior and fairer than the MIT license
I personally use Apache 2.0 because it’s been upheld in court. I’m not sure if MPL has been directly challenged in court. Either way, I agree with the sentiment. The legal perspective is why I moved away from MIT/ISC.
you should considwr MPL, if someone found a security vulneravility theyd be legally obligated to tell yoy for example. also, it still allows commerical closed source software. try it!!
Don’t forget to add Nintendo
I really like seeing codeberg being used more.
Also I’m definitely keeping my eyes on this repo once in a while 👀🧐🍵
The new owner of Simple Mobile Tools? Buying it and then adware stuffing? ZipoApps?
Add Mazda to this list please.
The developer of this plugin for HomeAssistant apparently didn’t have insurance and couldn’t risk the legal fight. This is the DMCA take down that Mazda issued for the reason that the code “provides functionality same as what is currently in Apple App Store and Google Play App Store”
https://github.com/github/dmca/blob/master/2023/10/2023-10-10-mazda.md
Additional Coverage: https://arstechnica.com/cars/2023/10/mazdas-dmca-takedown-kills-a-hobbyists-smart-car-api-tool/
I’m shocked that the list only contains one
I created it less than an hour ago. If you have any other suggestions please share (or send a pull request).
EDIT: The list contains 3 companies now
We are writing to inform you that we have discovered two Home Assistant integration plug-ins developed by you ( https://github.com/Andre0512/hon and https://github.com/Andre0512/pyhOn ) that are in violation of our terms of service
Did the guy explicitly agree to their Terms of service? If not, how can he be in breach of them?
cease and desist all illegal activities
What illegal activities exactly?
Feels like unenforceable scare tactics, but IANAL.
Surprised that most hardware companies aren’t on the list. AMD, Intel, Nvidia, Apple, Broadcom all are hostile to reverse engineering or in Nvidias case, not even bothering to do the bare minimum for an ultra lenient Torvalds.
It’s open to pull requests
Sure would be a shame if people used this blacklist as a basis for leaving negative reviews on Amazon.
