Anonymous ID: 5e0d7c Aug. 11, 2021, 5:45 p.m. No.14329899   🗄️.is 🔗kun   >>9917 >>9918

>>14329369 lb

Update

Trackers are connecting and there is a single seeder, either the seeding is/was on hold due to "stolen" drives or CM pivoting or glowing jrlives tpb style larp. The certs here are about to expire again, same as 3 months ago. There will be impacts, recaptcha with the tick link at the top of the page and hope that we do not lose the ability to post/captcha. FJ discord might be a good place to regroup if we cannot post again. I have tried to reach out to Jim last week and again now, but am a nobody so who knows.

Anonymous ID: 5e0d7c Aug. 11, 2021, 5:54 p.m. No.14330008   🗄️.is 🔗kun   >>0095

>>14329917

That's what I was thinking 3 months ago, what we are assuming is that the cert provider auto provides a new cert, and then it is auto applied to the servers and then services restarted. It didn't work well last time if that was the case, and with all the other stuff going on it is totally equally possible that either it is meant to expire (and was 3 months ago but timings changed) or they will miss it due to everything else going on. It is also possible that level of devops automation is vulnerable to attack and would just break again like it did 3 months ago.

>>14329918

If we cannot validate a connection to sys.8kun.top we will lose the ability to captcha and therefore post, happened 3 months ago when this same situation happened. DNS fuckery will not work if the connection cannot be validated, sure you can load the captcha page but it will not validate even if it shows passed you still will not be able to post.

Anonymous ID: 5e0d7c Aug. 11, 2021, 6:20 p.m. No.14330251   🗄️.is 🔗kun

>>14330134

If we manage to bake another bread, it would be wise to keep the noise to a minimum to try and make it last as long as possible. It would be an 8kun xmas miracle if it actually happened, but worth putting out there. Lets see what happens.