Yes its paraphrased obviously. But the concept is unchanged. You should never give up options for protection from something that almost never happens.
Modding in factorio involves human readable lua files that are not compiled prior to distribution. Anyone can take the time to read what the mod does before using it. As soon as one person has a legit problem no one will ever trust that modder again. Problems are almost self solving without any restrictions needed.
Create some way for Inter-Process-Communication
Re: Create some way for Inter-Process-Communication
I strongly disagree on this one. It's as saying "why lock your car when there is so little chance for it to be stolen" ?seronis wrote:You should never give up options for protection from something that almost never happens.
Statistically, if they don't sandbox, there WILL be some time when shit will happen. Consider it as an insurance you only get hoping you won't have to use it.
Koub - Please consider English is not my native language.
Re: Create some way for Inter-Process-Communication
Anyone can. Sure. So you suggest that either everyone becomes knowledgeable in Lua and takes the time to untangle every function and audit every line of code in a mod before using it or wait for an expert to do so and write a review, "yep, this mod won't delete your files and is safe to use." Who is actually going to do this?seronis wrote:Modding in factorio involves human readable lua files that are not compiled prior to distribution. Anyone can take the time to read what the mod does before using it.
Right. As soon as a mod erases a couple of hard disks or steals passwords etc. the victims will just complain about it on the forums so people will stop using the mod and the problem fixes itself. Terrific.seronis wrote:As soon as one person has a legit problem no one will ever trust that modder again. Problems are almost self solving without any restrictions needed.
Automatic Belt (and pipe) Planner—Automate yet another aspect of constructing your factory!
Re: Create some way for Inter-Process-Communication
The very VERY few (only 2 or 3 that I can remember) mods in minecraft and sims3 that did questionable things got called out for it almost immediately. You dont need everyone to be knowledgable. There will always be 'just enough' curious others trying to learn from someones code that it will be found. Worth noting that those are both 2 games where the code IS COMPILED and source isnt required to be supplied without being decompiled first.prg wrote:. So you suggest that either everyone becomes knowledgeable in Lua
So no. Sandboxing is not helpful. At all. The actual history of what has happened in modding proves this. And the hindrance is not worth the prevention of those few events. They get found out and dealt with.
Re: Create some way for Inter-Process-Communication
The standard game is not getting un-sandboxed.
I was thinking about it and had the idea that we might provide a flag that mods could use or perhaps a startup flag that would be required that enabled all of the unsafe and non-deterministic methods that aren't normally available. It would at the same time disable multiplayer and replays but this is all just ideas - I'm not sure if it would be worth the time at this point.
I was thinking about it and had the idea that we might provide a flag that mods could use or perhaps a startup flag that would be required that enabled all of the unsafe and non-deterministic methods that aren't normally available. It would at the same time disable multiplayer and replays but this is all just ideas - I'm not sure if it would be worth the time at this point.
If you want to get ahold of me I'm almost always on Discord.
Re: Create some way for Inter-Process-Communication
The discussion has derived from inter-process communication to pro/against sandboxing argument.
I consider the original topic answered, so I'll lock this topic.
[Koub] Topic locked
I consider the original topic answered, so I'll lock this topic.
[Koub] Topic locked
Koub - Please consider English is not my native language.