I might recommend at least temporarily turning off anonymous commenting; these things tend to go in waves where a few users get hit pretty hard (though 80 is a lot, ow) and then they slack off or move on to a different target.
Basically the hazards of getting spammed are: Your time and energy gets spent on dealing with the spam. There's a small risk that a legit comment might get lost in the spam (either something you needed to deal with gets overlooked, or an innocent passerby gets reported, or both; since there's human review of spam after it's reported, generally low-volume mis-reports are disregarded.) If the spam remains up, the spammers' mothership might think your journal or entry is an easy target and start sending more. Ew, spam in your journal.
A number of standalone blog sites do get compromised by spammers and used to host gnarly things themselves, but DW (and LJ) are less vulnerable to that -- the codebase is well hardened, there's not as much ability to customize using methods that are vulnerable to attack.
(Hilariously, I had to pause in writing this comment because something was spamming up my LJ. I hate spammers so much.)
no subject
I might recommend at least temporarily turning off anonymous commenting; these things tend to go in waves where a few users get hit pretty hard (though 80 is a lot, ow) and then they slack off or move on to a different target.
Basically the hazards of getting spammed are:
Your time and energy gets spent on dealing with the spam.
There's a small risk that a legit comment might get lost in the spam (either something you needed to deal with gets overlooked, or an innocent passerby gets reported, or both; since there's human review of spam after it's reported, generally low-volume mis-reports are disregarded.)
If the spam remains up, the spammers' mothership might think your journal or entry is an easy target and start sending more.
Ew, spam in your journal.
A number of standalone blog sites do get compromised by spammers and used to host gnarly things themselves, but DW (and LJ) are less vulnerable to that -- the codebase is well hardened, there's not as much ability to customize using methods that are vulnerable to attack.
(Hilariously, I had to pause in writing this comment because something was spamming up my LJ. I hate spammers so much.)