We should add a pref that indicates that submitted crash reports should be auto-priority. The server-side would give these reports priority by default. This would be for developers/testers who know they want to see their reports.
don't make it a pref. let people register email addresses on the server as auto priority. then people submitting reports w/ those email addresses get auto priority.
That's much more of a pain in the ass. Also, we're considering getting rid of email collecting.
anything client side will be abused eventually and become useless.
(In reply to comment #3) > anything client side will be abused eventually and become useless. Not if we don't advertise it. For 99% of users, they won't know it even exists and that's good enough for me.
Yeah, I don't think it's that big a deal. We were handling 100% of crash reports through the beta period of Firefox 3 without any problems, so even if a few million people turn this on, we should be fine.
Do you guys know what this flag will be named?
I haven't touched anything yet, so pick a name!
This would require some changes to the way that priority jobs are handled. Currently, identification of priority jobs is handled through the WebApp talking to the database. The monitor sees these requests and queues the jobs appropriately. To keep the collector database free, we'd have to devise another channel of communication with the monitor for identification of priority jobs - likely via the file system. The latest version of monitor is much more modular in the way that it handles priority jobs. Adding this secondary communication channel would not be particularly disruptive.
Y'know, the current system seems to be working pretty well.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.