Wes' Journal

Subject:	phuck
Time:	11:27 pm.
Mood:	aggravated.
Music:	mason jennings - east of eden.

San Francisco Chronicle, Sunday, June 20, 2004 by Greg Palast

In the 2000 presidential election, 1.9 million Americans cast ballots that no one counted. "Spoiled votes" is the technical term. The pile of ballots left to rot has a distinctly dark hue: About 1 million of them -- half of the rejected ballots -- were cast by African Americans although black voters make up only 12 percent of the electorate.

This year, it could get worse.

These ugly racial statistics are hidden away in the mathematical thickets of the appendices to official reports coming out of the investigation of ballot-box monkey business in Florida from the last go-'round.

How do you spoil 2 million ballots? Not by leaving them out of the fridge too long. A stray mark, a jammed machine, a punch card punched twice will do it. It's easy to lose your vote, especially when some politicians want your vote lost.

While investigating the 2000 ballot count in Florida for BBC Television, I saw firsthand how the spoilage game was played -- with black voters the predetermined losers.

Florida's Gadsden County has the highest percentage of black voters in the state -- and the highest spoilage rate. One in 8 votes cast there in 2000 was never counted. Many voters wrote in "Al Gore." Optical reading machines rejected these because "Al" is a "stray mark."

By contrast, in neighboring Tallahassee, the capital, vote spoilage was nearly zip; every vote counted. The difference? In Tallahassee's white- majority county, voters placed their ballots directly into optical scanners.
If they added a stray mark, they received another ballot with instructions to correct it.

In other words, in the white county, make a mistake and get another ballot; in the black county, make a mistake, your ballot is tossed.

The U.S. Civil Rights Commission looked into the smelly pile of spoiled ballots and concluded that, of the 179,855 ballots invalidated by Florida officials, 53 percent were cast by black voters. In Florida, a black citizen was 10 times as likely to have a vote rejected as a white voter.

But let's not get smug about Florida's Jim Crow spoilage rate. Civil Rights Commissioner Christopher Edley, recently appointed dean of Boalt Hall School of Law at UC Berkeley, took the Florida study nationwide. His team discovered the uncomfortable fact that Florida is typical of the nation.

Philip Klinkner, the statistician working on the Edley investigations, concluded, "It appears that about half of all ballots spoiled in the U.S.A.
-- about 1 million votes -- were cast by nonwhite voters."

This "no count," as the Civil Rights Commission calls it, is no accident. In Florida, for example, I discovered that technicians had warned Gov. Jeb Bush's office well in advance of November 2000 of the racial bend in the
vote- count procedures.

Herein lies the problem. An apartheid vote-counting system is far from politically neutral. Given that more than 90 percent of the black electorate votes Democratic, had all the "spoiled" votes been tallied, Gore would have taken Florida in a walk, not to mention fattening his popular vote total nationwide. It's not surprising that the First Brother's team, informed of impending rejection of black ballots, looked away and whistled.

The ballot-box blackout is not the monopoly of one party. Cook County, Ill., has one of the nation's worst spoilage rates. That's not surprising. Boss Daley's Democratic machine, now his son's, survives by systematic disenfranchisement of Chicago's black vote.

How can we fix it? First, let's shed the convenient excuses for vote spoilage, such as a lack of voter education. One television network stated as fact that Florida's black voters, newly registered and lacking education, had difficulty with their ballots. In other words, blacks are too dumb to vote.

This convenient racist excuse is dead wrong. After that disaster in Gadsden, Fla., public outcry forced the government to change that black county's procedures to match that of white counties. The result: near zero spoilage in the 2002 election. Ballot design, machines and procedure, says statistician Klinkner, control spoilage.

In other words, the vote counters, not the voters, are to blame. Politicians who choose the type of ballot and the method of counting have long fine-tuned the spoilage rate to their liking.

It is about to get worse. The ill-named "Help America Vote Act," signed by President Bush in 2002, is pushing computerization of the ballot box.

California decertified some of Diebold Corp.'s digital ballot boxes in response to fears that hackers could pick our next president. But the known danger of black-box voting is that computers, even with their software secure, are vulnerable to low-tech spoilage games: polls opening late, locked-in votes, votes lost in the ether.

And once again, the history of computer-voting glitches has a decidedly racial bias. Florida's Broward County grandly shifted to touch-screen voting in 2002. In white precincts, all seemed to go well. In black precincts, hundreds of African Americans showed up at polls with machines down and votes that simply disappeared.

Going digital won't fix the problem. Canada and Sweden vote on paper ballots with little spoilage and without suspicious counts.

In America, a simple fix based on paper balloting is resisted because, unfortunately, too many politicians who understand the racial bias in the
vote- spoilage game are its beneficiaries, with little incentive to find those missing 1 million black voters' ballots.

