comment on

... Alternately, one could just refer to the posts themselves ... And isn't that the important thing, the comment of the post-not the author? ...

Yes it is the important thing :)

Examine what is said, not who speaks." -- from BrowserUK's sig Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

But the complain seems to be that its harder to examine what is said when you're dealing with an amorphous blob that can't be differentiated from other instances of the same amorphous blob.

So the remedy, of having something like said the Anonymous Monk in auditorium seat East42 with all the accuracy of ip+browser (or currently+branded+browser+session, or ip+browser+thread and without revealing either ip or browser), seems to make it easier to differentiate the blob within a thread, so folks can keep track of which Anonymous in the auditorium they're discussing with

I like that, auditorium seat, in the form of a cookie (like login cookie except no identifying information, just a seat number based on some crypto operation )

In reply to Re^2: Assigning unique identifiers within a discussion thread to each distinct anonymous commenter (auditorium seat) by Anonymous Monk
in thread Assigning unique identifiers within a discussion thread to each distinct anonymous commenter by PopeFelix

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks