←back to thread

431 points dangle1 | 3 comments | | HN request time: 0s | source
Show context
Calavar ◴[] No.41861254[source]
We've lost a lot with the deletion of this repo. Not the code - that's already out in the ether - but the absurdist comedy of the issues, pull requests, and commit history of trying to piecemeal delete third party non-FOSS software.
replies(6): >>41861434 #>>41861797 #>>41861800 #>>41862842 #>>41863375 #>>41864656 #
TheCraiggers ◴[] No.41863375[source]
The other thing we lost is that future companies will think again before making their code public. It's already such an incredibly rare thing in the wild, but now companies and their lawyers will see that Winamp was exposed to potentially lawsuitable behavior that wouldn't have come to light had they never opened the code.
replies(4): >>41863868 #>>41864229 #>>41865023 #>>41865025 #
fluoridation ◴[] No.41863868[source]
All of this happened because the company didn't want to open source the code, they wanted to openwash it and get free labor from the open source community. If another company wants to do the same and they decide not to because of this, nothing of value is lost.
replies(1): >>41864088 #
ezekg ◴[] No.41864088[source]
> they wanted to openwash it and get free labor from the open source community.

This is such a ridiculous accusation. Why do discussions about source-available models often turn into accusations of soliciting free labor? Why can't authors just provide access to source code, but reserve some or all of the distribution rights? It's their code, after all. Nobody is forcing 'the open source community' to contribute under the terms set forth; anybody who does contribute does so under their own free will, under the terms set forth by the license.

It doesn't always have to be a binary choice between open source and closed source, nor does it justify further accusations of "openwashing."

replies(7): >>41864186 #>>41864195 #>>41864203 #>>41864260 #>>41864587 #>>41865036 #>>41866336 #
filcuk ◴[] No.41864186[source]
What is the point of 'open source' where you're not even allowed to fork the damn repo?
replies(2): >>41864464 #>>41864940 #
tcfhgj ◴[] No.41864940{3}[source]
In case of security sensitive software, you could verify the security claims.

Look at Apple, they claim E2EE, but don't even allow to verify that defeating the purpose of E2EE entirely (lack of need to trust the provider)

replies(1): >>41864967 #
mort96 ◴[] No.41864967{4}[source]
You can do that with source-available software too, I'm not sure where you think open source comes in?
replies(1): >>41870188 #
1. tcfhgj ◴[] No.41870188{5}[source]
My point is that Open Source isn't necessary for it, aka "open source without forking" is sufficient
replies(1): >>41871561 #
2. mort96 ◴[] No.41871561[source]
There is no such thing as "open source without forking". It's source available.
replies(1): >>41873064 #
3. tcfhgj ◴[] No.41873064[source]
I don't care how you call it.

My comment was a reply to a comment which described it this way.