Comments Gimme some lovin.

Subject:	assholes galore
Time:	5:14 pm.
Mood:	bitchy.
Music:	ben harper - i'll rise.

OK, I've had it. I am so burned out at work. WTF is wrong with people? I cannot believe how many fucking prima donnas and drama queens I work with. It's pathetic. Below is just a small example (doesn't really even convey the immense amount of bullshit i've been putting up with the past couple years). The names have been changed to protect the Bitchasses. It's an email thread, so you'll want to start form the bottom and work your way up...

From: Wes
To: *Bitchass Coworker*
Cc: Wes’ Boss
Subject: RE: handheld policy

Hi *Bitchass Coworker*,

I wish I had time to talk about this all day, but I don’t. There are two of us trying to support an office of 50 that feels like an office of 500 because everyone has *something* that makes them special. You *need* your palm. Dayvid *needs* to work on a Mac because he can’t be bothered to learn how to point and click on a windows machine. But wait, he *needs* a windows machine too because Flash is broken on OS X so he needs a machine to sit on his desk for use once a month or so. He also *needs* to control his radio station through some strange tcp port from work. Oh, wait, DJ Jennifer *needs* to spin her station from work too. Allen *needs* to load AOL and god knows what else on his laptop. He also *needs* to get a new phone every 13 days, and expects new software to be loaded and configured each time. Jodell *needs* to be able to load any piece of random software off the internet at any time on our internal network for evalution. Jodell, Allen, and Rajiv *need* to not be bothered to walk over to the QA lab to test and/or evaluate websites or software, so instead they *need* a second computer right at their desk for intermittent use. Marshall *needs* to walk up to the helpdesk and pull Patrick off of whatever he is doing regardless of how many times he is reminded that it is inappropriate and rude to jump ahead of others using the proper methods of contacting support. Lisa K *needs* to have her IE favorites show up horizontally along the browser because having them along the left side just doesn’t work for her, and “seriously impedes her work flow.” Rick *needs* to use the MSN client instead of Trillian because that’s what his wife uses. Mary *needs* to have a better remote access solution, but of course doesn’t want a CHSF laptop (she already has her own) and won’t consider migrating her personal documents and such to a CHSF machine. Rajiv and the kids team *need* no less than FIVE development servers running right now. The moms team adds three more to the mix. This is on top of the 14 other servers I have to maintain, which is on top of all the network infrastructure and security demands on my time. Jodell and Mary *need* unlimited email storage because a WHOPPING 400 MEGABYTES is cramping their style. These are just off the top of my head – I could peruse the HelpDesk archives and get back to you with more gems.

So yeah. Believe you me I’d like to “step up and make an executive decision.” But instead, what do I get to do? I get to spend weeks doing the due diligence to come up with the best solution I can trying to take into consideration technical, financial, and staffing factors, and then when I go for approval I get told that “it’s political suicide” and that “we need to hold hands and have a big group hug about this.” That’s the kind of response I get when I try to make a decision. So sorry if I’ve been too lovey-dovey or soft-handed for you. Guess I’ve spent too many years in Core Services trying to appease the unappeasable.

So from now on, it’s the new Wes. The new Wes will be logical, rational, and firm. The new Wes will say things like “This is the supported list of devices. Talk to your supervisor about purchasing one for you. We will not consider any suggestions you make nor feedback you give, so please don’t offer any.” The new Wes will be even less popular than the old Wes (not an easy task). The new Wes will certainly feel more intellectually and emotionally honest, however. The new Wes will ignore management’s suggestions regarding terms such as “hand-holding,” “tiptoeing,” and “buy-in.” Because as you so astutely point out *Bitchass Coworker*, in the end it’s all bullshit, right?

Actually, never mind. Let’s stick with the old Wes. But we’ll amend the policy. We will alter it to state that Mr. *Bitchass Coworker* gets to choose one non-PocketPC handheld device that will be available to staff. Mr. *Bitchass Coworker* will provide support to staff members who purchase this device, and will have administrative rights to their machines in order to install, configure and maintain the Palm Desktop and Pocketmirror software. It’s a win-win for everybody!

Group hug!
-Wes

p.s. – *Bitchass Coworker*, maybe you can tell me – why do I let this kind of bullshit bother me? Why can’t I just let go of SL’s ridiculous demands and do my job? Oh, and by the way, nice do!!!

From: *Bitchass Coworker*
Sent: Friday, May 28, 2004 4:02 PM
To: Wes
Cc: Wes’ Boss
Subject: RE: handheld policy

