Yes, it is so very simple, as long as you do not consider that what you suggest
... will add a layer of exploitable code for which there is no solution.
... may cause bad experiences for a sizeable amount of users.
... could fulfill the previous points without actually being used much, and will certainly do so before being "overused".
Most of the userland/policy issues would be alot less apparent if a server running the restrictions was flagged as private, in which case the code makes no sense since you will achieve exactly the same by doing the small amount of organizing required for a semi-private server. Your suggestion will also reject someone who's built a clutch pedal that pushes a button, and admit someone who uses an xbox controller as a h-shifter.
What you've selected does not need to equal or even be remotely similar to what you are using, the code is pointless. You will achieve exactly as much by running a league or a "club" with the restrictions you want.
What's the point in enforcing things you cannot verify. Anything could send the axis value for the clutch, including a button. The H-shifter uses keys or joystick buttons, anything can send them, including paddles. It's not feasible to check for these things, the result is lots of code that will break as soon as anyone tries to break it.
I don't think LFS would be limited to choosing between a non-system and a poor system. BitTorrent is a great technology for distributing huge files by creating a huge network of unreliable sources, not so good for small files on a small network.
Let's say Scawen adds a file-not-found check to the update distribution system, triggered by the game not being able to find a file (or a file being "OOS") LFS would ask if you'd like to download the file and ask the master server where to find this file. Great for a broken installation. Add multiple source downloading and source broadcasting, dedicated servers (being servers) could notify the master server saying they're ready to serve the following list of files/packages, and/or that these files are available at location x.
Add a custom track to a dedicated server, set it up for distributing the file along with one or more sources on the web and clients could probably download the new content at very decent speeds without ridiculous delays before transfers start. A very generic update / repair system for the game turns into a decent "mod" distribution system with Scavier unable to control the contents and thus not "selling" unlicensed content. The system would still work if the master server was given to the community, if/when service and support is dropped for LFS.
Technology aside, obviously i want more tracks. If i had an amazing car in real life i'd want to drive it at many locations. Same thing.
Basically a re-post, i'd like to see something like different channels, RSS feeds perhaps (very trendy), subscribing to tags (or level / category of misbehaviour, ... something) you want and get some bans applied automatically.
"The more choice available, the more likely people will choose nothing.", kind of fits the current system, IMHO.
A separate "patching exe file" could be distributed by the current update system, it could be designed as a launcher, notifying you if there is an update (and performing the updates), launching the game if there isn't one. In my opinion this is a slightly better design, avoiding the restart for players who want tracks loaded as LFS starts, alerting and updating for players who don't race online very often and keeping the update code separated from LFS itself.
At the start i got surprised by the wind, went off in turn one and drove straight into Tyrion who had also gone off, very sorry about that, i think you were still going backwards when i decided where to go or something :sorry: I know it wasn't a very spectacular incident, just really odd.
Anyway, good race, i hope i wasn't too aggressive with all my attempts to pass in the chicane.
Sounds like you want to filter messages and commands, could make for some tedious verification procedures i think, atleast for the chat messages, and i don't think chat messages should ever be filtered since it'll probably introduce administrative stuff under a false sense of security.
+1 for being able to hear/affect/control commands though.
I don't mean it's a bad idea or that it would take very long, just that i wouldn't use it for the thing i had in mind (and not really fit the target group of users [my target group, if i was to .. etc etc]).
The JSON provider would surely be a neat thing all by itself.
That stuff was just an idea, needs someone to create and serve it. Would probably need to be lfsworld since pubstats is sort of a semi-non-free service now, would be a bit weird if someone else offered a mirror of practically everything for free.