- Joined
- Jun 16, 2021
Been dealing with so many 429s and still am, but now the contentless pages have returned. No VPN, on desktop with only IPv4.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I have no information on how this happens. I don't know what people are doing to accomplish it.Been dealing with so many 429s and still am, but now the contentless pages have returned. No VPN, on desktop with only IPv4.
I can provide plenty details potentially relevant to the issue for you at a later time. The contentless pages aren't too big of a deal, it's the 429s that push me onto Tor.I have no information on how this happens. I don't know what people are doing to accomplish it.
Not troonbux. Tax payer bux.
You can bet your ass these freaks live on welfare just like the legendary anti-work reddit mod on Fox News.
So long as they receive any kind of social aid, they will always dedicate part of it to attacking this website until their tugboat runs out, the zeitgeist changes or the website actually falls.
Frankly, I am amazed Null didn't had a hitjob on him yet.
They have pull on banks, paypal, all relevant social media, cloudflare and FUCKING TIER 1 PROVIDERS!
You'd think that showing his face online would be enough for full scale weaponized autism to get him doxxed by now.
Good doggy, I thought i was the only one receiving these, glad i'm the only one who got pozzed like this.We've been under near-constant D/DoS attacks for the last few days. The system has mostly been able to handle it with some config tweaks, but the net was cast too wide, which was causing 429 errors. I've identified the problem and you should no longer see 429 errors.
Just now, I applied a small update to the KiwiFlare which should have a big change. I believe I have improved the system's ability to handle concurrency. I had observed that the CPUs were not pegged (meaning, they were well below 100% utilization), but there was another bottleneck, which I believe was poor concurrency causing all 48 cores to block when receiving thousands of requests a second.
In my local tests, I had previously been able to cause DDoS loads of 30,000+ requests before seeing issues. However, with the new improvement, I was not able to reproduce the issue with any number of requests before being bottlenecked by socket counts.
Edit: There's a very heavy attack that I'm using to experiment with config options.
Please report if you receive an Error 403, or Error 429, while using the website.
I need to know if you are using a VPN or public network as well. If you are using a VPN, please say which one.
Error 429, here. I am using the VPN service that comes with Norton 360 - and I had wondered if that was causing the errors. Glad to see you're on top of things, chief.Please report if you receive an Error 403, or Error 429, while using the website.
I need to know if you are using a VPN or public network as well. If you are using a VPN, please say which one.
Yesterday I got a few 429s (over the weekend got a couple 504s, a 502, and a short while when there was just no connect at all ("cannot find server")).I have no information on how this happens. I don't know what people are doing to accomplish it.
I don't use Tor, but even in mobile it's really snappy.Feels faster to me, could just be placebo though. Tor sites working nice though.
Very nice. It's handling it well. The mitigation is also having the semi-optimal result that instead of failing entirely, service simply slightly degrades. Daily dilation of stinkditch is pathetic.We've been under near-constant D/DoS attacks for the last few days. The system has mostly been able to handle it with some config tweaks, but the net was cast too wide, which was causing 429 errors. I've identified the problem and you should no longer see 429 errors.