Just saw the discussion around the Haier Home Assistant takedown and thought it would be good to materialize the metaphorical blacklist.

73 points

Should add Reddit. Started out as FOSS, closed down their GitHub, then killed their API which killed dozens of third party integrations impacting hundreds of thousands of users.

permalink
report
reply
15 points

And now apparently removing all comments that mention Lemmy…

permalink
report
parent
reply
5 points

lol dw we all know

permalink
report
parent
reply
36 points

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.

permalink
report
reply
6 points

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?)

permalink
report
parent
reply
4 points

No. Never. It’s a ruse.

permalink
report
parent
reply
33 points

The new owner of Simple Mobile Tools? Buying it and then adware stuffing? ZipoApps?

permalink
report
reply
31 points

Don’t forget to add Nintendo

permalink
report
reply
6 points
permalink
report
parent
reply
31 points

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!

permalink
report
reply
16 points
*

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.

permalink
report
parent
reply
5 points

Maybe your could also add organisations (companies, government agencies, NGOs,…) that create standards in such a way that the standard is hard or impossible to implement in open source implementations?

permalink
report
parent
reply
0 points

I.e reddit raising API costs high enough that it effectively killed it.

permalink
report
parent
reply
4 points

IBM is so good and so bad. Their machines are so open. Their software is not.

permalink
report
parent
reply
1 point

i feel like the MPL is fsr superior and fairer than the MIT license

permalink
report
parent
reply
2 points

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.

permalink
report
parent
reply
4 points

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!!

permalink
report
parent
reply
-1 points

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.

permalink
report
parent
reply
2 points

Are you not familiar with Richard Stallman? Here’s one piece.

permalink
report
parent
reply
-2 points
*

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.

permalink
report
parent
reply

Open Source

!opensource@lemmy.ml

Create post

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

Community stats

  • 5.1K

    Monthly active users

  • 1.7K

    Posts

  • 29K

    Comments