That's very zen of you, but 'no quotes in the username' was never part of the rules. It simply should have been. If you wrote a parser to the current rules, broken as they are, it wouldn't choke on quotes in usernames unless the user had a deliberately disruptive name that was impossible to parse under the rules. But what IS happening, is players with the name 'bob "sam" joe' are breaking parsers. That is the parser's fault.
Nobody is arguing that the rules are flawed, but like I said, 'the rules SHOULD be as such' doesn't mean it's ok to write a parser that breaks in normal usage. For another example, take the current TCP port vulnerability of all source servers (except recently patched TF2 servers). If my server goes down to this attack, it is valve's fault. But, having known about this exploit forever, it's also my fault for not setting up a simple firewall rule to stop it. There are some situations where it can't be stopped without giving up functionality. Again, this is valve's fault. But it doesn't excuse having a firewall that does nothing about it and causes my server to go down to script kiddies constantly. I would still be inept. - Neph On Thu, May 8, 2008 at 12:29 PM, Ronny Schedel <[EMAIL PROTECTED]> wrote: > If you want to interpret something, you need rules, in the real life and > also in the computer world. If you cannot count on rules, you cannot > interpret it with a program. The rule of a player information was: > > "name<id><steamid><team>" > > If Valve breaks this rule, you have to adjust, but there are possibilties > were you cannot adjust, because when everything is allowed, there are no > more rules. No rules, no way to interpret. > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
