[CUViper]

You can protect against SQL injection, but you can't make anyone read the article. The best you could do is make them click the link first.

Just like you can't make anyone read a EULA before clicking "I agree". You can force them to scroll through it, but then you sometimes end up with the comical scroll-all-the-way-down button as well. (Can't remember where I've seen that, but it's more than once.)

[crasshopper]

I agree. But I think the extra level of annoyance is enough of a "sin warning". If I really want to vote something up w/o reading, I'll sin.

But the annoyance of having 25 new tabs would dissuade me enough of the time to make the tweak worthwhile.

As for spammers -- you have to take a separate approach with them. What I'm targeting are not the malicious but the _careless_ rulebreakers.

(I didn't go into this level of detail in the article because I thought it would come up in comments.)

[zck]

Ideally, you'd want the users to read and understand the article, if understandable. However, as this is difficult to implement, opening the page is a the minimum you'd have to do to understand it. If users voting on articles without reading them is a problem, requiring users to at least click on the article would lessen the problem.