Buckle up. Voat is currently being hit with a malicious attack. This couldn't have possibly happened at a worse time for me personally and I may have to put Voat into lockdown mode or even set it to Read Only. Perhaps we will resurrect the
bit privilege checking goat (you know you miss having your bits privilege checked).
I'm hoping that the code is in a good enough place to handle a majority of the incoming traffic, but expect slow responses.
I will try my best to keep Voat online. Wish me luck.
Edit:
I'm still waiting for the main attack. Every DDOS we've been hit with before follows a pattern of probing exploits, quiet time, then the full attack. So we will see, but waiting is the hardest part
Edit 2:
As of now I feel they've postponed. After taking us down two times the morning of this announcement, I've seen no further activity. A temporary win I suppose.
https://voat.co/v/announcements/1330806
view the rest of the comments →
OneTiredThrowaway ago
I would like to suggest, @PuttItOut, that there be something put on the front page, stickied, that names the specific likely (re: definitely) suspects, e.g. ShariaBlue. As such, even if you have to switch to read-only mode, there's still a nice message explaining who is responsible for this and why they are doing it.
Best part about that is that even if you have to force it to read-only mode, the one thing they don't want on the front page is the front page.
Bonus points for mentioning the election and "caravan" (re: invasion) directly.