Closing Statement: Given the rather unique situation around this RfA, I feel that some words need to be said.
The matter of the IP information coming to light in a less-than-graceful manner, I think it is fair to say, did have an impact on this RfA; however, please note that the phrase "impact" is inherently neutral. As to how the entire situation impacted the RfA, there are two components to consider: the situation of the CU revelation (including Deskana's placing this RfA on hold for 20 hours before I reopened it), and the IP edits themselves.
The community has made it abundantly clear that the way the Checkuser evidence was presented was... sub-optimal. I could possibly comment more on this, but I think to do so would be unproductive, and honestly is no longer relevant to this request for adminship, which is all I'm concerned with at this time. It is fair to say that most people regard the position that Enigmaman was put into, where he was more or less (the full extent of which is open to debate... somewhere else) coerced into revealing his IP, as extremely undesirable (to put it mildly). Some editors supported Enigmaman's candidacy based on his behavior ("grace under fire" being the most succinct descriptor) and felt that he showed the very characteristics that we have come to expect from our administrators. Some editors, however, saw Enigmaman's reluctance to share personal information as an attempt to hide away edits that he wasn't proud of. Without taking sides in that particular debate, I'll like to posit that the two arguments effectively negate each other.
Before the CU information was brought out into the open and Deskana placed the RfA on hold, there was unanimous support for Enigmaman. I don't want to appear flippant, but this is an irrelevant fact. There has been some rumbling about how the pre-situation !voters should perhaps be contacted to get their opinion on the new information brought to light, or to ask them to reaffirm their support for the candidate. However, in this regard and this regard only, this RfA is just like any other; it starts out of the gate just fine, new information is brought into play, and then people begin !voting based on the new evidence. Often, there's little to no comment from the past participants. In this regard and this regard only, the CU situation itself played no role, only the raw information it presented, which (again, in this regard and this regard only) is no different from how information is interjected into the RfA process normally.
As I noted that there are two components to this particular RfA, that leaves us with the IP edits themselves, and that debate is far harder to wash away in quite the same manner.
At best, some editors saw the edits as harmless blowing off of steam, and/or the result of an all-too-easily-done logged out session (something that I must admit has happened to me several times at seemingly random intervals). Other participants saw the edits as a clear attempt to game the system, logging out of his account to specifically distance himself from the "bad behavior". There is far too much contention between these two camps for me to render a judgement on the matter (which one could also argue is outside my purview as a bureaucrat). However, as the IPs were made by the candidate (as opposed to past times where Checkuser information has made abrupt appearances at RfAs and caused equally unfortunate situations), they are perfectly valid reasons for editors to oppose the candidate, and the will of the community in regards to those edits cannot be dismissed.
For the TLDR crowd, here's my summary: the CU situation was regrettable, but as it brought to light valid evidence for the RfA, the direct fallout (the edits) can't be disregarded as readily as any !votes for or against the candidate based directly on the CU situation itself. The edits by the candidate stand, and at this time there is no consensus to promote. EVula // talk // ☯ // 22:36, 13 January 2009 (UTC)[reply]