#121 User preferences comments modifiers; need public and private

[Degrees]

Here is the problem I am attempting to solve:

One particular user irritates the heck out of me by his
(lack of decent) spelling and grammar. Several other
people mentioned to him their similar irritation, and
his response was "if you don't like it, don't read my
posts." I can 100% agree with this concept, and
actually have a way of doing that. I mark him as a
Foe, and in my account preferences, comments, People
Modifier, I can assign a -6 score to Foes.

The only thing that bugs me about this is that my
choice to mark him as a Foe is rather arbitrary, and
that its effect spills over into the People Modifier:
Foes of Friends.

Just because my personal preference is to not read the
guy, doesn't mean that other people should be
influenced by my choice. Additionally, telling the guy
(and the world) that he has made a foe may
unnecessarily embarass him.

Here is my suggested solution to this problem:

Alter the Relationship to have five values - Friend
(Public), Friend (Private), Neutral, Foe (Private), and
Foe (Public). The public and neutral relationships do
not change in any way from the way they work now. What
does change is the page rendering code when looking up
modifiers. When computing the score of a post - if the
poster is a friend or foe of *me*, all five
relationship values matter. But when computing the
score of a post - if the poster is not in my direct
friend or foe list, only the original three
relationship values (neutral and public) matter (just
as it always has).

As you might expect, Friend (Private) and Foe (Private)
would not be reported on a user's *public* relationship
page.

This way, I would mark the guy that annoys me as a
private foe. I wouldn't see his posts, but other
people still could, without score modifiers. The guy
doesn't have to get all butt-hurt that he has been
marked a foe - because he doesn't know.

Of course, if I want to embarass the guy, I can still
choose to change the relationship to Foe (Public).

Anyway, its a thought. If it is easy to do, great. If
it significantly consumes CPU without really changing
anything, then never mind.