The system serves to record the arrows you've clicked, therefore this information must be stored somewhere. Someone with access to this this information should be able to determine "what stuff an account upvoted," unless the system has been designed to obfuscate the connections(i.e. accounts & clicked items) at the database level.
Edit: should have clarified that by user I meant a hash of name and password, so it's infeasible to calculate offline.
So yes, PG can see what you voted. I'm pretty sure he won't use it against you though ;-)
This is trivial to deduce from the webserver log alone.
The owner of the server has the power to log each and every access to the site and that includes up and downvotes.
That said I'm pretty sure PG & company can be trusted wrt to such things, HN would die overnight if there ever were any question as to the ethics of the people running it.
There would be much more worrisome things for some people here, imagine being a VC writing here under a pseudonym and being unmasked or someone openly critical of their employer having their posting history revealed.
As others have said, the answer is obvious from the behaviour of the site. But even if it were not, other aspects of the server's configuration would be highly relevant, indeed central to the matter, and the source code is unavailing.
All images and CSS for this site are served by Apache but the actual text/html request is not. However - my point still stands, as the primary request is proxied by Apache and proxy requests, IIRC, are included, or can be configured to be included, in the Apache logs.
update: I am going to have to eat my words here. I have no evidence news.ycombinator.com is proxied by Apache. All the css and images are served by Apache, but they're hosted on a different domain and a different IP at ycombinator.com. I am kind of amazed PG wrote an HTTP server but .. apparently he did. Kudos.
Don't know about votes on comments.
Anyone else notice things like that?
Or maybe I'm going crazy.
Vote something up or down, log out, and come back. You will never see an arrow next to that entry again. Why? Because the intersection of your login and that entry must be storing that fact that you already voted on that.
(I cannot infer from this data alone which way you voted, simply that you did vote.)