I think a lot of modders already have some crashes stored inside the OpenEye crashes db that aren't fixable on their side.
Maybe a feature could be added that crashes could be marked as 'ignore' by telling it to the IRC bot (by crash hash). That way new crashes from that type wouldn't be pinged anymore by the IRC bot and not all crashes are visible anymore on the website via a regular search (maybe they do if a checkbox for that is checked).

No. The database isn't some tool to see who is crashing lots and who isn't. It's there to collect the information and let people deal with it as they wish.

I don't want to add anything into the system that could mean that vital information is lost. One developer might decide to 'ignore' a crash, but it might be vital information to another developer.

There's also a very strong case that any 'user caused issues' are still issues. The developer should consider dealing with them in a better way, presenting the information to the user in a better way.etc.

No crash is necessarily 'assigned' to one particular mod. It tries to detect which mods have some involvement based on the stacktrace and the mod states, but it never knows for sure what the cause of a crash was. Nobody should be given the permissions to 'hide' a crash because it might not be their mod causing it.

OpenEye isn't a tool for blame, and frustratingly some developers appear to be butt hurt when they see their mod listed as a possible cause of a crash. It's there to collect information about what is crashing and what isn't, nothing more.