Alright I don't know about you guys but I hate seeing my log clogged up by multi hacks and raids. What I suggest is having them stack somewhat like artifacts do.
Example:
Message from (Player Name)
10-35 minutes ago (Player name) hacked into your database and stole 12,578 research points)
(17)
Just to keep the log uncluttered while still getting the message across.

They do stack up but only when you get the same artifact/mineral/research from that raid/hack. Other than that there's no other way of stacking different raid/hack amount.

2x
1 day, 19 hours - 1 day, 19 hours ago From: Rebel4561
417 Research Points were hacked and stolen from your database by Rebel4561

What I'm saying is, (if this is possible) Add the amount of research/minerals stolen, make it one message then say the time frame and amount of hacks it took to steal x amount of research/minerals

the issue that i can forsee in this is that the game isnt going to be keeping a running tally of actions done against you by player X, player Y and player Z etc.. whos to say that they will all be done doing X action against you..

what I can see as a possibility, would be to total up your hourly loss from player x, and give you the one notice, same for player Y

This would be very helpfull. When I get alerted I dont want lots of spam in my log about how much each individual raid/hack took. Just compile it into one neat total. Im sure it wouldn't be hard to get the game to simply add each hack/raid together.

From a programing perspective this could be a huge pain, and would cause more load on the server for every calculation that would have to be run.

Would be nice, yes... but a huge -1 for me

things are fine as is. -1

The easiest (programming wise) solution: (horrible psudo code, too lazy to write proper code, but should give the idea)
when a hack/raid msg is to be generated.
If last-entry-in-log is a hack/raid from same player.
then change last entry to +1 count, +whatever amount stolen.
else
generate new entry


the better one would be looking a bit deeper into the log for entries, possibly cycle through all entries in the last x min to check if there is such a "matching" entry to update.