I thought we had fixed that bug in the past. But apparently there are still some situations where it can happen.
It's just a UI bug. Everytime a notification is marked as read, the number goes down by one. If you manage to trigger "mark as read" multiple times for the same notification (could happen with slow network maybe), there's a possibility of the number going negative.
On the next page refresh it will show the real count again.
