Thank you, Baker. Have a good night.
It is sheer speculation that only 1% of the deaths are showing up on VAERS.
That may have been true historically but maybe not now. Nobody really knows.
You must have hit a site other than 8kun due to the DNS fuckery.
Found: Alternative IP address block for 8kun
So I cycled through all of the 8kun IP addresses to see if one or more of them actually work reliably instead of going dead every so often. Unfortunately, they all have a failure rate ranging from 1/3 to 1/20, varying over time. I don't know if geographical location is a factor. The end result is that your 8kun client may lock up occasionally, necessitating a reload. You may also get the "deleted or pruned" error message. These are the IP addresses currently assigned to 8kun:
94.103.81.80, 94.103.82.74, 94.103.94.73, 193.178.169.19, 195.2.92.96, 195.2.93.193
I have long suspected that Vanwanet has an entire address block that can be used to access 8kun. There are two other sites that I know to be Vanwanet clients, qagg.news (23.163.176.200) and dailystormer.su (23.163.176.229). Digging further, I find that the entire block of addresses from 23.163.176.200 to 23.163.176.230 inclusive belong to Vanwanet and any of them may be used for 8kun. The few that I tested extensively work reliably, unlike the IP addresses assigned to 8kun by the Vanwanet DNS server.
We can speculate as to why this is. Is Vanwanet deliberately sabotaging 8kun? Or is it the DDoS protection service which, as far as I know, is still DDoS-Guard (https://ddos-guard.net)?
Additionally, the posting server at sys.8kun.top has been slow to respond. The 8kun client is impatient and times out too soon with an error message saying that the "server took too long to respond". I'm experimenting to determine if switching the posting server to the alternative address block will help with that.
Starting to see a lot of reports about 404 errors.
This is related to the issue that I posted about here: >>14870242
The "deleted or pruned" error is caused by the 404.
Nicked.
So November 22 is another datefag date?
>Do we have a workaround?
Site is working fine for me. And, yes, there is a workaround if you can change your "hosts" file.
Pick a random IP address in the range 23.163.176.[200-230]
testing
Okay. Can still post via 185.165.190.88 for sys.8kun.top so it isn't a posting problem.
All of the IP addresses for 8kun.top are down. So it is unlikely that anybody will see this message unless you took heed of my warning to bypass the DNS and switch the IP address to the range that I specified. Anybody who has done that should be able to post here. But nobody is posting. I'm all alone, you suckers.
Well, a few people have posted but I gather that they can't even see their own post.
Maybe it's a DDoS but it can be bypassed.
Looks like the board is back up.
This is a follow-up to my previous post: >>14870242
I'm retesting all of the IP addresses and, so far, it does appear that the site is back to normal.
Well, what do you say about the site going completely off-line for a half-hour soon after my post? And, when it comes back up, it seems to be fixed? After two or three days of intermittent errors? Riddle me that.
>This isn't even the first time shit like this has happened. More like the 30th.
Pretty much. We always look for a way around it though. Now we're supposed to do nothing? Screw that.
Proving yet again that Democrats are communists.
The site went down for about a half-hour between 11:00 and 11:30.
It seems to be back to normal. I'm only catching an occasional failure to connect whereas the failure rate was as 30% for the past two days.
>>Pick a random IP address in the range 23.163.176.[200-230]
>"domain not found"
You can't just use an IP address like https://23.163.176.200 in the browser. That won't work with a CDN. The change has to be made at the level of the "hosts" file or some other mechanism to bypass the DNS resolver.
Maybe it's ebola. How the fuck would you know that it's not? Or pick any one of a thousand viruses that are known to cause similar symptoms. Why do you assume that it's Covid? Oh, I see, that's the one that gets all of the publicity.
>please no, not the hosts file solution again !
Yeh. I could offer a better way but nobody listens to me.
You might consider the possibility that the vaxxed may have lost their souls and are therefore demonic. Maybe it's shedding or maybe it's a bad aura.
Are you wishing bad karma on those around you? Not good.
>Only because those around me wished bad karma on me first.
That may be the case but Q did not assemble us here to wish ill on our fellow humans. We must stand tall.
>Some people need to be pushed to the precipice to see the light.
Winning over one NPC at a time. And waiting for that final domino to fall.
We still get weird comms but what do you mean by weird?
Yeah, Q's b'day. Here is an unfinished work that I abandoned some time ago. It's a record of the conversation that went on around Q from October 28 to November 2.
https://8chananon.github.io/Q/who-are-anons-1.htm
https://8chananon.github.io/Q/who-are-anons-2.htm
https://8chananon.github.io/Q/who-are-anons-3.htm
https://8chananon.github.io/Q/who-are-anons-4.htm
https://8chananon.github.io/Q/who-are-anons-5.htm
Happy Birthday, Q
Wish you were here. Sniff.