Angius

Since this seems to be the closest thing to a megathread, lemme crosspost my mod provenance suggestion. tl;dr: there are ways to guarantee that the mod files uploaded to the moddb have been built from the exact specific code in a public repository. One of the reasons the whole ConfigLib conundrum feels so malicious, is that the "anticheat" code did not exist in the public repository. This time it was something somewhat benign, yes, but what's stopping someone from uploading a zipbomb? Some sort of provenance system is, IMHO, necessary.

You at least got a warning before. I was suddenly banned without as much as a warning, and I still have no clue what for

Mod DB should support mod provenance, that is a way to attest that the mod we download is build from the exact code on Github/Gitab/Codeberg/whatever. A build function should exist that builds the code and uploads the built binaries to the database, with some integrity checks along the way. That way, it can be guaranteed that the code the mod author has on their Git repo is what the player actually runs, removing the risk of the author uploading binaries built from code different to what they claim it is. cough cough ConfigLib At the same time, I'm not arguing for it to be required, just give the mods that have a proven provenance some badge or something, and let us filter for it. Prior art: JSR.io, NuGet.org

Tyron is the server owner, so...

Now mods on the Discord are deleting messages lmao Good going guys, protect the malicious modder and stay silent, ignoring and silencing the discussion about issues like that has historically never gone badly, right?