Yeah, I noticed that the user names are enclosed in different classes, depending on where they are.  Some you would want to show, like on the profile page, but the one's we really want to ignore are articles and comments.

I also noticed that user names in comments don't have a specific cascaded class definition but are instead displayed using to the hyperlink's default style.  The only thing that seems to distinguish it is the "/user/uid:" portion of the HREF attribute.  That's probably sufficient for comments, because then you can simply block the whole DIV containing that comment and anything in the DL tag that follows it -- or not, because blocking the DL tag along with its parent comment would block comments from users that you don't intend to block.

Also, if the script see's the user name you want to block, it can't simply block the entire

that contains it because it might be someone else simply referring to that user.

And I'm not even sure that simply looking for the "/user/uid:" in a hyperlink is foolproof.  For instance, if I write a comment containing a Ken's user name "Hugh Everett" as a link to his profile (although I can't imagine why I would ever want to do that), then the script could block my comment unintentionally.

However, looking for the

</b> on <A CLASS="light"...

that immediately follows the name would probably do the trick.

Articles are a little easier because all you have to block is the DIV containing the user name that you want to block if that DIV is of class "border_shim" and whether it's on the site's front page or on the forum list.

Those are really the only places I'm concerned about.  If I can block Ken's/Hugh's comments and articles from being listed on just those pages, I won't care about his profile page or anywhere else his name might appear.

by EveningStarNM on 12/11/2009 01:02:28 PM EST

[ Parent ]