The source code in this torrent is a clone of the git repo. I don’t know if there are missing branches but it should have the entirety of the master branch history at least.

I have my own backup of the git repo and I downloaded this to compare and make sure it’s not some modified (potentially malicious) copy. The most recent commit on my copy of master was dc94882c9062ab88d3d5de35dcb8731111baaea2 (4 commits behind OP’s copy). I can verify:

• that the history up to that commit is identical in both copies
• after that commit, OP’s copy only has changes to translation files which are functionally insignificant

So this does look to be a legitimate copy of the source code as it appeared on github!

Clarifications:

• This was just a random check, I do not have any reason to be suspicious of OP personally
• I did not check branches other than master (yet?)
• I did not (and cannot) check the validity of anything beyond the git repo
• You don’t have a reason to trust me more than you trust OP… It would be nice if more people independently checked and verified against their own copies.

I will be seeding this for the foreseeable future.

Aha I see what you’re saying. It’s possible that dr CD considered the second part to be crucial, but it doesn’t seem that people who listened to his message felt the same way, myself included. I probably speak for a lot of people when I say we hadn’t realized just how much these platforms are “subsidized” and how much damage that does to the entire market. So that part ended up being associated in our minds with the term enshittification.

“Enshitification” does not mean “I don’t like it”. It is specifically about platforms that start out looking too good to be true and turn to shit when the user base is locked in. The term is generally used for cases where the decline in quality was pre-planned and not due to external factors. Using the same term each time is, in my opinion, an appropriate way to point out just how common this pattern is.

This is great. Proton is getting a lot of testing just based on Steam’s userbase and it is backed by Valve. We also have a lot of data on proton’s performance and potential game-specific fixes in the form of protondb. Making sure that non-Steam launchers can use all that work and information is crucial to guaranteeing the long-term health of linux gaming. Otherwise it is easy to imagine a future where proton is doing great but the other launchers are keep running into problems and are eventually abandoned.

One thing that I am curious is how this handles the AppId. If this AppId is used to figure out which game-specific fixes are needed, then it will have to be known. Do we have a tool/database that figures out the AppId from the game you are launching outside of Steam?

I read through the article but it doesn’t seem to specify the nature of the book. How do we know it’s a “knock off”? It might very well be fanfiction. Copyright law aside, fanfiction can be original and is a valid artistic expression.

This is quite a nuanced issue. The author is claiming that the Rings of Power copied his ideas. Even if the author didn’t have the legal right to publish this book, he might have put original ideas into his work, and the Tolkien Estate should not automatically own these. The copyright owner “should” (within the current legal framework) be able to make you take down your derivative work, but they don’t own it. The article doesn’t specify why the original lawsuit was dismissed.

You can argue that “open source” can mean other things that what the OSI defined it to mean, but the truth of the matter is that almost everyone thinks of the OSI or similar definition when they talk about “open source”. Insisting on using the term this way is deliberately misleading. Even your own links don’t support your argument.

A bit further down in the Wikipedia page is this:

Main article: Open-source software

Generally, open source refers to a computer program in which the source code is available to the general public for use for any (including commercial) purpose, or modification from its original design.

And if you go to the main article, it is apparent that the OSI definition is treated as the de fact definition of open source. I’m not going to quote everything, but here are examples of this:
https://en.wikipedia.org/wiki/Open-source_software#Definitions
https://en.wikipedia.org/wiki/Open-source_software#Open-source_versus_source-available

And from Red Hat, literally the first sentence

Open source is a term that originally referred to open source software (OSS). Open source software is code that is designed to be publicly accessible—anyone can see, modify, and distribute the code as they see fit.

…

What makes software open source?

And if we follow that link:

In actuality, neither free software nor open source software denote anything about cost—both kinds of software can be legally sold or given away.

But the Red Hat page is a bad source anyway because it is written like a short intro and not a formal definition of the concept. Taking a random sentence from it and arguing that it doesn’t mention distribution makes no sense.

Here is a more comprehensive page from Red Hat, that clearly states that they evaluate whether a license is open source based on OSI and the FSF definitions.