She create botnet of crawlers. Botnet activity resulted in huge spike of traffic. Traffic cost money for client. Every AWS instance have a protection against traffic spikes, to prevent bankruption of client in case of DDoS or similar attacks. AWS intentionally turned off all protection against traffic overdrawing for Parler instance. AWS did not shut or slow down instances with crawlers or filter external IPs who generated that traffic spike. All that openly described by the girl in her twitter without any fear of legal charges.
So, she knew for shure that:
any legal charges for such activity will be dropped by authorities
it will be possible to do the job in that bruteforce way, because AWS dropped all protections.
I'm not saying that did not happen. But, if you wrote up how it was done and elaborate on it with sources (maybe), it could help non-techies understand exactly what happened.
To get something from service you have to make request.
Service will reply with response containing requested data.
To get a lot of data you have to make a lot of requests and receive a lot of responses.
Every time you make a request you consume service CPU and traffic.
CPU and traffic is what services like AWS sold for money.
If you continuosly make a lot of requests back-to-back, creating requests storm, service instance at AWS will spend all its CPU time and traffic for dealing with your storm of requests and other users would have to wait for their responses for a long time. Service will be unavailable for ordinary users. This is how Denial of Service attack (DoS) works.
Service could have multiple CPUs and have thick traffic channel (much more than you could afford), so you have to make your requests storm from multiple instances (using your shills or botnet) to grab all CPUs and all traffic. It is Didtributed Denial of Service attack (DDoS).
To prevent DoS and DDoS any company like AWS have a protection. It detects storm of requests and drop them or slow down the stream.
To quickly download huge amount of posts and comments you have to make a huge amount of similar requests fast using multiple copies of your crawler, working from different places simultaneously. This have no any difference from DDoS, so, in normal situation AWS DDoS protection will be triggered and will not allow your crawlers to bother service, so you will not be able to download all data and create a traffic spike. If you suddenly did it, it means that DDoS protection was disabled.
All the sources are in any book or article about how web works.
All the proofs of prepared and organized DDoS is on the link in OP.
Thank you for explaining further. So, you believe Amazon may have intentionally let this dyke pull all the data and that Amazon essentially turned off the DDOS protections for Parler so she could do it?
Indeed. And Amazon openly published the exact time and date of turning off Parler servers in advace. They don't do that when shutting down instances even if they break some written or unwritten rules. This is information for customers only. It was definitely a deadline for the mob of crawlers to work faster.
Just think about it - Amazon want to "deplatform" a very "dangerous" for "people" service. They can do it immidiately after they make that decision without any problems. But instead Amazon issue a political proclamation with exact datetime, giving SJWs mob time to grab all data.
There is nothing to investigate at all.
She create botnet of crawlers. Botnet activity resulted in huge spike of traffic. Traffic cost money for client. Every AWS instance have a protection against traffic spikes, to prevent bankruption of client in case of DDoS or similar attacks. AWS intentionally turned off all protection against traffic overdrawing for Parler instance. AWS did not shut or slow down instances with crawlers or filter external IPs who generated that traffic spike. All that openly described by the girl in her twitter without any fear of legal charges.
So, she knew for shure that:
I'm not saying that did not happen. But, if you wrote up how it was done and elaborate on it with sources (maybe), it could help non-techies understand exactly what happened.
Techical stuff, as simple, as possible:
To get something from service you have to make request.
Service will reply with response containing requested data.
To get a lot of data you have to make a lot of requests and receive a lot of responses.
Every time you make a request you consume service CPU and traffic.
CPU and traffic is what services like AWS sold for money.
If you continuosly make a lot of requests back-to-back, creating requests storm, service instance at AWS will spend all its CPU time and traffic for dealing with your storm of requests and other users would have to wait for their responses for a long time. Service will be unavailable for ordinary users. This is how Denial of Service attack (DoS) works.
Service could have multiple CPUs and have thick traffic channel (much more than you could afford), so you have to make your requests storm from multiple instances (using your shills or botnet) to grab all CPUs and all traffic. It is Didtributed Denial of Service attack (DDoS).
To prevent DoS and DDoS any company like AWS have a protection. It detects storm of requests and drop them or slow down the stream.
To quickly download huge amount of posts and comments you have to make a huge amount of similar requests fast using multiple copies of your crawler, working from different places simultaneously. This have no any difference from DDoS, so, in normal situation AWS DDoS protection will be triggered and will not allow your crawlers to bother service, so you will not be able to download all data and create a traffic spike. If you suddenly did it, it means that DDoS protection was disabled.
All the sources are in any book or article about how web works.
All the proofs of prepared and organized DDoS is on the link in OP.
Thank you for explaining further. So, you believe Amazon may have intentionally let this dyke pull all the data and that Amazon essentially turned off the DDOS protections for Parler so she could do it?
Indeed. And Amazon openly published the exact time and date of turning off Parler servers in advace. They don't do that when shutting down instances even if they break some written or unwritten rules. This is information for customers only. It was definitely a deadline for the mob of crawlers to work faster.
Just think about it - Amazon want to "deplatform" a very "dangerous" for "people" service. They can do it immidiately after they make that decision without any problems. But instead Amazon issue a political proclamation with exact datetime, giving SJWs mob time to grab all data.
Not a girl
Whatever. I'm standard rude intolerant barbarian Russian white suprematist, so I'm not very into all that rainbow gender stuff. :)