Thursday 27 October 2005

The Nokia N90, $900 Camera Phone Reviewed

The Nokia N90, $900 Camera Phone Reviewed: "This phone is a travesty.
(Score:5, Funny)
by generic-man (33649) * Alter Relationship on Wednesday October 26, @08:12AM (#13879875)
(http://weill.org/ | Last Journal: Saturday October 01, @01:18PM)

I will absolutely not buy this so-called 'phone.' For $900 I can get:

1. A Nintendo DS on which to play games
2. A small 4-megapixel camera with which to take photos
3. An Archos PXF-78-MNpL-1 Personal Media Player Jukebox that will extract the photos, sew them into a DivX movie, synchronize with all seven of my Linux boxen, and perform many other tasks that an iPod cannot do
4. A free cellular phone from any carrier I wish
5. A portable DVD player on which I will watch movies
6. A large backpack to haul this around

As is common in these discussions, I believe I speak for everyone in this forum when I state that because I do not want this product, none of you should ever even consider purchasing it.

--
For more information, click here."

================
http://www.mobileburn.com/review.jsp?Id=1689
real review, hey

================

Re:This phone is a travesty.
(Score:5, Funny)
by killmenow (184444) Alter Relationship on Wednesday October 26, @09:08AM (#13880214)
(http://slashdot.org/)
I will absolutely not buy this so-called "phone." For $900 I can get:

1. Hookers
2. Blow

I already have a digital camera and a cellphone and if my digital camera's batteries die after I photograph myself with the hooker, I can still use my phone to call my dealer for blow.
--
Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony.
============


Japanese cell phones
(Score:5, Informative)
by Bueller_007 (535588) Alter Relationship < > on Wednesday October 26, @08:28AM (#13879993)
The "West" is so far behind in mobile phone technology. For only $200, I can get this phone in Japan:
http://www.vodafone.jp/english/products/model_3G/v 903t/index.html [vodafone.jp]

It's completely bilingual (although I don't think it has predictive text in English mode), has a 2 MB camera, global roaming (and global GPS navigation (although only five or six countries are available at the moment)), can take video calls, communicate via Bluetooth or IR, read QR codes (very convenient in Japan). The Nokia N90 can't even vibrate when it's in silent mode. WTF? That's pretty much par for the course over here. And the Nokia is $700 more? If you can switch this phone to work on a Verizon account back home, it's almost worthwhile to buy a ticket to Japan, buy the phone and then fly back.

Even the free phones you get with a new account over here have AT LEAST a 1 MB camera. Some have 2. Some of the newer Sharp phones even have built-in optical zoom.

Vodafone is generally looked down upon by the Japanese people. NTT Docomo probably have even better phones available.
--
"Live your beliefs and you can turn the world around." - Henry David Thoreau


#5 TSA Airport Security =HOAX; re:Blizzard Made Me Change My Name

Blizzard Made Me Change My Name: "Cmdrtaco, you think YOU feel 'violated?'
(Score:5, Insightful)
by dpbsmith (263124) Alter Relationship on Wednesday October 26, @10:43AM (#13881131)
(http://world.std.com/~dpbsmith)
How did I feel when the clerk at the airline check-in desk told me that I was on the 'no fly' list? He then corrected himself and said someone with my _name_ was on the 'no fly' list.

You have been using your online name for ten years. I have been using 'Daniel P. Smith' for, uh, my whole life.

The airline ticket clerk takes my driver's license away from me, along with the driver's licenses of my wife, son, and daughter-in law, and he and another airline ticket clerk took them to some inner sanctum and did something mysterious, and after about five minutes came back and said we could be issued boarding passes.

On contacting the TSA I'm told that I can submit a form called a PVIF [tsa.gov] along with notarized copies of three forms of identification (driver's license, birth certificate, passport, etc.). This will accomplish... well, it's not exactly clear what it will accomplish. 'Please understand that the TSA clearance process will not remove a name from the Watch Lists.'

So what does it do? 'Instead this process distinguishes passengers from persons who are in fact on the Watch Lists by placing their names and identifying information in a cleared portion of the Lists.'

And what does THAT do? Well, here's what it doesn't do: 'Clearance by TSA may not eliminate the need to go to the ticket counter in order to check-in. While TSA cannot ensure that this procedure will relieve all delays, we hope it will facilitate a more efficient check-in process for you.'

You're upset because some online game doesn't like the name you've chosen for yourself? Please.

_I'm_ upset because my government doesn't like the name I was born with. And, yes, I'm upset because I can see the look" in the clerk's eyes... and in the eyes of the notary at my local bank stamping the notarized copies (yes, of course I caved... what do you think I am, someone with principles?)... thinking "Well, he's probably OK but, gee, he's on the TSA's list..."

I think I'm going to get a court order to change my surname to Cmdrtaco. Hopefully there aren't too many people on the no-fly list named Daniel P. Cmrdtaco.

--

Elinor Goulding Smith's Great Big Messy Book, ba [std.com]
=========

===========
*****
Hell, Congress made me change mine this year!
(Score:5, Informative)
by ankhank (756164) * Alter Relationship on Wednesday October 26, @11:30AM (#13881718)
(Last Journal: Sunday January 23, @11:06PM)
I've used my family's "nickname" -- rather than a long cumbersome Southern three-part name with a Roman numeral trailing it -- since about age five. Nothing in the world except my Social Security card and birth certificate had the long form.

Until this year when the PeopleSoft company took over my employer's staff database, and had to change everyone's name on record (they say because it has to match the Social Security database).

So Blue Cross simply terminated the health record file (close to three decades worth of records) attached to the name I've been using, discarded it, and created a new file under the Social Security file name -- with of course the same SSI number.

So they bounced a bunch of medical bills reporting "that subscriber terminated his health care coverage." Although they claim they do use the SSI as their internal identifier so they shouldn't have thrown the files away. And they told my medical practitioner's office to discard the old files as well -- and they did, the pea-brains -- and opened new empty files for the new SSI-official name Congress now insists I use.

Keep your own medical history as I have done -- else I'd have no health records.

You worry about an online game? Trying to get your life back after your identity is stolen by your government. Or maybe it's not the government, but PeopleSoft claims that's the reason they did it. Or maybe it's Blue Cross, but they blame PeopleSoft.

It's happened to other people I know too -- blindsided them as well when their files went away.

War of Worldcraft, I think this is.
==========
******************************************

Only people with REAL power need to be accountable
(Score:5, Insightful)
by RomulusNR (29439) Alter Relationship on Wednesday October 26, @01:48PM (#13883056)
(http://www.keithtyler.com/)
Nobody ever thinks that *they* need to be held accountable for how their actions affect others. It's always *other people*, people with "real power", who need to be challengeable or redressable.

Accountability is an inconvenience, and a threat to the target's power. Few people *want* to be accountable; it means that you can be penalized for doing something wrong, and people always do wrong things, so its inevitable that accountability will lead to penalty of some sort (however minor); the fear is that an irrationally vigorous redressing will over-penalize you (and this does happen).

The point is... Everyone says that those with power need to be accountable for it, except when it comes to the power *they themselves* hold. GMs aren't powerful -- not *really* powerful -- so they don't see any need to be accountable. Of course, they *do* have *some* power, but it's never "enough" to require accountability. (I'm using GM here as a relevant example, but it's hardly the only valid one -- insert the term of the agent of power you most love to hate here -- site admins, police, CSRs, etc.)

There's an annoying norm of disproportionate contraries, particularly in the online world. A GM making a bad, misapplied, or abused decision on another player will retort to complaints with "it's only game"; in the grander scheme of things (and there is *always* a grander scheme of things, in everything, which most people forget when they apply this adage) it "doesn't really matter". Well, if the actions of a GM aren't such a big deal, then accountability of the GM shouldn't be a big deal, either. But clearly, it *is* such a big deal, to the GM. The use of their power is not important -- but the fear over the questioning of that use *is*.

There's always a touchy-feely reason not to challenge the admins, either. They're volunteers, or they work really hard, or they are really good people, or they "could have done worse". All of these are provided as reasons why the individual should not be able to challenge the people who exert power over them. What this implies, of course, is that being a volunteer, or working hard, or being lenient (while still being wrong) all become licenses to abuse or misapply power.

I guess I can't entirely blame the unfortunate empowered individuals for treating accountability as a personal insult or unfair restriction on them; they for whatever reason don't recognize that they have power and that any power should come with appropriately proportional checks on it. Of course, the people above them, both within the paradigm and within society, are always looking to avoid accountability as well. Sometimes the people succeed in compelling accountability upon them; but sometimes they don't. And rarely does it work in your favor to wilfully invite accountability. You have to do it due to principle and selfless benevolence, not entitlement and self-aggrandizement.

What really is disappointing is that even intelligent geeks can't be expected to believe in the universal application of principles like accountability of power. They're just as susceptible to the allure of power, however minor, as the common masses. So much for geeks inheriting the earth.
--
Terrorists can attack freedom, but only Congress can destroy it.
*******************



The Rovers That Just Won't Quit

The Rovers That Just Won't Quit


2 years and still no postcard!
(Score:5, Funny)
by Viol8 (599362) Alter Relationship on Wednesday October 26, @10:55AM (#13881312)
I dunno , some robots , just no consideration for those left on earth.
===============

Read this book.
(Score:5, Informative)
by grub (11606) Alter Relationship on Wednesday October 26, @10:46AM (#13881174)
(http://www.grub.net/ | Last Journal: Friday October 21, @09:40PM)

I read Roving Mars [amazon.ca] a few months ago. It was written by Steven Squyres, the principal investigator for the Mars missions. A very good book with some behind the scenes scoop on the politics and squabbling involved in getting these things build and sent. Highly recommended.
--
Landmark Forum [rickross.com] is a cult.

Does Visual Studio Rot the Brain?

Does Visual Studio Rot the Brain?






====================
Re:Microsoft DEVELOPER tools are good
(Score:5, Insightful)
by captain_craptacular (580116) Alter Relationship on Wednesday October 26, @05:40PM (#13884902)
If anyone but MS made Visual Studio I have 0 doubt that everyone on /. would be singing it's praises right now. VS is IMHO if not the best, then without of a doubt one of the top 2 IDE's in existance right now and has been for quite some time. Even in the much maligned VB.net you aren't forced to do anything with the GUI.

The authors gripes about not being able to see the code in it's entirety are complete BS. All you have to do is expand the conveniently hidden setup and autogenerated code and you can read to your hearts content. The default is to hide most of that code because frankly, it's insignificant. Do you really need to see the declarations for the 250 objects on your form? Do you really need to see the wrappers around database drivers? No and No.

Are you going to claim that a mechanic who uses the computer in your car to tell him you have a bad sparkplug is a bad mechanic? Or are you going to be quietly grateful that he was able to fix your problem for $50 in 1/2 an hour instead of the old school "hard core" method of slowly replacing part after part until you figure out which was the broken one, which costs you lots of time and money?
--
They who would give up an essential liberty for temporary security, deserve neither liberty nor security

==========
Exactly; if a person needs an IDE in order to understand the code, then that person is not a programmer, they are an IDE operator.

IDEs can definitely help you understand the code faster, however. Take Eclipse, for example:

* If I see a class name I don't recognize, I can control-click to go to the class definition. If the source is not attached, I at least get a view of all the method signatures.
* If my code invokes a method I don't recognize, I can hover the mouse over the method and the Javadoc description of the method will pop up, telling me what the method does, what the arguments are for, and what the return value is.
* If I'm navigating through someone else's class hierarchy, by selecting the class name and pressing Ctrl+T I can see all interfaces this class implements, and its superclasses from which it inherits methods. If I hit Ctrl+T again, I can see all classes that inherit from this class, and what classes inherit from them, etc.
* If I hot Ctrl+O, I can see all the methods callable from my current cursor position. I can also see all variables within scope.



Granted, I could understand the code without an IDE, but it's going to take me longer. I don't know if you were being sarcastic (I'm a little tired, so not so mentally keen), but people who use IDEs should not be written off as the equivalent of assembly line operators...

- shadowmatter
============
Eclipse has even more nice/brain-rotting features than Visual Studio, mostly because Java is a much easier language for an IDE to understand than C++ because there is no preprocessor. In fact Eclipse makes Visual Studio look like not much more than Notepad with a GUI builder. It even detects compile errors and warnings as you type. So it totally encourages that bottom-up programming style. Is it also evil? Developing Java in Eclipse is so much faster than developing it by hand, and Eclipse provides tools to "clean up" what you did by refactoring, tools to automatically generate stubs for those undefined classes/methods that you're calling to get rid of those nasty red underlines representing compile errors, etc. I would say it's just much easier to make an IDE smart if it knows what you're doing, i.e. you declare stuff before using it.
==========
.../... Nobody denies that Visual Studio has features that are useful. What is under scrutiny here is the fact that it also has features, and there's some crossover, that enable complete dimwits to produce the kind of results management is looking for in the time they are looking for, leaving those who can actually design and develop software looking incompetent. The PHB doesn't care that the real hacker's design is far superior and the implementation robust, it took 4 weeks longer (because they understood the entire problem and handled all the cases) and dammit the client wants it NOW, who cares that its crap - that's just a small detail that can be fixed later - potentially for more money. This then forms a culture that a particular breed of "programmer" - namely those that can only use Microsoft tools and work solely on the Microsoft platform - are better and that Microsoft solutions are better; not because they are but simply because more quality people and alternative solutions are shut down before their full benefits are realised, because of the impetus on getting a quick buck and must have things NOW.

==============


Evolution of Development
(Score:5, Interesting)
by TheNetAvenger (624455) Alter Relationship on Wednesday October 26, @06:38PM (#13885327)
Whether the 'old' timers (myself being one) like the abstraction of low level coding and what is becoming mainstream, this is an evolution of development.

Visual Basic back in 1992 was in of itself a massive advance for this type of programming and programming understanding. Look at all the 1000s of VB applications from this time period by people that truly had very little coding experience.

However, some of the VB programs from this time were quite effective.

I think the biggest injustice to programming and the programming community as a whole, is the lack of UI guidelines, and understanding usability and User Interaction and User Flow.

How many times have you grabbed a GOOD program, with brillant LOW LEVEL coded features, but the interface to the application work about as well as a broken pay phone.

So sure VS can remove the user from 'low level coding', but this is NOT always a bad thing.

As development EVOLVES, there is NO REASON with the AI in the development tools and the AI in the code produced by these development tools should not be used. Why should a person in the 21st century truly have to fully understand memory allocation, advanced recursion, or even see program past advanced event handlers, as that is what programs ARE - event handlers...

Why do we have to beat down development tools just because they remove the developer from having to DO THINGS THE Tool or Compiler should DO FOR YOU? This is what makes advanced devleopment and the progression of better applications bloom.

Go back to the VB of 1992, it was a major eplosion for application availability. Sure some of the programs were crap and from people that had no idea of coding, but there were also serious developers that didn't want to take time to screw with all the crap that a developer in THIS DAY and AGE should not have to do.

I welcome development tools advancement. Sure there is some fundamental coding knowledge that everyone should know, but you can't blame these tools for this.

I could have the same arguments about many projects in the Open Source world, they are brilliant, but since the coders have little undertsanding of usability or UI guidelines, they applications are virtually worthless to anyone that is not a geek.

I'm not even arguing VS is the best set of tools out there, Borland still makes some really great development environments. I still like Delphi, and am amazed of how tight the code it produces, and yet how much it DOES FOR ME, even if I do know how to do the things it is doing for me is irrelevant.

We not only need to support development that is beyond a text editor and command line compiler, but we also need to support development tools that try to structure and help users with usability for the people that will be using the applications. PERIOD.

VS and Borland products are pretty good, but they could even be better - imagine a development environment that gives a flag when it notices a break in usability, or gives a compile warning after it 'intellectually' sees the appliction has many inconsistencies that would confuse the user.

Additionally, VS is even dated for what the new Microsoft Development and technologies are introducing. VS2005 barely touches the abilities of future Windows development - that is why the 'Expression' like of products will be used to augment the UI and User experiene for VS applications.

Give the world a couple of years, and the foundations of 'native' understanding being built into the next generation of Windows Vista, WILL change not only the user experience, but the development world. Leapfrogging concepts of today.

Go look up some of the concepts Microsoft has introduced and HAS that are often overlooked, go do a search on the last PDC. There are things in Vista that move development to a new level of understanding and functionality for not only developers, but what the users will start to see in the next 5 years.

It is like one of the brains behind the XAML and XPS systems in Vista said, we are giving developers some so revolutionary, it is bascially fire. And right now these devleopers will just use this fire to cook meat, but eventually they will understand that this same fire is capable of pushig a rocket into outer space.

If you are a strong OPEN SOURCE believer, you need to pay CLOSE attention to the technologies of Vista and things we here often make fun of. If we discount them or don't fully understand how extensive these technologies are, we will be left far far behind in a coupld of years, when developers are pumping out applications that are not only beautiful (cooked meat), but taking users to places we can barely see now.

Vista's model is a great example of how development WILL change to higher level development and less of low level coding. Applications will be NOW built by graphic designers in addition to the script and VB kiddies. We will have a new creative element in applicaiton development with Vista (which will be on a lot of desktops no matter how much we like it or not).

Here is the thing with Vista.

A) It will be on a lot of computers, the market is already there and just new system shipments will guarantee its success, we have NO CHOICE on this.

B) It introduces so many new models of application interobility, and capabilities, it is staggering. Imagine a WHOLE OS that is passing XML as INTERNAL calls (no more Win32 concepts). Imagine an OS where XAML is not only telling the GPU in the machine how to display a floating cube in a chart, but also is using the same XAML to push information to other applications, telling the printer wha to print, and yet give applicatios an XAML and XML system of storing these messages being passed throughout the OS.

It is a freaking unified model, that can be molded and tapped into beyond what we can barely see right now. Just like the GDI of Windows 3.0 was overlooked at the time, and it is child's play compared to what Vista will do. (GDI and Win32 are dead in new development - it is new structured OS, that has GDI and Win32 compatibility. - Do NOT under estimate how powerful this will be for developers and users.)

Open Source people have an advantage, we can choose to understand what it WILL DO and see how we can 'steal' their concepts and start unifying our pet OSes.

I am lucky to have access to Vista to see some of the things coming, and a lot of this information is available for free at http://msdn.microsoft.com/ [microsoft.com] - go there, KNOW YOUR COMPETITION...

So I disagree with this idea that Higher level development tools that abstract us from having to do the 'plumbing' is a bad thing. I think that if we applied this model, then we should force everyone back to defining ASCII characters everytime we write an application, it would be just that stupid.

Not only do I disagree, but I think UI and Usability should be PUSHED more in development tools. Borland was always good with this and VS used to have a pretty crap IDE, but now is up to par with Borland's stuff.

Also don't forget, development tools is something Microsoft has DONE WELL, even if you are an open source devleoper, you can use VS for *nix development. The low level C and C++ compilers from Microsoft have been the leading edge for performance for many years.

In closing...
DON'T Discount MAKING THINGS easier, IT SAVES us old times a lot of time, even though we know how to hand code this crap ourselves.

Don't close your eyes to the paradigm shift that Vista and the development world will be seeing, we need to know the enemy (if that is how you see MS and Vista), because right now, their concepts are raping what we are doing in the Open Source world by 5 to 10 years at LEAST. This is a massive shift, and we NEED TO FREAKING PAY ATTENTION.

(And don't let the Mac only peeps convince you that Vista is just a OSX knock off - Sure Vista can do the pretties, but that is SO FAR from the bomb/fire that is in Vista. It has a solid NT foundation, keeps Win32 compatibility, and introduces a whole new OS in terms of capabilities and Development concepts. - And yes you are going to see applications that look amazing, do some really interesting things, and are written with a few lines of code by people that know 1/100th the development and coding concepts you do - this is the reality we will be facing.)
[ Reply to This ]
Starting Score: 1 point
Moderation +3
70% Interesting
30% Insightful
Extra 'Interesting' Modifier +1 (Edit)
Karma-Bonus Modifier +1 (Edit)


I work with someone who only last week could not comprehend exactly how they were going to go about doing a particular job as Visual Studio was not installed on the server. The job involved editing some XML config files and doing some minor Python programming. Visual Studio by default has absolutely zero Python support (Activestate and presumably others have $$$ plugins for it, but that's not the point). That particular sentiment came the day after I installed Vim (with the Cream suite - I do that on Windoze boxes to stop Windoze gumbies whining about the default keybindings - another symptom of "cannot cope outside the box") while they watched on, and we did some of the work together. The whole "outside the box" thing annoys me because this VB programmer culture festers this idea that those who do it the Microsoft Way are somehow immune to the requirement to be flexible. Case in point, there's no requirement for them to "put up with" using something other than Visual Studio - yet you take someone with Unix experience and the onus *is* on them to adapt. I know its because Unix people are far more flexible and generally smarter and more capable, but in reality it translates to our skills being taken for granted and abused when it suits the purpose.

Basically, I'm sick to death of seeing morons who shouldn't be allowed to use a computer being paid more than I am and given more opportunities simply because they have a tool that compensates for their complete lack of ability. First Microsoft develop the culture that it is acceptable to have not just implementation but design flaws - and serious flaws - in software; giving a mindset that IT is incompetent and crap must be expected. Then they develop a tool that makes it easy to churn out such crap. Then they abuse their illegal monopoly power to force educational institutions into calling a fairly incompetent artist (someone who can paint something boxish in Visual Studio) a software engineer. These people flood the industry, further entrenching the "expect crap" mindset in managers and also ensuring that the only solutions there are resources to develop are Microsoft based, furthering their illegally-obtained monopoly. The monopoly then ensures that its pointless to try to break the cycle and actually teach people real skills.

And folks like me who could competently code in 3 languages and get by in a few more *before* they reached tertiary education (and of course picked up many more during) want to leave the industry and take up another profession. I'm thinking infantry, where you can even get promoted for killing the people that really piss you off ;)

But for now I'll just bitch on /. *g*
--
Matt

1. Read Slashdot
2. ???
3. Profit
============

#2 Engineers Report Breakthrough in Laser Beam Tech

Engineers Report Breakthrough in Laser Beam Tech: "Overstated results
(Score:5, Interesting)
by PhysicsPhil (880677) Alter Relationship on Wednesday October 26, @04:29PM (#13884340)
Somewhere between the lab and the press release things got overstated. Since my PhD is in silicon-based optoelectronics, I am familiar with this kind of work. A few thoughts crossed my mind after reading the paper.

What these guys have found is a physical effect that possibly could lead to fast modulation of light. Neglected in the press release are a few fairly important issues:

* They haven't demonstrated any time-resolved optical effect, and are inferring it strictly from what might be possible. I have no doubt they can modulate, but the operational speeds are still guesstimates.
* The effect that was demonstrated is not within the 1550 nm wavelength window used for telecom traffic. Their current work shows the effect right in the middle of an H2O absorption peak. Can the effect be shifted? Probably, but these sorts of things are always more work than expected.
* From a practical standpoint, other Quantum Confined Stark Effect devices often show a strong sensitivity to the polarization of the input light. Ensuring a known input polarization is a major problem right now in optoelectronics. Lord knows it was (still is, actually) a major hassle in my research
* This device is not quite as CMOS compatible as might be hoped. Building strained germanium quantum wells on a silicon substrate requires depositing atoms layer by layer, and is a slow process. Process throughput will no doubt be an issue.

All that being said, this is still very exciting. It is a new physical effect demonstrated in a silicon-based material, and a physical effect that has been used elsewhere to do useful things. Hopefully a real modulation device will come along shortly."

Students Banned from Blogging

Students Banned from Blogging


Re:Constitutional protections....
(Score:5, Informative)
by cdrguru (88047) Alter Relationship on Tuesday October 25, @11:40PM (#13878139)
(http://www.infinadyne.com/)
The constitution applies to Federal laws, and perhaps state and local ones in some cases. It has no applicability to schools, employers, or anything else.

There is no "school" right to free speech. There is no right to free speech on the job. There is no right to free speech in a shopping mall, if the shopping mall has a rule that says otherwise. And, the First Amendment has nothing whatsoever to do with this because it is not a federal law. So, the government hasn't made a law abridging free speech.

Not unless you think the Federal government gets to review and approve all school rules, employee handbooks and shopping mall rules.

Dick at the Heart of Darkness -- Maureen Dowd NYT

t r u t h o u t - Maureen Dowd | Dick at the Heart of Darkness: "Dick at the Heart of Darkness
By Maureen Dowd
The New York Times

Wednesday 26 October 2005

After W. was elected, he sometimes gave visitors a tour of the love alcove off the Oval Office where Bill trysted with Monica - the notorious spot where his predecessor had dishonored the White House.

At least it was only a little pantry - and a little panting.

If W. wants to show people now where the White House has been dishonored in far more astounding and deadly ways, he'll have to haul them around every nook and cranny of his vice president's office, then go across the river for a walk of shame through the Rummy empire at the Pentagon.

The shocking thing about the trellis of revelations showing Dick Cheney, the self-styled Mr. Strong America, as the central figure in dark conspiracies to juice up a case for war and demonize those who tried to tell the public the truth is how un-shocking it all is.

It's exactly what we thought was going on, but we never thought we'd actually hear the lurid details: Cheney and Rummy, the two old compadres from the Nixon and Ford days, in a cabal running the country and the world into the ground, driven by their poisonous obsession with Iraq, while Junior is out of the loop, playing in the gym or on his mountain bike.

Mr. Cheney has been so well protected by his Praetorian guard all these years that it's been hard for the public to see his dastardly deeds and petty schemes. But now, because of Patrick Fitzgerald's investigation and candid talk from Brent Scowcroft and Lawrence Wilkerson, he's been flushed out as the heart of darkness: all sulfurous strands lead back to the man W. aptly nicknamed Vice.

According to a Times story yesterday, Scooter Libby first learned about Joseph Wilson's C.I.A. wife from his boss, Mr. Cheney, not from reporters, as he'd originally suggested. And Mr. Cheney learned it from George Tenet, according to Mr. Libby's notes.

The Bush hawks presented themselves as protectors and exporters of American values. But they were so feverish about projecting the alternate reality they had constructed to link Saddam and Al Qaeda - and fulfilling their idée fixe about invading Iraq - they perverted American values.

Whether or not it turns out to be illegal, outing a C.I.A. agent - undercover or not - simply to undermine her husband's story is Rove-ishly sleazy. This no-leak administration was perfectly willing to leak to hurt anyone who got in its way.

Vice also pressed for a loophole so the C.I.A. could do torture-light on prisoners in U.S. custody, but John McCain rebuffed His Tortureness. Senator McCain has sponsored a measure to bar the cruel treatment of prisoners because he knows that this is not who we are. (Remember the days when the only torture was listening to politicians reciting their best TV lines at dinner parties?)

Colonel Wilkerson, the former chief of staff for Colin Powell, broke the code and denounced Vice's vortex, calling his own involvement in Mr. Powell's U.N. speech, infected with bogus Cheney and Scooter malarkey, "the lowest point" in his life.

He followed that with a blast of blunt talk in a speech and an op-ed piece in The Los Angeles Times, saying that foreign policy had been hijacked by "a secretive, little-known cabal" that hated dissent. He said the cabal was headed by Mr. Cheney, "a vice president who speaks only to Rush Limbaugh and assembled military forces," and Donald Rumsfeld, "a secretary of defense presiding over the death by a thousand cuts of our overstretched armed forces."

"I believe that the decisions of this cabal were sometimes made with the full and witting support of the president and sometimes with something less," Colonel Wilkerson wrote. "More often than not, then-national security adviser Condoleezza Rice was simply steamrolled by this cabal."

Brent Scowcroft, Bush Senior's close friend, let out a shriek this week to Jeffrey Goldberg in The New Yorker, revealing his estrangement from W. and his old protégé Condi. He disdained Paul Wolfowitz as a naïve utopian and said he didn't "know" his old friend Dick Cheney anymore. Vice's alliance with the neocons, who were determined to finish in Iraq what Mr. Scowcroft and Poppy had declared finished, led him to lead the nation into a morass. Troop deaths are now around 2,000, a gruesome milestone.

"The reason I part with the neocons is that I don't think in any reasonable time frame the objective of democratizing the Middle East can be successful," Mr. Scowcroft said. "If you can do it, fine, but I don't think you can, and in the process of trying to do it you can make the Middle East a lot worse."

W. should take the Medal of Freedom away from Mr. Tenet and give medals to Colonel Wilkerson and Mr. Scowcroft.

The Strange Saga of Cheney and the "Nuclear Threat" -Jim Lobe

t r u t h o u t - Jim Lobe | The Strange Saga of Cheney and the "Nuclear Threat"

Go to Original

The Strange Saga of Cheney and the "Nuclear Threat"
By Jim Lobe
Salon.com

Wednesday 26 October 2005

Why did the veep suddenly lose interest in the evidence?

In the wake of the release of the Downing Street Memo, there has been much talk about how the Bush administration "fixed" its intelligence to create a war fever in the U.S. in the many months leading up to the invasion of Iraq. What still remains to be fully grasped, however, is the wider pattern of propaganda that underlay the administration's war effort - in particular, the overlapping networks of relationships that tied together so many key figures in the administration, the neoconservatives and their allies on the outside, and parts of the media in what became a seamless, boundary-less operation to persuade the American people that Saddam Hussein represented an intolerable threat to their national security.

Vice President Cheney, for instance, is widely credited with having launched the administration's nuclear drumbeat to war in Iraq via a series of speeches he gave, beginning in August 2002, vividly accusing Saddam of having an active nuclear weapons program. As it happens, though, he started beating the nuclear drum with vigor significantly earlier than most remember; indeed at a time that was particularly curious given its proximity to the famous mission former Ambassador Joseph Wilson took on behalf of the CIA.

Cheney's initial public attempts to raise the nuclear nightmare did not in fact begin with his August 2002 barrage of nuclear speeches, but rather five months before that, just after his return from a tour of Arab capitals where he had tried in vain to gin up local support for military action against Iraq. Indeed, the specific date on which his campaign was launched was March 24, 2002, when, on return from the Middle East, he appeared on three major Sunday public-affairs television programs bearing similar messages on each. On CNN's "Late Edition," he offered the following comment on Saddam:

"This is a man of great evil, as the President said. And he is actively pursuing nuclear weapons at this time."

On NBC's "Meet the Press," he said:

"[T]here's good reason to believe that he continues to aggressively pursue the development of a nuclear weapon. Now will he have one in a year, five years? I can't be that precise."

And on CBS's "Face the Nation":

"The notion of a Saddam Hussein with his great oil wealth, with his inventory that he already has of biological and chemical weapons, that he might actually acquire a nuclear weapon is, I think, a frightening proposition for anybody who thinks about it. And part of my task out there was to go out and begin the dialogue with our friends to make sure they were thinking about it."

Why do I think that Cheney moment, that particular barrage of statements about Saddam's supposed nuclear program, remains so significant today, in light of the Plame affair?

For one thing, that Sunday's drum roll of nuclear claims indicated that the "intelligence and facts" were already being "fixed around the policy" four months before Sir Richard Dearlove, head of Britain's MI6, reached that conclusion, as recorded in the Downing Street Memo. It's worth asking, then: On what basis could Cheney make such assertions with such evident certainty, nearly six months before, on September 7, 2002, Judith Miller and Michael Gordon of the New York Times first broke a story about how Iraq had ordered "specially designed aluminum tubes," supposedly intended as components for centrifuges to enrich uranium for Saddam Hussein's nuclear weapons program. Even five months later, after all, those tubes would still be the only real piece of evidence for the existence of an Iraqi nuclear program offered by Colin Powell in his presentation to the UN Security Council.

Indeed, on March 24 when Cheney made his initial allegations about an Iraqi nuclear program, we know of only two pieces of "evidence" available to him that might conceivably have supported his charges:

* 1) Testimony from Adnan Ihsan Saeed al-Haideri, a "defector" delivered up by Ahmad Chalabi's exile organization the Iraqi National Congress (INC), and enthusiastically recounted by the Times' Miller on December 20, 2001 (although rejected as a fabrication by both the CIA and Defense Intelligence Agency). Al-Haideri claimed to have personally worked on renovations of secret facilities for biological, chemical, and nuclear weapons in underground wells, private villas, and under the Saddam Hussein Hospital in Baghdad as recently as 2000.

* 2) The infamous forged Niger yellowcake documents that, at some point in December, 2001 or January, 2002 somehow appeared on Cheney's desk, supposedly through the Defense Intelligence Agency or the CIA, though accounts differ on the precise route it took from Italian military intelligence (SISMI) to the Vice President's office. It was these and related documents that spurred Cheney to ask for additional information, a request that would eventually result in Wilson's trip to Niger in late February, which, of course, set the Plame case in motion. Wilson's conclusion - that there was nothing to the story - would echo the conclusions of both U.S. ambassador to Niger Barbro Owens-Kirkpatrick and Marine Gen. Carlton W. Fulford Jr., then-deputy commander of the U.S. European Command who was also sent to Niger in February. A couple of days after his return to Washington, Wilson would be debriefed by the CIA.

How far up their respective chains of command Wilson's and Fulford's reports made it remains a significant mystery to this day. Cheney's office, which reportedly had reminded the CIA of the Vice President's interest in the agency's follow-up efforts even while Wilson was in Niger, claims never to have heard about either report. We do know that Fulford's report made it up to Joint Chiefs Chairman Richard Myers whose spokesman, however, told the Washington Post in July 2003, shortly after Wilson went public on the New York Times op-ed page, that the general had "no recollection" of it and so no idea whether it continued on to the White House or Cheney's office.

Meanwhile, Cheney, whose initial curiosity set off this flurry of travel and reporting, appeared to have lost interest in the results by the time he left on a Middle Eastern trip in mid-March; at least, no information has come to light so far indicating that he ever got back to the CIA or anyone else with further questions or requests on the matter of whether Saddam had actually been in the market for Niger yellowcake uranium ore. Yet, within four days of his return to Washington, there he was on the Sunday TV shows assuring the nation's viewers that Iraq was indeed "actively pursuing nuclear weapons at this time."

Did he then acquire new information, perhaps from Iraq's neighbors, during his trip to the Middle East, or had he simply decided by then that the "facts" really had to be "fixed" - or more precisely in Wilson's case, ignored altogether - if the American people were to be persuaded that war was the only solution to the problem of Saddam Hussein? In any event, one can only describe his sudden lack of curiosity combined with his public certainty on the subject as, well ... curious.

That Cheney did indeed make the initial request to follow up on the Niger yellowcake report appears now to be beyond dispute, and it also draws attention to another little-noted curiosity of the Plame case - the knowledge and role of Clifford May, ex-New York Timesman, recent head of communications for the Republican National Committee (1997-2001), and president of the ultra-neo-conservative Foundation for the Defense of Democracies (FDD). In an article at National Review Online (NRO) on September 29, 2003 (as pressure was building on John Ashcroft to appoint a special prosecutor in the case), he boasted that he had been informed by an unnamed former government official of Wilson's wife's identity long before her outing as a CIA operative by Robert Novak, on July 14, 2003, and so had assumed that her identity (and relationship to Wilson) had been an "open secret" among the Washington cognoscenti. He has subsequently told the Nation magazine's David Corn among others that he was interviewed by the FBI but has never been asked to testify on the subject before Special Prosecutor Patrick Fitzgerald's grand jury.

In that NRO article, he also noted that he "was the first to publicly question the credibility of Mr. Wilson" following the ambassador's Times op-ed. Indeed, only five days after that op-ed appeared, on July 11, 2003, NRO published May's first attack on Wilson - many more would follow right up to the present - depicting the ambassador as a "pro-Saudi, leftist partisan with an axe to grind." The article - and this is the curious part - included the following passage: "Mr. Wilson was sent to Niger by the CIA to verify a U.S. intelligence report about the sale of yellowcake - because Vice President Dick Cheney requested it, because Cheney had doubts about the validity of the intelligence report." This phrasing is fascinating because it purports to know Cheney's subjective motivation, and the motivation ascribed to him - that he had "doubts" about the Niger story - conflicts with everything we've otherwise come to understand about why he asked for the Niger story to be investigated. It hints, certainly, at how consciously Cheney would indeed fix the facts when it came to Saddam's nuclear doings.

Given this tidbit of curious information hidden in May's piece, it's important to know what former government officials might not only have told May about Plame's identity but possibly about Cheney's real thoughts on the subject of Saddam's nuclear program - presuming, that is, that Cheney himself or Scooter Libby, his chief of staff, was not the source. Among May's board of advisers at FDD were several former government officials, a number of whom were known to be very close to Cheney and Libby as well as to Pentagon hawks like Deputy Secretary of Defense Paul Wolfowitz and Undersecretary of Defense Douglas Feith. They included Richard Perle, head of the Center for Security Policy Frank Gaffney, former CIA Director James Woolsey, and Weekly Standard editor Bill Kristol. All of them played starring roles in efforts to tie Saddam's Iraq to al-Qaeda and the 9/11 attacks as well as in raising the nuclear bogeyman well before Cheney did so on March 24, 2002.

In fact, a close examination of how the pre-war propaganda machine worked shows that it was led by the neocons and their associates outside the administration, particularly those on the Defense Policy Board (DPB) like Perle, Woolsey, and Kenneth "Cakewalk" Adelman (and Judith Miller of the Times) who had long championed the cause of Ahmad Chalabi and his Iraqi exile organization, the INC, and were also close to the Office of Special Plans that Douglas Feith had set up in the Pentagon to cherry-pick intelligence. They would invariably be the first to float new "evidence" against Hussein (such as the infamous supposed Prague meeting of 9/11 conspirator Mohammed Atta with an Iraqi intelligence officer). They would then tie this "evidence" into ongoing arguments for "regime change" in Iraq that would often appear in the Times or elsewhere as news and subsequently be picked up by senior administration officials and fed into the drumbeat of war commentary pouring out of official Washington.

It is by now perfectly clear that the neo-conservatives on the outside were aided by like-minded journalists, particularly the Times' Miller - then the only "straight" reporter on the client list of neoconservative heavyweights and columnists represented by Benador Associates - and media outlets, especially the Wall Street Journal's editorial page and Fox News. Working hand-in-glove with the war hawks on the inside, they created a powerful and persuasive machine to convince the public that Saddam Hussein's Iraq represented an imminent and potentially cataclysmic threat to the United States that had to be eliminated once and for all. The failure to investigate and demonstrate precisely how seamlessly this web of intra- and extra-administration connections worked in the run-up to the war - including perhaps in the concoction of the Niger yellowcake documents, as some former intelligence officials have recently suggested - has been perhaps the most shocking example of the mainstream media's failure to connect the dots (the reporters from Knight-Ridder excepted.)

In that context, it is worth noting the first moment that the specter of an advanced Iraqi nuclear-weapons program was propelled into post-9/11 public consciousness. On December 20, 2001, the New York Times published Judith Miller's version of the sensational charges made by Chalabi-aided defector al-Haideri. Her report was immediately seized on by former CIA Director and DPB member Woolsey (who had just spent many weeks trying desperately but unsuccessfully to confirm the alleged Mohammed Atta meeting in Prague that would have linked Saddam to the 9/11 attackers). Appearing that same evening on CNBC's "Hard Ball," he breathlessly told Chris Matthews, "I think this is a very important story. I give Judy Miller a lot of credit for getting it. This defector sounds quite credible." Within a week, he was telling the Washington Post that the case that Iraq was developing nuclear weapons was a "slam dunk." (Now, there's a familiar expression!) He continued confidently, "There is so much evidence with respect to his development of weapons of mass destruction and ballistic missiles… that I consider this point beyond dispute."

One week later, Perle weighed in with an op-ed in the New York Times in which he also referred to Miller's work, albeit without naming her. "With each passing day, [Saddam] comes closer to his dream of a nuclear arsenal," he wrote.

"We know he has a clandestine program, spread over many hidden sites, to enrich Iraqi natural uranium [Nigerian yellowcake perhaps?] to weapons grade. We know he has the designs and the technical staff to fabricate nuclear weapons once he obtains the material. And intelligence sources know he is in the market, with plenty of money, for both weapons material and components as well as finished nuclear weapons. How close is he? We do not know. Two years, three years, tomorrow even? We simply do not know, and any intelligence estimate that would cause us to relax would be about as useful as the ones that missed his nuclear program in the early 1990's or failed to predict the Indian nuclear test in 1998 or to gain even a hint of the Sept. 11 attack."

It was a new argument being taken out for a test run, one that would become painfully familiar in the months that followed. At about that time, or shortly thereafter, a report about the mysterious Niger documents landed on Cheney's desk and the rest would be history.