Comment 2 for bug 1158979

Seems like a reasonable plan, but for memory reasons I feel like we should only have one model. Schema could look like this:

id:str (if any)
message:str
severity:int (define 0 as "notification", 1 as "warning", 2 as "fatal error", or maybe even get more fine-grained if necessary)
seen:bool

Then the client could decide how to display each level of severity and how to determine if they were acknowledged or not.

Another nice thing about doing this in a deemodel is that different client apps would all have the same seen state, so you wouldn't get the same error bothering you from multiple apps. just one app would tell you the error first.

Are you wanting this landed in raring or is this a trunk-next idea?