THE HTTPS CERTIFICATE IS NOW BEING USED TO SLOW DOWN SOME SITES
Obviously this site is not affected by this because I knew they’d do this eventually and therefore never used HTTPS even though it is a “one click feature” on this server.
This started happening this morning. The sites will still load, but only after a delay of exactly 23 seconds. This is repeatable across all pages on a site. The delay is obviously timer based.
I tried this across multiple computers and internet providers. The reaction is the same. Clearly a timer is being used to delay page loads, and it is the HTTPS certificate that is holding up the sites. Obviously the objective for this is to discourage hits without actually taking the sites offline. If you do not need https, there is no way you should ever put it on your site. That is why this site does not use that, I knew they’d use that certificate to hang sites when the figured they should.
If you notice a site is behaving like this, and it is https, it is not the site’s fault, it is the fault of those issuing the certificates.
And, a rant. WARNING, this rant is bad.
And if you are responsible enough to realize you should offshore your servers NOW and are actually willing to act on that, here is where you go:
Due to the superior level of service, I highly recommend Orangewebsite. Take your pick:
You need to be set up in Iceland with direct IP. That is the one place you’ll be safe, (actually, there is a vulnerability but Iceland will be the last place to go down.) It eventually will go down. LAST. Flokinet is probably the last host that will go down in Iceland, but Orangewebsite is vastly superior. TAKE YOUR PICK.
And now for the rant. If you are not going to offshore, you deserve this.
If you are not doing anything with your site that involves banking, HTTPS is horse dung, WTF were you thinking when you set up that vulnerability? Who convinced you to be stupid with your news site, which is supposed to be 100 percent publicly available? Oh yes, the MSM TOLD EVERYONE to do it because it was the responsible thing to do, and NO ONE thought it might be a trap to screw them in the future. That is EXACTLY what it is. What? you have to securely send what you are OPENLY posting for the public to see? ARE YOU STUPID? I have a secret. If you are alt media using HTTPS, I think you are. And I sent that secret to you directly and unencrypted. Thanks for reading what I sent to everyone, their dog, and even their dog crap totally unsecurely THE WAY IT SHOULD BE IF IT IS TO BE DISSEMINATED WIDELY. Anyone who sets up HTTPS on an OPEN BROADCAST has got to be some sort of sucker. THEY WILL HANG YOU WITH THAT WHEN THE TIME COMES, THE CERTIFICATE HAS TO BE ISSUED BY THEM OR YOUR SITE WILL NOT LOAD. And you’ll probably wonder how you got cut off, even after you read this. I know I am stating this rudely, I don’t care. If you set up HTTPS and there’s no reason to have it, you deserve it.
STOP MAKING YOURSELF VULNERABLE BY USING B.S. THAT IS CONTROLLED BY THE ENEMY. NO HTTPS. NO ANALYTICS. NO WORDPRESS. AND NOT EVEN DNS. BE RESPONSIBLE AND GO DIRECT IP WITH ABSOLUTELY NOTHING ATTACHED TO IT NOW OR YOU WILL BE GONE and if you lived only on Facebook, Twitter, Blogger, or any other site and you were serious, well, I never considered you serious. This warning is not for you because clearly you did not have the skills needed to make it at all and as a result you are now either dead or dying all the while if you had a lick of sense you’d have at least gotten a bottom dollar shared server and pointed to it from wherever you were while you still had a chance. You would not get direct IP with that but at least you’d get a warning. My warning this time is for those that at least had enough sense to do that.
You need to be set up in Iceland with direct IP. That is the one place you’ll be safe, (actually, there is a vulnerability but Iceland will be the last place to go down.) It eventually will go down. LAST. Flokinet is probably the last host that will go down in Iceland, but Orangewebsite is vastly superior.
Please note: Having a dedicated IP is NOT ENOUGH by itself, you need to configure .htaccess to automatically load direct IP when your domain name is hit, that way people can bookmark it.
comment: yes, the 23 second delay is noticeable …