the current method of writing in:
"Package Handler,
Customer was an asshat...you know what to do"
was starting to get noticed

CDMA is shorthand for CDMA2000 of course...so the comparison still stands

Why is it that CDMA is always left by the wayside? It seems as though all new, cool phones always end up GSM...and never go CDMA. Is it really in the minority so much that vendors pass it by? ....or is it that I need to change my provider?

John Hammond: "All major theme parks have had delays. When they opened Disneyland in 1956, nothing worked!"

Dr. Ian Malcolm: "But, John. If the Pirates of the Caribbean breaks down, the pirates don't eat the tourists."

The problems that exist in the world today cannot be solved by the level of thinking that created them. - Albert Einstein As someone who played with their parent's chemistry set as a kid, and grew up fascinated by science and technology...I hope this works out

will Windows Marketplace be the one to get it right?

Was anyone else reminded of Carmageddon

Denmark does have a similar class action lawsuit type civil case. It's called Gruppesogsmal (sic)

This is why there are confidentiality agreements, data protection and security procedures defined in the contract with large fines if they are not followed.

Neither Gentoo nor Ubuntu is on the certified products list....and therefore DoD won't/can't use it. Welcome to the Government, the land of red tape. http://www.niap-ccevs.org/cc-scheme/vpl/

He's not kidding. The waiver is called a Plan of Action and Milestone (POA&M) if he's going by the DoD/DISA IA vulnerabilities and their vulnerability management system. This is the only way they can actually set maintenance schedules. A lot of the admins submit these 'waivers' with a plan of action which includes quarterly or monthly patch days, otherwise they'd have to run patches every other day, possibly breaking their applications and services. It's a lot easier to bulk patch and test the app/service once a month or quarter than every day. The frequency of DoD IA notices is so high that this is the only manageable solution.

I don't think your summary does Google Voice justice. Within their database they have phone numbers with the area code 406 dynamically assigned to a Google voice subscriber and each of that subscriber's contacts. This means that if you call from your phone which is registered under Google voice the 406-xxx-xxxx that corresponds with a certain person within your contact list, you will be in turn calling that person transparently, and they will see on their caller id your GV number not the actual number of the phone your dialing from. This gets around the whole "Hey everybody! I have a new phone number, don't use the old one" problem as well as the manual proxy that is calling your own GV number from your phone then putting in the number of the person you want to call. Since the 406 number is personal to you and is dependent on you and who you are calling, Google only needs to buy enough 406 numbers from a Telco provider to fulfill the person has the largest contact list. It is hard to describe but, in effect, they have reduced the need to know phone numbers because they do it all in the background transparently, as well as the manual proxy annoyance. The downside is that it is not fully implemented. To see one of your contact's own 406 number, you have to SMS them from your GV number and they need to reply back. There is a rumor that Google may be automating this soon. If you don't think about the security concerns, Google's got a winner here

Well Ohio did call dibs and they've got the documentation to prove it