It's a shame that Pocketmirror has been causing problems for you guys. And despite the fact that when I initially ran into problems I solved them and sent HelpDesk the steps. It's strange because with my new machine I followed the same steps and haven't had a problem with pocketmirror playing nice with me since. The only real problem I had was trying to be nice about not simply demanding admin access to handle the situation myself - which in both cases was what happened.

I certainly agree that a solution that is easier for you to support makes sense. That's not my argument. The point I have not yet been convinced on is why it is being forced off machines. Lack of support, I understand and accept. I haven't seen a decent argument for forced removal. Show me that an installation of PocketMirror is interfering with Exchange or creating a security issue with Exchange or my specific machine (and I mean documented problems, not the vague hand-waving responses you have been offering).

Or make an executive decision, step up to it and tell me the policy stands and there is no room for argument. I have no choice but to adhere to the policy, though I don't have to like it.

Regarding your comment about buying any device I want as long as I understand it isn't "supported", this is literally unbelievable. I *have* a device that isn't "supported" and I am being forced to stop using that device. Why should I trust you that any device that isn't "official" will not be locked out in a similar manner in the future?

I recommend yet another executive decision. Don't allow any but your officially chosen devices and stick to it. It's obvious that you are following the very typical IT position of constricting user choice to a narrow range of similar installations. It's easier to support from your perspective. Just stop pretending that your users have choices - ever. Continuing this allowed-but-unsupported gray area seems like you are trying to be helpful to individual users. Unfortunately, without clear and firm boundaries, it leaves users to take paths that leaves them out in the cold. This is utterly antithetical to the basic concept of "support".

Pick your one or two official devices and support them *very* well. Again, I may not like it, but I will have no illusions about chosing technology for myself.

From: Wes
Sent: Friday, May 28, 2004 2:21 PM
To: *Bitchass Coworker*
Cc: Wes’ Boss
Subject: RE: handheld policy
Hi *Bitchass Coworker*,

The pocketmirror installation/setup process is a pain, and we have had all kinds of issues with getting pocketmirror to play nice for people, plus having to deal with periodic upgrades to outlook causing issues, etc etc. It is yet another variable for the understaffed systems and support team to worry about and it makes the most sense all the way around to stick with a native server-side solution.

The initial pricing on the MPX will probably be quite high, however if signing up for new service the provider should subsidize a substantial part of it (hopefully). Alternatives to the MPX that we will look at include the Mpx220 (the successor to the mpx200 you linked to) which is due to go on sale in July, and the mpx100 which is a similar model. While we will likely only approve and support one model, there is nothing to prevent you from buying a different one as long as you realize it won’t be “supported” via software on CHSF machines. The flipside of that is that the pocketpc/smartphone setup is very simple, and since everything is server-side, you actually won’t require a connection from your device to your chsf machine for anything. The test unit I’m working with has no activesync association, I take care of everything via 802.11b and the exchange server itself. The upside of all this is that the documentation the HelpDesk will provide for our pocketpc users should apply to just about any device running Windows mobile 2003. There is a chance we will approve both a “pocket pc phone” AND a “smartphone” model. I will keep you informed as our evaluations progress.

As for a pocket pc phone device, we would likely try to stick with HP for our approved device (unless there are some serious issues with the h6310). This keeps the process manageable: ordering (from our net30 vendor cdw), support and maintenance (all support contracts through cdw), inventory, etc. Again, employees are certainly free to purchase any product they wish, it simply can’t be supported by the helpdesk – but again that is not a huge deal considering how simple the server-side syncing setup is and the fact that these devices never have to talk directly to a computer to sync.

As for changing service providers, that may be impossible to avoid. We will do our best to pick a fairly flexible device – in this day and age that probably means a GSM device which will work with just about any carrier other than sprint and Nextel (I’m not sure what verizon’s network is?). I don’t know how subsidizing part of the cost of a more expensive device would work with accounting/inventory, but I imagine it could be worked out – however again we really aren’t going to be able to provide support outside the 2-3 approved devices (and yet again, not so big a deal in the server-syncing model – do I sound like a broken record yet?).

I have no doubt that we will be able to work out a solution that works for you by January. If this is something that recognizably enhances your productivity, then I see no reason that the Foundation would not purchase a device to facilitate that.

-Wes

From: *Bitchass Coworker*
Sent: Friday, May 28, 2004 12:48 PM
To: Wes
Cc: Wes’ Boss
Subject: RE: handheld policy

I do appreciate the amount of consideration you have put into this. I could still se some help in these areas:

- The policy states "If an employee on their team also requires a handheld, the device will be requested and acquired with that team’s budget." While Directors are guaranteed a new handheld, there is no such guarantee for employees. I'm not expecting the foundation to run out and buy a device for everyone. However, can you see that I have a working solution that, from my perspective, is being taken away and I might be forced to dig into my own pocket just to *keep* something that works for me. It feels like being mugged. I realize this is not for you to answer and I will have to take it up when Jeanene gets back. I want you to know the basis for my strong negative reaction.

