Bush's Terror Error

Grok Headline matches for Bush's Terror Error

How Satan is propping up Bush's war on
terror

How Satan is propping up Bush's war on
terror 01/18/2004 04:54 AM
An obsession with the devil, born out of personal experience, explains why so many fundamentalist Christians believe that Saddam Hussein and Osama bin Laden were working together.

U.S. Citizen Can't Be Held in Bush's War
on Terror (Reuters)

U.S. Citizen Can't Be Held in Bush's War
on Terror (Reuters) 06/28/2004 10:11 AM
Reuters - The U.S. Supreme Court ruled on Monday that an American captured overseas in President Bush's war on terrorism cannot be held indefinitely in a U.S. military jail without a chance to contest the detention.

Bush's Leadership Against Terror Hailed
(washingtonpost.com)

Bush's Leadership Against Terror Hailed
(washingtonpost.com) 09/01/2004 12:31 AM
washingtonpost.com - NEW YORK, Aug. 31 -- The Republican National Convention spent a second night celebrating President Bush's leadership in the struggle against terrorism, praising him for putting "all his heart and soul" into the fight against America's enemies.

Bush's Ratings Erode as Anti-Terror
Fighter

Bush's Ratings Erode as Anti-Terror
Fighter 06/21/2004 10:13 PM
Reuters via Wired News Jun 22 2004 2:43AM GMT

Chart of terror alerts and Bush's
approval ratings

Chart of terror alerts and Bush's
approval ratings 09/06/2004 05:37 AM

Interesting chart showing how terror alerts in the US seems to coincide with drops in Bush's approval ratings.

via JuliusBlog

Comment - TrackBack

Kerry Attacks Bush's Handling of
Campaign Against Terror

Kerry Attacks Bush's Handling of
Campaign Against Terror 09/24/2004 02:17 PM
Senator John Kerry said attacks were on the rise and the Bush administration was "in confusion" about how to respond.

High Court Deals Blow to Bush's War on
Terror (Reuters)

High Court Deals Blow to Bush's War on
Terror (Reuters) 06/28/2004 07:45 PM
Reuters - The U.S. Supreme Court placed the first limits on President Bush's war on terrorism on Monday when it ruled that terror suspects can use the American judicial system to challenge their confinement.

Bush's Ratings Erode as Anti-Terror
Fighter (Reuters)

Bush's Ratings Erode as Anti-Terror
Fighter (Reuters) 06/21/2004 08:35 PM
Reuters - Public confidence in President Bush's ability to fight terrorism has significantly eroded, in a challenge to his re-election campaign as a "war president," according to a poll released on Monday.

HotFix Watch: Win32 Error = 1072 error
appears after you change the SMS 2.0
Service account of a secondary site

HotFix Watch: Win32 Error = 1072 error
appears after you change the SMS 2.0
Service account of a secondary site 12/28/2004 07:03 PM

Cliex32.dll Error 126 Error in
Wnmanual.log

Cliex32.dll Error 126 Error in
Wnmanual.log 06/18/2004 08:16 AM

Advanced Error Handling: Writing an
Error Handling Class

Advanced Error Handling: Writing an
Error Handling Class 11/10/2003 11:25 PM
If you're tired of the default error handler and want to have complete control over default error messages, you should write your own error handling class. Writing your own handler will enable you to change the way php handles your error messages, and allows you to create your own error types. With this class you will be able to send error messages to a log file, or send error reports via email.

SignOnSanDiego.com > News > Nation
> America's War on Terror -- Ex-S.D.
sailor allegedly linked to terror
suspect

SignOnSanDiego.com > News > Nation
> America's War on Terror -- Ex-S.D.
sailor allegedly linked to terror
suspect 08/07/2004 09:06 PM
a sailor sent valuable information about fleet movements .. San Diego Union-Tribune .. email

signonsandiego.com/news/nation/terror/20040807-9999-1n7benfold .html
track this site | 3 links

