Friday, February 11, 2011

CSM, the out of pod experience.

As mentioned yesterday, I don't like much that the CSM members have to divulge their meatspace ID to the whole intarwebs, starting with the rabid EVE fanbase.

My argument is simple, CSM is not a job, you get in the seat on a part-time, extracurricular basis, and on the merits of your in-game persona (in the loosest meaning of in-game, including OOC/meta stuff, obviously).
Furthermore, nobody expects you to shed your in-game affiliations for the duration of your CSM mandate (contrary to what CCP employees are supposed to do).
In short, you're elected as a player and mainly for who you are in (and around) the game.

Thus, I don't see any benefits for the community or for the election process in divulging the CSM candidates/members out of game ID to the general public, and since the potential for trouble is obvious, it is a no-brainer that it should be up to the individual CSM delegates to decide whether they feel comfortable getting out of the closet in that way.

Some may object that the CSM role is a public one, and it is likely that any CSM delegate's face (and other body parts) could end up plastered across the intarwebs as a result of partaking in meetings, fanfest events and other photo shoots or alcohol-fueled embarrassing tapes.
Maybe so, but then again, if all there is to tie to these images is a spacenerd nickname, and one is not a public figure in his/her non-EVE activities, the odds are pretty good some separation can be maintained (if one chooses to).

CCP will still know who CSM delegates are, on account of their filling the plane and hotel tickets reservations, and they can therefore ensure nobody is entering under three different nicknames into the election.

As far as I can tell, the current rule only prevents people who are mildly wary of being stalked and harassed by mouthbreathers over in-game grudges from running for CSM, with no discernable upside for CCP, the CSM delegates or the community at large.

Am I missing something obvious ?

No comments:

Post a Comment