Your wish is my amusement (I think that's the right phrase). ?node=SilasTheMonk;displaytype=voteview will now show SilasTheMonk his own voting history. I'll probably eventually make I've also made it so that it will show other people their votes that they have cast upon SilasTheMonk's nodes.

Now there should probably be a link to make this easier to get to. I think I'll end up putting it on homenodes (in part because they need some "love" anyway). Then there is the possibility of making it work on root nodes to just show you votes you have cast in that thread.

I won't update Tidings until I'm done fiddling.

Most controversial, is the possibility of allowing one to see summary information about votes that have been cast upon one's nodes (by other monks). This may never come to pass, as obsessing about votes cast against one appears to be detrimental to one's monkly health. If it does come to pass, it might show totals for votes over a period of one or several days (only for previous days), grouped by node.

Feel free to vent your ( suggestions | outrage ) at this ( feature | offensive change ) here, for consideration for future adjustments.

Thanks Tye for your actions and for acknowledging that you were amused.

I have two use-cases.

1. Sometimes I wish to find a node that I remember voting for or against. Obviously there are ways round this, but they all require work on my part. Also I may have voted in a hurry or without thinking very hard about all aspects of the node. Sometimes it can be surprisingly hard to remember details sufficient to search for the node.
2. Sometimes I feel like checking how I voted in the past. Perhaps if I could do this I would be surprised at the results.

Both applications would require being able to go back a long time in history, which maybe is the real problem here.

Okay, I've updated the homenode layout to add a link to the new "vote history" information. It appears as "Your votes" after the new "For this user:" heading.

I've moved all non-user-entered information into the table of items that shows to the right of the monk image (when there is one). There used to be three links outside that table. The "send private /msg" link looked the most like user content since it was at the top of the user content with no visual distinction. It is now after the "For this user:" heading. The "Edit your user info" link is now called "Profile" in the new "Edit your: Profile, Settings" entry. The "Settings" link goes to User Settings. I also made the "Scratchpad:" links on one's own homenode not so verbose.

I think the much more prominent location of "Edit your: Profile" will improve the fairly common situation of people having a hard time finding where to, for example, change their password. And I much prefer having the non-user-entered information much more clearly separated.

I hope most of y'all find this to be an improvement as well.

- tye        

Now we just have to rename "homenode" as User Control Panel. And put up a fake index.php.
--
Online Fortune Cookie Search
Office Space merchandise

tye,

Thanks. I had not replied earlier because I was puzzled by the submit box and I did not want to appear stupid. I think I have worked out that I can scroll through my entire voting history by entering n*100,101 for n=0,1,2,3,.... In this manner I have established that I vote down about 10% of my votes on average.

Suggestions:

• Use ++ and -- instead of +1 and -1. Makes it a bit easier to read. Those rare -1's will stand out more since they'll be more drastically different from the +1's.
• Use alternating classes, like we do for the CB, node lists for users, etc., so that CSS can do something to make it easier to read.
• I think we can put in multiple classes (when separated by spaces) - so maybe using another class for ++ vs -- tr's and td's to allow CSS to highlight (or fade out) ++'s or --'s
For example,

<tr class="odd-row voteup"><td><a href="?node_id=12345">blah</a></td>
<td align="center" class="voteup">++</td>
<td align="right">some-date</td></tr>
<tr class="even-row votedown"><td><a href="?node_id=12346">blah</a></t
+d>
<td align="center" class="votedown">--</td>
<td align="right">some-date</td></tr>
[download]

Opinions?

Years later...

I played around (years ago) with different combinations of '+'s and '-'s and such and settled on '1' for "up" and '-1' for "down" as having the best over-all visual aspects.

I implemented the candy striping.

I did not implement classes for "up" vs "down". Perhaps part of the reason was that old versions of IE choked on space-separated class names. We can probably stop caring about that now.

But I think I'll (instead) eventually add "only show up-votes" and "only show down-votes" inputs and maybe stop forcing people to type in "100,500" for paging (while still allowing similar power).

I also particularly like cmv's idea of teaching super search to allow restricting results based on voting.

- tye        

If it comes to pass, why not only show votes cast since its passing?

Recently Active Threads shows your vote status for any nodes it shows and you can show all recent nodes by clicking the "Clear my last checked flag" button. Not exactly what you want, but a good part of it at least.

Why would you need a voting report? I am not sure that offers value when considering the effort and resources involved.

Well the system must store my votes to stop me from voting twice. So all I was asking was whether it was possible to make that voting history available to the me.

You pretty much answered that question to yourself. Yes, the system stores each vote for a node, which involves the storage of IDs of the monks that voted for it. I guess there isn't an index on that, so gathering a monk's voting history would put some load on the database; and creating an index wouldn't improve neither performance nor storage of PerlMonks, either.

If we were to create such a think, to what end would that be? Tell a use case.

For what purpose?

I was thinking about asking for this again as it is very useful to me, so I'm delighted to see it get implemented.

One improvement I would like to suggest, is to add a "Nodes I voted for" checkbox on Super Search. I can manually search my vote history, but being able to restrict in SS would allow me to find things much faster.

Thanks again!

-Craig