The Command Post - Global War On Terror
- Albany Mosque Raided In Terror Plot
Sting

The Command Post - Global War On Terror
- Albany Mosque Raided In Terror Plot
Sting 08/05/2004 10:21 AM
Two Men With Suspected Ties Ansar al-Islam Arrested in Albany Mosque Raid .. raid and arrests .. The Command Post

command-post.org/gwot/2_archives/014220.html
track this site | 3 links

PXE-E51 Error

PXE-E51 Error 08/14/2004 05:23 PM

Error

Error 08/10/2004 02:34 PM

livejournal.com/tools/memadd.bml?journal=jmhm&itemid=959603
track this site | 2 links

404 error

404 error 01/14/2003 02:28 PM

I found this funny 404 error message on SDForum's Web site:

Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.

VBScript Error with FTM

VBScript Error with FTM 09/02/2004 02:43 AM

Error in SMS RTM Documentation

Error in SMS RTM Documentation 05/28/2004 05:06 AM

Error-Wait-0.05

Error-Wait-0.05 12/27/2003 06:42 PM

Read error

Read error 11/02/2003 05:25 PM
CNET Asia Nov 2 2003 4:29PM ET

Error-Wait-0.02

Error-Wait-0.02 11/16/2003 04:50 AM

Error-Wait-0.03

Error-Wait-0.03 11/16/2003 04:50 AM

Error In Downloading

Error In Downloading 11/14/2003 09:47 PM
Record, tech industries battle to make music pay off. By Russ Britt and Steve Gelsi (CBS MarketWatch via MyAppleMenu)

Error in fink-0.22.0

Error in fink-0.22.0 08/21/2004 12:30 PM
The fink-0.22.0 package manager, which was available briefly in the unstable tree this past week, had a bug which prevents further updating via rsync. If you installed this version of fink, you can recover by running the command fink install fink-0.21.2-1 which will downgrade fink to the version in the stable tree, and subsequently running fink selfupdate If for any reason those commands don't work, go to the fink file release page at sourceforge and download the file fink-0.22.1.tar.gz . Unpack this file with tar xfz fink-0.22.1.tar.gz , and then from within the fink-0.22.1 directory, run the command ./inject.pl The fink team apologizes for the error, and thanks the user community for bringing it to our attention quickly.

Error-Wait-0.01

Error-Wait-0.01 11/03/2003 05:54 PM

Database Error

Database Error 05/07/2004 06:10 AM

Access Error

Access Error 05/24/2004 04:33 AM
General Says Sanchez Rejected Her Offer to Give Address to Iraqis About Abuses

c.moreover.com/click/here.pl?r157808591
track this site | 3 links

On "Feedbag Error 17"...

On "Feedbag Error 17"... 10/29/2003 12:10 AM

A couple of days ago I noticed that I couldn't add Azeem Azhar to my iChat AV contacts list. I kept getting returned "Feedbag Error 17" which seemed entirely unexpected and unpleasantly phrased. Was I a feedbag? Had iChat eaten Azeem? The mind boggled.

After several hours of consideration, another option occurred to me. Perhaps iChat was trying to protect me from excessive contact with Azeem! Maybe my beautiful new Pantherised beast was being defensive! "No, Tom!" It was going, "He's bad news! He'll tell you that you work in Marketing again and you'll get all cross and defensive and make that ludicrous speech about being an artisan! Please! Please! Let me protect you from the embarrassment!" At which point, I assumed, feedbag laptop decided to chow-down on poor Mr Azhar's AIM name with fierce hungry vengeance. I touted this theory around a few of my friends. General consensus, "It's not a bug, it's a feature!"

Well now I know that I'm not alone and that it's nothing personal, Mr Azhar! My Powerbook loves you and iChat loves you and all I had to do was throw away a couple of my childhood friends who - frankly - are never online anyway and kind of sucked at web stuff. In the end the problem was all caused by having too many friends - apparently AIM can only handle 150 contacts - at least that is according to Mssrs. Unsanity, Rael and Webb.

