Woohoo, I've been certified! Thanks to all those who took the time to give me a certification and special thanks to mdekkers who tipped the scale, allowing me to participate more. Now I think Journeyer is a bit high myself but I'm not complaining.
The past few days I've tried to help drive a Mozilla bug confirmation attempt. It all started after when I was hanging out on #mozillazine and someone mentioned there should be a #kill-unco channel. So I made one.
A few days later this lead to Bugzilla being overwhelmed by unnecessarily large queries, slowing things down for other people. Hopefully I'll be able to set up some sort of static caching script to help ease the problem I helped create....
A brief appeal - if you can offer additional help to the confirmation process it will be much appreciated. A staggering number of new bugs are being filed all the time as Mozilla approaches 1.0 and the only hope of keeping up is with more people weeding out the bad reports from the good ones. You don't need to be an expert to help get a bug confirmed - you just need to have a recent build (preferably a nightly build as bugs in the releases are often fixed quickly).
Also if you have filed a bug with an old build, can you check that it is still reproducable in new one? If not resolving worksforme (many people don't realise that they can resolve bugs they have filed themselves). There are also a hardcore collection of untouched unconfirmed gtkmozembed bugs forming that many confirmers lack the tech to reproduce. So anyone who can help to clear those wins ...umm... a less buggy browser!