This is not the first time this has been suggested.

As it happens, vroom himself hinted it was possible in this node and both Ovid and tye expressed interest in the replies to it.

For the record, I very much like the idea. I think I would prefer it to read like "Reputation: 144 - 22 = 122" but that's just cosmetics.

-sauoq
"My two cents aren't worth a dime.";

Some work has already been done to support the idea expressed in (tye)Re: Node Tension. But quite a bit more work needs to be done so don't hold your breath. Prior to these changes, the database didn't even have a place to keep track of votes. Now it has a place but it still doesn't keep track (so we'd have to add code to start tracking and then run a really long job to update this field based on all of the votes ever cast so far). Since ar0n has fallen off the face of the Earth and I've got both new responsibilities at "work" and a huge new personal project, very little is being done to maintain the site. I keep trying to get others more involved but that isn't easy (for me or for them), so it is happening, just slowly.

And the display would be more like everything2 does, listing the rep and then optionally listing the total number of votes cast.

        - tye (but my friends rarely call, I'm too busy)

Perhaps I'm just being an old codger, but I don't like this. First off, XP is designed to be a general idea of the community's overall reaction to your node, not a true reflection of its quality or your popularity. Like anything that's unscientifically sampled, there's little point to over-analyzing the results. Sure, you get numbers, but they're not really worth much.

Second, since this would require at least one additional query (if not two, for performance reasons) in order to present each node, I don't see why the minor benefit would outweigh the additional overhead. Sure, the performance might seem negligible for single nodes or smaller threads, but since we've had threads with dozens of messages before, it seems like it would really impact thread view and section views (like The Monastery Gates).

Finally, I can imagine a host of new "whinging" about "OK, which two of you voted me down today?" We've had such witch hunts before and I, for one, would rather not go through them again.

If you want to track the voting progress of your nodes, you can always use some of the classics.

--f

FWIW, I'd be in favour of this change, even if it was only shown to a nodes author, and only on his/her home node posts list to concerve server power.

If the information is already available in the database, then it would suggest that both values are already being accessed now to produced the composite figure we see now. Either that, or one of Mr Codds N-rules (where N increases seemingly exponentially as time->the present) is being violated by storing data derivable from other data.

Reputation: 122 (144++ / 44--)

Hopefully, the computer would do the math better:^)

As for difficulty in implementing, I know that Everything2 employs this for all nodes, so it shouldn't be that difficult. (So says me.)

-- rozallin j. thompson
The Webmistress who doesn't hesitate to use strict;

$|=$_="1g2i1u1l2i4e2n0k",map{print"\7",chop;select$,,$,,$,,$_/7}m{..}g

Pluggin' away
Matt