But it occurs to me that there's something slightly suspicious about all of this. A couple of days ago I tried searching for information about this error message, but it was nowhere. There was literally no information. Today, there's a search result returned, and posts about the subject on three separate weblogs. So what's happened? Is it a new error message or is it just we've all hit the limit at the same time? Or has the number of buddies available changed? I smell a mystery!

Read the comments

Margins of Error

Margins of Error 07/20/2004 09:16 AM
Wider margins should be greeted with wider smiles.

A possible fix for an iTunes 4.8 error
400

A possible fix for an iTunes 4.8 error
400 06/22/2005 02:23 AM
If you recently upgraded iTunes, you may have problems authenticating, viewing your cart, or shopping. There are two errors which have been occuring recently. The first seems to be 502, I believe, and this appears to be resol...

Error Handler

Error Handler 04/16/2005 11:27 PM
Support now available

More on XML Error Handling

More on XML Error Handling 01/22/2004 02:56 AM

I thought I'd respond to a few of the comments I received:

Many people suggested that there be a built-in validator in the browser that could show the errors to the developer. The validators basically break down into two types: obtrusive validators and unobtrusive validators.

If the validator is unobtrusive, then I would argue that it won't receive sufficient usage to make a difference. If the browser doesn't impose a penalty of some kind, then there will be no incentive for the author to correct mistakes.

I can see the value of an obtrusive validator, as long as the obtrusive part was only checking well-formedness (i.e., really basic mistakes).

(2) Some people pointed out that my own blog was not valid. I have two responses to that:

(a) I am not arguing for perfectly valid XML documents. I am arguing for well-formed XML documents. There is a difference. I think asking that the page be well-formed is setting the bar fairly low. For example, one of the current errors on this blog is that I have two elements with the same id. While this makes the blog invalid, it does not have any effect on the blog being well-formed. At least I don't think it does. :)

(b) I'm illustrating a point, namely that I have no reason to make the blog valid, given that browsers will display the blog anyway.

(3) People complained that I wasn't serving up XHTML. I can't actually serve up XHTML if I want the blog to be displayable in all browsers, including Safari, which still has sufficient issues with XHTML that I can't make that switch yet.

(4) My comments on HTML error handling were largely misinterpreted.

Some people thought I was attacking WinIE for its permissive handling of HTML. I was not, and I'm glad others appreciated that fact. Back in the 90s WinIE had to emulate the permissive error handling of the then-dominant browser Netscape. They had no choice if they wanted Web sites to be viewable as the designer intended. They were in the same position then that Safari is in now.

Nor am I suggesting that WinIE should become less tolerant of malformed HTML, or that they are at fault for not doing so. That is simply not a logical conclusion to have drawn from my previous comments. You can't take a Web site (even a malformed one) that works a certain way and suddenly refuse to render it or even render it radically differently than before.

For HTML, this issue was resolved long ago in favor of permissive error handling and recovery, and no modern browser is to blame for that situation.

Others said a browser that handles malformed HTML is better than one that does not, and if Safari doesn't handle all this malformed HTML, then it's simply not as capable a browser.

What amused me about this comment is that there is no definition of what it means to handle malformed HTML. As long as a browser shows you something and doesn't crash, it has handled the malformed HTML. What people don't understand is that you don't simply have to handle the malformed HTML. You have to handle it in exactly the same way as the Web browser that the site author designed for.

If you do not, you'll end up with different renderings of the same page, which as I said before, constitute the largest set of rendering differences between Web browsers. Perfect emulation is what makes error recovery so difficult. If you allow grossly malformed pages, then most XML on the Web will end up being grossly malformed (as is the case with HTML today).

