Tracking the Blackout bug

Grok Headline matches for Tracking the Blackout bug

Broadlook--#1 Applicant Tracking
Software Solution--Empowers your
Applicant Tracking Software and fills
your Applicant Tracking Software with
applicant tracking relationships.

Broadlook--#1 Applicant Tracking
Software Solution--Empowers your
Applicant Tracking Software and fills
your Applicant Tracking Software with
applicant tracking relationships. 07/16/2004 03:14 AM
Whichever applicant tracking software your company uses, you need to look at the Broadlook Suite of Software which should seamlessly integrate with whichever applicant tracking software you are using. BroadLook is an integrated set of applications designed to harness the Internet as a powerful real-time data source--the data from which can be exported into your applicant tracking software. [PRWEB Jul 16, 2004]

Clockware Releases Version 4.4 -
Significantly Enhances Timesheet Styles,
Expands Status Tracking, Employee and
Organizational Data Tracking Features

Clockware Releases Version 4.4 -
Significantly Enhances Timesheet Styles,
Expands Status Tracking, Employee and
Organizational Data Tracking Features 04/05/2005 04:50 AM
Clockware announces its seventh major release in eight years, adding enhancements to its enterprise timesheet software, time tracking, leave and exception time tracking and other key timesheet system features. [PRWEB Apr 5, 2005]

Tracking Blogs, Tracking Packages --
What's The Difference?

Tracking Blogs, Tracking Packages --
What's The Difference? 03/31/2005 09:04 AM
Extreme Tech Mar 31 2005 1:16PM GMT

Web Tracking of Billable Time Improves
Productivity and Bottom Line/New Kyebot
Time Tracking and Billing Software
Announces Availability

Web Tracking of Billable Time Improves
Productivity and Bottom Line/New Kyebot
Time Tracking and Billing Software
Announces Availability 09/13/2004 02:58 AM
New Web-based time and billing application simplifies administrative tasks associated with tracking billable hours and virtually eliminates problems with under-billing. [PRWEB Sep 13, 2004]

Tracking the newsroom bug-tracking idea

Tracking the newsroom bug-tracking idea 02/01/2005 09:42 PM
I want to return to the idea I floated a few days ago about bug-trackin g software for newsrooms. The comment s response ranged from "neat idea!" to "it'll never work," so let's look it over again.

What I imagined was something similar to the way open-source software development projects manage bug reports. When people file bugs against such a project, they go to a publicly available online resource and enter a form that says "Here's a problem I encountered," and provide details. Different projects follow different organizational structures, but generally speaking, other developers will review the bug and try to classify it: Sometimes they'll say it's a duplicate and point to previous entries in the database that dealt with it; sometimes they'll say it's a simple problem and go fix it right away and close it out; sometimes they'll say it's a big one and leave it open to be dealt with in the future; sometimes they'll say it's a "known bug" that for one reason or another is never going to be fixed; sometimes they'll say it's not a bug at all.

For a newsroom, the idea is to provide a structure and a channel for reader dissatisfaction. You wouldn't have to follow the software model detail for detail, but the general outline could be valuable: Provide a form for readers to enter complaints, one that requires them to present details. Post the complaint publicly as soon as it's entered, and record the publication's response in a reasonably prompt fashion -- anything from "Thanks, we fixed the spelling on that name" to "we chose the phrase 'private accounts' because it is an accurate description of the president's proposal, and the label was in wide use by supporters of the idea until very recently, so we do not plan to stop using the term." The explanation is on record, and if other readers keep filing the same complaint they can simply be pointed back to the original answer. Spam? Just delete it. Letters to the editor that don't have a specific complaint? Re-route them to the letters box.

The most common objection seems to be, forget it -- this will become another free-for-all for political partisans to work out their agendas, another wide-open Internet forum that will degenerate into circular debate. Such forums already exist, to be sure; the point of a bug tracker is to avoid that outcome by choosing a narrower environment for the feedback that allows you to quickly aggregate and dispose of duplicate complaints, and that provides a public record of responsiveness and accountability. If 500 people all holler that you shouldn't say "private accounts," you can answer them once and be done with it -- but you can point each individual complaint back to your explanation, so those people understand that you actually heard them and offered some sort of response. There's a big difference between the silence of no response and "no, we're not doing that, here's why." The latter won't satisfy everyone, but it at least acknowledges that there's been an exchange on the subject.

Ross Karchner proposed a somewhat different model based on wiki practices: "1) A publically viewable changelog, where you can see, in detail, the changes made to an article. 2) A place where the author(s) and editor(s) can discuss the changes needed and made. This is also in public view..." I'm not sure whether Ross means the changelog and the writer/editor dialogue to commence from the first time the writer composed a draft, or only upon publication. The former is, I think, too wide open -- even a blogger has the right to compose a posting and revise it in private before choosing to push the "publish" button. The latter is fine -- but since most reputable publications rarely change articles once they're published, and note the changes as corrections if they do, then it's just codifying an existing practice in slightly different ways.

As for the idea of trying all this out at Salon: Who knows, I might well advocate it, though my current on-leave status doesn't put me in a good spot to work on it. But Salon has been dealing with the back-and-forth of online criticism of our work for 9 years plus. Whatever problems we may suffer from, a failure of responsiveness to online feedback is not, I think, one of them, and we have a pretty sturdy process for reviewing complaints fast and correcting them where needed.

I think this approach would pay off best for a newsroom that is having difficulty convincing readers that the publication is actually listening to them. If you showed the public that you were recording and responding to the issues they raised -- whether you end up publishing a correction or simply saying, "We don't think that needs correcting, and here's why" -- I think you'd start to bank some confidence and trust pretty quickly.

I'm not suggesting that this idea is the single, one-fix-solves-all-problems answer to the ills of journalism today. It's a pragmatic, you-could-do-it-real-soon suggestion for beginning to deal with professional journalism's biggest problem: the public's loss of trust, which begins with the sense that media companies are big institutions that pay no attention to their own mistakes.

.ca Blackout

.ca Blackout 06/13/2004 12:41 AM

CIRA's on a witch hunt, and the first casualties are the wave of multiple suspended .ca domains dropping off the internet this weekend.

Blackout ultimatum

Blackout ultimatum 08/27/2004 01:48 PM
GNU-Darwin wishes to reiterate our solidarity with the anti-war demonstrators, and warn the powers that we will go black with an extended list of demands if the NYC demonstrators are ill-treated, harmed, or molested in any substantial way. We will also join the boycott plans against Disney, etc, and we will lend the communicative power of our Distribution to that effort.

anti-war blackout

anti-war blackout 03/13/2003 10:23 AM
In the event that war breaks out with Iraq, GNU-Darwin will observe the anti-war moratorium by replacing our home page with the following message; Stop the war now!

Other News: The Blackout Bug

Other News: The Blackout Bug 02/18/2004 10:41 AM
Who could have guessed - a software bug played a part in the massive U.S. blackout last year?

GNOME BlackOut 0.1

GNOME BlackOut 0.1 05/18/2004 05:59 AM
A clone of the Tiger Toys game, Lights Out!

The Ben Barnes blackout

The Ben Barnes blackout 08/30/2004 03:46 PM
Even with new video of the Texas pol saying he's "ashamed" of helping President Bush get his National Guard slot, the story gets little play from the media.

How to beat the blackout blues

How to beat the blackout blues 12/21/2003 01:23 AM
US News Dec 21 2003 0:01AM ET

Blackout Cause: Buggy Code

Blackout Cause: Buggy Code 02/12/2004 10:11 AM

Software Bug Contributed to Blackout

Software Bug Contributed to Blackout 02/12/2004 12:54 PM

GNU-Darwin: blackout anniversary

GNU-Darwin: blackout anniversary 04/09/2004 04:10 PM
On this day last year we announced our intent to blackout in protest of US aggression in Iraq. All of the major points of our argument have been vindicated, while the Bush administration has spent the past year back-pedaling, whitewashing, and covering up the many lies that they have told. If you are interested in revisiting the rationale for the GNU-Darwin anti-war blackout, it was formalized and generalized in a short essay the following April .

Did Blaster cause the August blackout?

Did Blaster cause the August blackout? 12/10/2003 10:18 PM
Bruce Schneier (author of Beyond Fear) speculates that the great August blackout on the East Coast may have been caused by the Blaster worm.

Although the worm didn't have to perform any malicious actions on the computers it infected, its mere existence drained resources and often caused the host computer to crash. To remove the worm, a system administrator had to run a program that erased the malicious code; then, the administrator had to patch the vulnerability so that the computer would not get reinfected.

The coincidence is too obvious to ignore. At 2:14 p.m. EDT, the MSBlast worm was dropping systems all across North America. The report doesn't explain why so many computers--both primary and backup systems--at FirstEnergy were failing at around the same time. But MSBlast is certainly a reasonable suspect.

Lin k

BarlowSpams Sucked Into Blackout...

BarlowSpams Sucked Into Blackout... 01/07/2004 02:14 PM
Interesting problem. Shortly before posting the preceding two entries here last night, I dispatched them to my mailing list. But, at almost exactly the same time, the Mission District power substation in San Francisco caught on fire and shut down power to much of Babylon, particularly including the network operations center, only two blocks away from the substation, wherein sits the server that processes the BarlowFriendz list-serve. So. My spams never spammed forth. Whether they even exist any place besides my hard disk is difficult to determine, since, despite the installation of a 90 kw generator at the NOC this afternoon, things remain pretty whacked down there. My dilemma is trying to decide whether to resend them. If they were randomized into non-existence when the power blanked, then I will send them again, since they announce the existence of this blog to many folks who are unlikely to happen upon it. On the other hand, the server may stagger back into operation this evening, find them mouldering in its gullet, and spit them out. Which means that everyone would get them twice. Worst case, I try to resend, and the list-serve will gag even harder on the resend, further delaying its rehabilation. Meanwhile, I'm sitting in here in Salt Lake City, where a lovely snow is sifting down, and I'm at the mercy of machines a thousand miles away. I can't touch them in any useful way. This is, of course, my usual condition in many regards, but one forgets how far-flung are his dependencies. Strangers are trying to fix the problem for me. We forget how many strangers assist us every day....

Rat sparks NZ telecoms blackout

Rat sparks NZ telecoms blackout 06/22/2005 02:40 AM
A rat is being partly blamed for a major communications crash which has caused chaos in New Zealand.

IT Role Cited in Blackout

IT Role Cited in Blackout 04/19/2004 12:32 PM
The worst electric power failure in U.S. history could have been avoided in part through better business continuity planning and IT management.

Blaster and the great blackout

Blaster and the great blackout 12/16/2003 12:51 AM
Salon Dec 16 2003 0:02AM ET

Two-Fingered Blackout PowerBook Dropping

Two-Fingered Blackout PowerBook Dropping 03/14/2005 06:09 PM
Glenn Fleishman (~300 words)

I asked Apple to loan me a new PowerBook so I could test first-hand the hardware features they added in the latest refresh a few weeks ago: the scrolling trackpad, the Sudden Motion Sensor for hard drive protection, and increased backlighting for the keyboard. You can read about these features in Apple's marketing materials, but it's nice to test them first hand.

2003 Blackout 's Silver Lining

2003 Blackout 's Silver Lining 06/14/2004 03:38 AM
CBS News Jun 14 2004 8:22AM GMT

Computer trouble affected blackout

Computer trouble affected blackout 11/19/2003 10:28 PM
AP via Seattle Post Intelligencer Nov 19 2003 9:45PM ET

Zombie PC army responsible for big name
web blackout

Zombie PC army responsible for big name
web blackout 06/17/2004 05:12 AM
Silicon.com Jun 17 2004 9:05AM GMT

Microsoft Money blackout approaching day
four

Microsoft Money blackout approaching day
four 07/29/2004 10:17 PM
A server glitch has shut out a "subset" of Microsoft Money users from accessing their online financial files.

Blackout hits major Web sites

Blackout hits major Web sites 06/15/2004 03:03 PM
Google, Microsoft.com and others go dark after an apparent outage of Akamai's domain name server system. Yahoo Mail still patchy.

Utilities Still Fumbling a Year After
Blackout

Utilities Still Fumbling a Year After
Blackout 08/15/2004 01:42 PM
Reuters via Wired News Aug 15 2004 4:31PM GMT

Snake Triggers Blackout in Honduras (AP)

Snake Triggers Blackout in Honduras (AP) 05/19/2004 07:24 PM
AP - A boa constrictor triggered a 15-minute nationwide blackout when it slithered into a generator at a major hydroelectric plant, officials said Wednesday.

Software bug contributed to 2003
blackout

Software bug contributed to 2003
blackout 02/13/2004 12:46 AM
A flaw in General Electric's management system contributed to last August 14th's blackout.

Northeast Blackout Caused By A Software
Bug

Northeast Blackout Caused By A Software
Bug 02/11/2004 11:07 PM
Turns out after all the various speculation on reasons, the big northeast blackout from last summer was the result of a software bug that was only just discovered - and not (as many had speculated) from the Blaster worm that was going around at the time. The bug meant that an alarm that should have been triggered never went off - leading to a series of problems that went unnoticed until it was too late.

Blaster worm not responsible for NE
blackout

Blaster worm not responsible for NE
blackout 04/09/2004 04:13 PM
When the Northeast had a massive power outage lasting 16+ hours, there was speculation that it was caused by the Blaster (MSBlast) worm. Fortunately, this was not the case...

Cardinals impose media blackout

Cardinals impose media blackout 04/09/2005 09:37 AM
Roman Catholic Cardinals decide not to speak to the press until Pope John Paul II's successor is chosen.

Blackout Hits Athens Month Before Games
(AP)

Blackout Hits Athens Month Before Games
(AP) 07/12/2004 02:12 PM
AP - The worst blackout in more than a decade hit Athens and southern Greece on Monday, leaving millions sweltering in a heat wave and raising concerns about whether the lights will go out at next month's Olympics.

Prosecutor orders Greece blackout probe

Prosecutor orders Greece blackout probe 07/13/2004 03:28 PM

Blackout Highlights Business-Continuity
Drivers

Blackout Highlights Business-Continuity
Drivers 04/09/2004 03:58 PM
An investigative report issued by the U.S. and Canadian governments surrounding the worst power failure in U.S. history is shedding light on the importance of business-continuity planning through findings that the electric-system catastrophe could have been prevented.

Analysts: Continuity Lessons From
Blackout, Disasters

Analysts: Continuity Lessons From
Blackout, Disasters 08/13/2004 09:17 PM
Changes in the storage market for lower-cost data replication could be a part of improving business continuity plans. However, analysts say many IT managers and CIOs still don't heed the disaster warnings.

Blackout Hits Athens Month Before
Olympics (AP)

Blackout Hits Athens Month Before
Olympics (AP) 07/12/2004 08:48 PM
AP - The worst blackout in more than a decade hit Athens and southern Greece on Monday, leaving millions sweltering in a heat wave and raising concerns about whether the lights will go out at next month's Olympics.

SecurityFocus HOME News: Software Bug
Contributed to Blackout

SecurityFocus HOME News: Software Bug
Contributed to Blackout 02/13/2004 12:48 AM
http://www.securityfocus.com/news/8016 I KNEW IT!!!!!!!!!: A previously-unknown software flaw in a widely-deployed General Electric energy management system contributed to the devastating scope of the August 14th northeastern U.S. blackout, industry officials revealed this week. The bug in GE Energy's XA/21 system was discovered in an intensive code audit conducted by GE and a contractor in the weeks following the blackout, according to FirstEnergy Corp., the Ohio utility...

2003 blackout harbinger of future havoc,
CSIS says

2003 blackout harbinger of future havoc,
CSIS says 04/26/2004 01:05 PM
globetechnology.com Apr 26 2004 5:06PM GMT
Grok Description matches for Tracking the Blackout bug
GrokA matches for Tracking the Blackout bug

Tracking the Blackout bug

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