blog.errorhelp.com - Musings and announcements regarding the bug.gd ErrorHelp search engine.

Archive for November, 2007

Coverage summary page

Monday, November 19th, 2007

We’ve been so busy at bug.gd the past two weeks that I haven’t had a chance to catch up on all the reviews we had.

You can see why we were overwhelmed on the summary page of our news coverage:

http://blog.bug.gd/buggd-in-the-news/

There’s been a lots of discussion on sites like TechCrunch, Lifehacker, and many, many more.

We have some new tools in the works that make life even easier for computer users, so expect that list to get even bigger soon.

Thank you guys for spreading the word. We’d love to see a world where no one was blocked behind a fixed bug.

Accidental double email

Monday, November 19th, 2007

Today someone reported that they received two emails instead of one. If this affected you, don’t worry– it was a temporary glitch that’s been resolved.

Of course, please continue to report issues to bugs@bug.gd if you run into anything unexpected. Thanks for your support during our beta period, and sorry for any confusion.

bug.gd features released Nov-5

Thursday, November 8th, 2007

As you might have noticed, we’ve released a few new features to bug.gd. I promised to include those here.

The biggest items:

We’d love to hear from you here (or at bugs@bug.gd). What do you think?

bug.gd on KillerStartups

Thursday, November 1st, 2007

KillerStartups wrote the first review of bug.gd and we were very pleased by the coverage. In fact, I believe we killed their site for a time when we directly linked to their review during the Digg deluge.

You will be contacted in 48 hours to see how you dealt with the situation, and if you solved you will be asked to submit details on how you did.

It’s great to see that the first reviewer understood bug.gd right away. Some reviewers didn’t catch-on.

Bug.gd is a great site, but maybe it could include some Web 2.0 features.

We have a logo with a reflection! Oh, is there more to Web 2.0?

Users could have a user name and a history of errors that they have dealt with.

For beta, we wanted to see how well we could avoid requiring a login and password. If people really like the idea of non-anonymous names, we can add them, but it might distract a bit from our core search.

Other users could request their knowledge when they deal with a similar error message and maybe they could come to a solution even quicker.

Something like this is being considered. (If you also like this idea, please comment here.)

Bug.gd could feature an articles section on error solutions that users could take advantage of to try and fix their computer problems.

Once we get in the groove, we’ll likely write about the most common error searches. We expect this would be more like trivia for the software industry rather than anything users would enjoy. The average person isn’t so keen on errors unless one is staring them in the face. As such, our focus is almost exclusively on getting a specific error out of your way.

Thanks again to KillerStartups for such rapid coverage and the excellent review.

bug.gd on Digg

Thursday, November 1st, 2007

We’ve received lots of questions, but we’re way behind on responding to blog articles. Let’s see…

I thought I’d take a moment to respond to 5 of the ~90 comments on Digg. (We’ll ignore the humorous comments about our temporary downtime during the Digg deluge. We’re only human!)

anyone notice the logo reflection? — NavS

Hmmmm…

“If you’d like bug.gd for your intranet, please email corp@bug.gd. Full licenses are very cheap and begin around $4999.”
Cheap? $4999? That’s a joke right? — unknamed

Obviously it’s no joke, though the average diggster may not grok it. We are, though, getting emails from IT infrastructure managers and IT outsourcers who “get it” and see how this can be another great tool in their arsenal. Since every large company has custom applications and errors specific to their company and business, it can be a huge timesaver for employees to find other employees with similar errors/solutions. The cost is minor especially with no per-user or concurrent license fees.

In the future we’ll be adding tools that allow your company to integrate it with their software build systems, websites, etc. Why should company engineers and new hires have to send out “has anyone seen this error?” emails? Your corporation should never solve a problem more than once! Get them back to work as quickly as you can.

This sounds link splunk… http://www.splunk.com/hm2k

Not so much. Splunk has a great selection of tools– but nothing as simple and direct as bug.gd. I think you’d agree if you’ve used any of the splunk tools.

I don’t see how this is better than just googling the error which anyone with half a brain can do — SeanNorton

Searching for an error message via Google will work sometimes, but Google’s not really designed for that sort of thing. How many times do you end up getting results where someone says “I solved it!” in a forum without an explanation? How many times do you see errors posted but with the results hidden behind a pay site that fooled googlebot? How many times do you have to fix a multi-line error to squeeze it into the “keyword” search boxes?

We were sick of not finding solutions when we know people have been down a path before. If we all work together, the computing world will be a much nicer place.

Sure, some people post in forums or newsgroups. A rare few Samaritans blog about their error solutions. We believe, though, that the number of people posting those are far outnumbered by those who search/solve and never tell a soul. (Let’s stop doing that, please!) bug.gd sends a gentle reminder so you’ll remember to do the right thing.

Should have been included under ‘Favourites’ on IE7 for Vista. — Vazelos

No argument here!