Once you have a Web full of grossly malformed XML, there will be one dominant browser that designers will check to see if the site looks ok. They will then make assumptions that other browsers will recover from the malformation errors in precisely the same way and will simply assume that it is the fault of the other browsers if they don't.

Right now it is the responsibility of alternate browsers to emulate the dominant browser's error recovery strategies, but there's simply no reason to do that for XML as well.

SMS FAQ: Error Code 53

SMS FAQ: Error Code 53 06/24/2004 09:38 PM

Blue Or Red? Error Or Not?

Blue Or Red? Error Or Not? 04/05/2005 04:18 AM
More variation mongers, but this time it's legit - though a little bass ackwards, or is it?

XML Error Reporting II

XML Error Reporting II 01/22/2004 03:30 PM

Responding to comments in the previous blog entry:

(1) Some people thought this was a hacked expat. Darin actually switched Safari over to libxml2, so the error messages you're seeing (as well as the ability to continue parsing) are all built in to libxml2.

(2) Do you think it's better to show the page only up to the first error or to try to display the entire page (with the understanding that what follows the first error could be very badly mangled)?

(3) Often there are a lot of meaningless errors after the first. I could put a cap on the number of displayed errors to deal with this problem or just not worry about it. What do people think?

(4) Those of you who suggested drawers for errors, remember a drawer is a UI element in Safari and not WebKit. This feature should just work out of the box for WebKit clients, so I'm inclined not to use drawers or sheets, but to just display the errors at the top of the page.

Spot the Error

Spot the Error 02/10/2004 02:45 AM
Cleaned up eh? (hint: line 28)...

XML Error Reporting III

XML Error Reporting III 01/24/2004 02:50 PM

Thanks to those of you who answered my question regarding how much of an invalid page should be rendered. It turns out that the XML spec is clear on this issue, and that I must stop building up the page DOM after the first fatal error is encountered.

With that in mind I now tell libxml to continue the processing, but I start ignoring all of the callbacks. That way I get a list of all the errors, but properly stop the DOM tree buildup after the first error.

For those of you who suggested that WebKit needs some sort of error reporting API, I agree, and if it had one, these errors would obviously be reported to it. However, these errors still have to be reported aggressively so that WebKit clients can't mask these mistakes.

I don't believe in showing a sheet or a dialog as an intermediate step prior to displaying a rendering of the page. The reason I dislike this idea is that this error reporting is primarily a Web developer feature, and they're just going to want to load the page, see the errors, maybe correct some CSS at the same time, and then reload with changes until the error report has been eliminated.

The end user isn't ever going to see this report, since anyone who makes an invalid XML file right now ends up with something that won't display in any browser. Thus it seems to me that the report should be easy to access (in terms of # of clicks), always visible, and included with the page rendering.

I have polished the look of the report a bit based off suggestions. Here's another screenshot.

404 ERROR - Ultrashock.com

404 ERROR - Ultrashock.com 12/14/2003 06:49 AM
usable 404 page

ultrashock.com/404
track this site | 4 links

Funny error message

Funny error message 04/09/2004 04:02 PM
So I'm reading some science news about John Gottman and Robert Levenson, who have developed a mathematical model to predict with a 80% or higher accuracy rate whether a marriage will last. Interesting stuff: essentially, in marriages that last, positive interactions outnumber negative ones by a 5 to 1 ratio or more, creating a sort of bank of postive feeling to help couples recover from the inevitable arguments. So I want to read an actual paper, but am having no luck on the Gottman Institute web site getting from an abstract page to a paper. After several tries, I click on this abstract and read it, then try to go to the actual journal page. The error message I get is "You have entered a phrase that is too generic. Please try again." What? Running a web site like Zen Haiku, I understand why the link went stale, but that's still an awfully strange error message....
Grok Description matches for Bush's Terror Error
GrokA matches for Bush's Terror Error

Bush's Terror Error

The following phrases have been identified by the grok system as matching this entry: