Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My example was meant as satire, making fun of your "400ft AGL" amendment. And I don't think my example answers questions "without confusion"; the more specific you make the rules, the more cracks and gaps you create for litigious-minded park users to squeeze through.

As far as this applies to moderation: having simple rules, with an overarching "Use your common sense" rule, seems more practical than trying to make rules that cover all cases. Of course, that requires moderators that possess common sense.



> litigious-minded park users to squeeze through

Again, new/different goal post, this wasn’t the question being asked. Litigious-minded people often aren’t arguing the rule was unclear, sometimes they argue the rule is wrong or the intent was misguided or the rule was clear but didn’t cover their needs. It’s a valuable question in real world parks, but not what we were talking about here, not relevant to the ‘no vehicles in the park’ survey or Dan’s blog post.

> My example was meant as satire, making fun of your “400ft AGL” amendment.

I don’t get it, could you explain it? I don’t see how doing the opposite of what I suggested and adding a bunch of new rules makes fun of what I offered. That explanation just makes it seem like you didn’t quite understand my suggestion.

> I don’t think my example answers questions “without confusion”

You should go back through the survey again and just see for yourself. You partially defined what “vehicle” means, and you partially defined what “in the park” means, and you carved out some meaningful exceptions. This fixes a bunch of the actual trick questions in the survey that depend on not having defined what those words mean. If your point is that the survey author could have asked other different trick questions, then you’re implicitly acknowledging that your rule set improved the clarity of the rule ‘no vehicles in the park’.

> the more specific you make the rules, the more cracks and gaps you create

Are you suggesting that the size of the gaps doesn’t matter and that the coverage of the rule doesn’t matter either? Number of cracks is independent of overall rule clarity. The question is about coverage, about rule clarity. It doesn’t matter if you create more cracks and gaps, if they’re smaller, if the sum-total surface area of the cracks is smaller than what you had before, and if the clear and unambiguous coverage of the rule gets larger.

That said, I don’t think it’s even true that you’re creating more gaps. Think of it like this: every separate individual usage of a ‘vehicle in the park’ is a crack or potential exception to the rule. “no vehicles in the park” is not well defined, and it leaves a HUGE number of individual cracks. See it not as one large gap but thousands or millions of unique use-cases. Adding specificity to “no vehicles in the park” can limit a lot of the potential use-cases without adding any new ones. This is what adding the single word “motor” does - it rules out all motor vehicles without adding any new vehicles, because the prior rule was all vehicles. Adding “motor” doesn’t add any cracks or gaps, it removes thousands of otherwise ambiguous cases.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: