Earlier quoted context omitted.
This person is really confused about licenses and copyright. > Please note that this code is property of Valve-Software and any contributions that you make are considered a donation into the public domain.
Legitimately seems like a GPT-tier confusion. Just put all the somewhat-relevant words in a syntactically correct configuration and call it done.
Leaked source – CS:GO
51–60 of 117 posts
Re: Leaked source – CS:GO
#52Earlier quoted context omitted.
Anyone can start an organisation and define "open source" the way they want. The common way it is understood should probably be named "libre source" or something, because it means more than that the source is just out in the open.
That’s no different to saying “You can define black as white.” That’s true but nobody is going to pay attention to you if you do.
Re: Leaked source – CS:GO
#53Earlier quoted context omitted.
This person is really confused about licenses and copyright. > Please note that this code is property of Valve-Software and any contributions that you make are considered a donation into the public domain.
This is a common 'copyright infringement NOT intended ALL rights belong to X' type of widespread misunderstanding of how copyright actually works, and it's why I'm convinced that if most people understood copyright they would think it was absurd.
Re: Leaked source – CS:GO
#54Earlier quoted context omitted.
I mean, you're not saying that this project is "closed source" either, right? So what is it if not "open source" on the scale between closed and open? "Half-open source"? "Leaked source" only refers to the way the source has initially began to be distributed, not whether it's open/closed right now.
The middle ground is "source available", although that usually means source made available by the copyright holder under terms that don't meet the Open Source/Free Software definitions. I think just "leaked source" is the best terminology here.
Re: Leaked source – CS:GO
#55Re: Leaked source – CS:GO
#56Earlier quoted context omitted.
That’s no different to saying “You can define black as white.” That’s true but nobody is going to pay attention to you if you do.
The analogy falls flat because the words that make "open source" both already have meanings that make the OSI definition confusing to say the least.
Re: Leaked source – CS:GO
#57This world view is quite perplexing, to be frank. On one hand, he urges potential users to switch to Linux, emphasizing its cost-free nature and the freedom it offers in terms of code and game direction. However, on the other hand, the code being used is stolen and leaked, thus infringing on the original creator's copyright. Additionally, the repository's license claims that all contributions are considered public do…
Re: Leaked source – CS:GO
#58Re: Leaked source – CS:GO
#59The title says "open source" but then goes on to talk about leaked source. Unless a clean room RE was done, I don't think this can be called "open source". I want the thing in the title to exist, of course, but at best this seems like the sort of thing that won't be legal and free until we're all dead. If anyone was interested in making a properly free CS:GO, they probably should avoid reading this post as it seems t…
Licences, to many people, are the domain of really fucking boring crusty nerds.
Re: Leaked source – CS:GO
#60Earlier quoted context omitted.
Legitimately seems like a GPT-tier confusion. Just put all the somewhat-relevant words in a syntactically correct configuration and call it done.
Heh, it's like all those YouTube videos where someone uploads a song and the uploader puts "No copyright infringement intended" in the text description, sometimes with five or six exclamation marks just to really make sure they avoid the takedown.