- Could you give me a hand in understanding how PocketMirror is "problematic and unstable"? I don't seem to be having problems on my end. If I better understand the problems you see on your end, I might be less upset about being forced to give it up.

- Different Models - well, hey if I can get the foundation to pay for a Motorola MPX, I sure wouldn't complain. I asked about different options for two reasons:

1. mobile phone number portability is not yet as smooth as promised and being forced into one device could also mean a forced change in service provider. Keeping or avoiding a particular provider opens up some devices for use.

2. If the Foundation is willing to pay for part of the cost, but not all, employees might be willing to take on the incremental cost of a different (better) model.

I took a look at the Windows Mobile site to see what they offer:

Pocket PC
http://www.microsoft.com/windowsmobile/buyersguide/buy/ppc/americas.mspx

Pocket PC Phone Edition
http://www.microsoft.com/windowsmobile/buyersguide/buy/ppcpe/americas.mspx

Smartphones
http://www.microsoft.com/windowsmobile/buyersguide/buy/sp/americas.mspx

I expect that you wouldn't want to deal with the ASUS or ViewSonic products, but what about the Toshiba or Samsung phones? The least expensive alternative to what I currently have seems to be this Motorola smartphone:

http://www.microsoft.com/windowsmobile/devices/devicesdisplay.aspx?module=deviceDisplay;Smartphone;americas;70

So, if there are makers or models you definitely would not support even though they are Windows Mobile, that would be nice to know so as to avoid looking at those models.

Really, if I can get assurances from Jeanene that I'm not going to have money taken out of my pocket just to keep something that helps with my productivity, I'll be much more enthusiastic about having something that works for you too.

-*Bitchass Coworker*

From: Wes
Sent: Thursday, May 27, 2004 6:49 PM
To: *Bitchass Coworker*
Cc: Wes’ Boss
Subject: RE: handheld policy

Hi *Bitchass Coworker*,

I understand your concern – and part of the reason I pushed for this policy to allow non-supported devices to continue until January is the very fact that it gives us time to evaluate and approve a PocketPC phone or smartphone device. This is functionality that Alexa is looking for, as well as Allen, and I imagine possibly Ed as well. So there will be a cellular-enabled option approved for use before January – we simply don’t have it nailed down just yet. I am going to look at HP’s offering, the h6310 (info on new HP models at http://www.mobilegadgetnews.com/hp.html ) as well as the Motorola MPX (http://www.infosyncworld.com/news/n/4640.html ) and am open to suggestions on other models as well if there are devices you would like considered.

As far as your other questions, the policy also calls for these devices to be purchased not by employees, but by their departments. Pocketmirror is problematic and unstable and will not be allowed on CHSF machines beyond January 1.

We have done our best to find a solution that makes sense in our environment from a technical standpoint, a staffing standpoint, and a cost standpoint. We realize that this will mean change for some people but it is the only way for us to get a sustainable model in place.

-Wes

From: *Bitchass Coworker*
Sent: Thursday, May 27, 2004 4:07 PM
To: Wes
Cc: Wes’ Boss
Subject: RE: handheld policy

Wow. I expected to not be supported, but I didn't expect to be forced to quit using something I've already invested in and works perfectly for me. This policy represents a big step backwards for me. I have a phone integrated with a PDA that has current syncing software support for Outlook. I am facing being forced to purchase a product I don't want that does half of what I need from a handheld device.

Here are some questions I have:
- Are we restricted to HP ipaq devices or can we look at the range of Windows Mobile Devices? I realize smartphones aren't on the table, but toshiba and samsung have devices approximating what I need for a little less than the very expensive smartphones.
- Can I have a better justification of the Jan 2005 forced removal? Does Hotsync and PocketMirror actually interfere with the operation of other devices?

I realize that my negative attitude about this policy is little surprise. I'd like to better understand my options or if I am definitely being forced abandon the device of my choosing for a device not of my choosing.

-*Bitchass Coworker*

From: Wes
Sent: Thursday, May 27, 2004 1:00 PM
To: *Bitchass Coworker*
Subject: handheld policy

Hi *Bitchass Coworker*,

It’s still a work in progress but the doc can be found at \\Core\IT\Documentation\Policies

Let me know if you have any questions!
Thanks,
Wes

1 Comments Gimme some lovin.

LiveJournal for Wes.

View:	User Info.
View:	Friends.
View:	Calendar.
View:	Memories.
You're looking at the latest 20 entries. Missed some entries? Then simply jump back 20 entries.