This is the continuation of the DDOS attack, where the subject of (((Junkerman))) was brought up. Now Voat is in lockdown mode, they cannot straight bring down Voat directly. So they still attack periodically. At first, it was about 45 minutes everyday or so. Now it is happening more frequently, several times a day. What we are seeing is some innocent and some not-so-innocent users pushing the usual Voat-is-done narrative :-).
It seems to me that often the top level voat.co is blocked but something like voat.co/v/all/new works. I’ve mentioned this elsewhere and others agreed.
I got an error from CloudFlare once. If voat is using CF, isn’t that supposed to block denial of service.
It’s like some flakey code designed to make us give up and go away. Yesterday I’d look at a post, go back, and got the message. Did my trick and got in, but that happened again several times.
If we are all logged in nowadays, wouldn’t it be simple to see which user is fucking around and delete the account?
If any account is deleted, there will be outcry that Voat is censoring certain users. But if one were to detect the troublemakers, how would you do that? How would you distinguish those from genuine users? What if they adapt to the tactic to remain hidden below certain threshold?
That url error has been reported quite a number of times. Yeah it can be very annoying.
How about this: keep a table of user and last access time and request counter. As a page is requested if the last time was over, just for example, 5 seconds ago, clear the counter, otherwise bump it up. If the count gets too high consider that a malicious user. Maybe just ignore subsequent requests for an hour or log them out, versus deleting the account.
Deleting an account is completely unnecessary and a ridiculous over-reaction when you can just disable the account.
Side-note, the argument that there would be "outcry" if an account is deleted is ridiculous. 80% of the users have already left the platform due to this issue, and the void grows daily. The only people who have any "outrage" these days are Joint Task Force Tel Aviv and Langley, AKA SBBH - and let's face it, they're Voat's terminal cancer so who gives a fuck what those autistic faggots complain about.
view the rest of the comments →
MadWorld ago
This is the continuation of the DDOS attack, where the subject of (((Junkerman))) was brought up. Now Voat is in lockdown mode, they cannot straight bring down Voat directly. So they still attack periodically. At first, it was about 45 minutes everyday or so. Now it is happening more frequently, several times a day. What we are seeing is some innocent and some not-so-innocent users pushing the usual Voat-is-done narrative :-).
sore_ass_losers ago
I don’t believe it’s a DDOS. It’s so flakey:
It seems to me that often the top level voat.co is blocked but something like voat.co/v/all/new works. I’ve mentioned this elsewhere and others agreed.
I got an error from CloudFlare once. If voat is using CF, isn’t that supposed to block denial of service.
It’s like some flakey code designed to make us give up and go away. Yesterday I’d look at a post, go back, and got the message. Did my trick and got in, but that happened again several times.
If we are all logged in nowadays, wouldn’t it be simple to see which user is fucking around and delete the account?
MadWorld ago
If any account is deleted, there will be outcry that Voat is censoring certain users. But if one were to detect the troublemakers, how would you do that? How would you distinguish those from genuine users? What if they adapt to the tactic to remain hidden below certain threshold?
That url error has been reported quite a number of times. Yeah it can be very annoying.
sore_ass_losers ago
How about this: keep a table of user and last access time and request counter. As a page is requested if the last time was over, just for example, 5 seconds ago, clear the counter, otherwise bump it up. If the count gets too high consider that a malicious user. Maybe just ignore subsequent requests for an hour or log them out, versus deleting the account.
Would something like that fit in and work?
@Nosfewratsjews
Nosfewratsjews ago
Deleting an account is completely unnecessary and a ridiculous over-reaction when you can just disable the account.
Side-note, the argument that there would be "outcry" if an account is deleted is ridiculous. 80% of the users have already left the platform due to this issue, and the void grows daily. The only people who have any "outrage" these days are Joint Task Force Tel Aviv and Langley, AKA SBBH - and let's face it, they're Voat's terminal cancer so who gives a fuck what those autistic faggots complain about.
@MadWorld
sore_ass_losers ago
Could a logged-in DDOS attack use a stolen name/password? I suppose weak passwords could be guessed or keyloggers could be installed.
Okay, disable is better.