SoylentNews is people
SoylentNews
[Updated 2018/06/30 15:19:00 UTC. I've received word that "certificate renewed, but hasn't been issued" and that it will be installed as soon as we receive the new cert. Original story follows. --martyb]
We've been up front with the community right from the start... and intend to keep doing so in the future.
Where we are at:
We have encountered an issue with Lets Encrypt (LE), the certificate issuer for the majority of our [sub]domains. Even though we can 'see' these domains from any number of different servers... for some unknown reason, LE fails to see them. So, at the moment, we are unable to get them to generate certs for us.
Separately, the cert for soylentnews.org is handled by Gandhi. As far as I understand it (and I'm no sysadmin so take this with a healthy dose of salt) there are only two members of our staff who have the ability to update that cert. (We obviously don't want to let world+dog have access to that, right? My guess is that at that time, having a couple people seemed sufficiently redundant and secure).
What it means to you:
You may encounter a warning from your browser when trying to access the site that a certificate has expired. I cannot speak for all browsers, but I've generally seen that along with the warning is an option to trust the cert anyway. (Note: along with allowing that exception, I've sen at least one browser default a checkbox to make the exception permanent. It's entirely up to you, but I see no reason to make it a permanent exception at this point.)
We are working on it, and obviously hope to have things straightened out sooner than later! On the other hand, should things go sideways, I want to keep the community informed about what's up, what's happening, and what you can expect.
Checking status:
If you would like another means to check on the status of the certs, Comodo makes it easy with queries such as these:
https://crt.sh/?q=soylentnews.org
https://crt.sh/?q=%%25soylentnews.org
https://crt.sh/?q=sylnt.us
https://crt.sh/?q=%%25sylnt.us
tl;dr:
If the site becomes unavailable because of an expired cert, yeah, we know and we're working on it. Accept a temporary exception in your browser and we'll let you now when things are back to normal.
--martyb
P.S. Our Editor-in-Chief, janrinok, is currently undergoing preparations for a medical procedure... it's hard to say at this point, but it's likely he may be unavailable to help with the site for a couple weeks. Please join me in wishing him well for the procedure and for a speedy recovery!
(Score: 3, Interesting) by The Mighty Buzzard on Saturday June 30 2018, @03:39PM (4 children)
Weird. SN renders fast as hell on everything I've ever tried it on. How old are we talking exactly?
My rights don't end where your fear begins.
(Score: 0) by Anonymous Coward on Saturday June 30 2018, @08:51PM
I've noticed long loading times for SN on some webkitgtk-based browsers, but not super recently, seemed to be fixed about 6 months to a year ago. Probably stuff that has older versions (debian based?) would still have that though.
(Score: 0) by Anonymous Coward on Saturday June 30 2018, @09:11PM
I use an iPhone 4s running iOS 5. Everything works except for the spoilers and expand buttons.
(Score: 2) by RS3 on Sunday July 01 2018, @01:08AM (1 child)
Okay, I dunno what's going on but it's very fast now on Old Opera 11.01, and with javascript ON.
I know I had tried it very many times over the past year+. What I noticed was a big delay before received packets network activity- several seconds- maybe 10, then it would render quite well.
One of many nice things with Old Opera is I can accept the cert. Vivaldi now blocks me. I'm sure there's a workaround but who cares. Thank you for once again inspiring me, and for all you do.
(Score: 2) by The Mighty Buzzard on Sunday July 01 2018, @02:36AM
Well, back when we did the comment styles rework, we did a hell of a speed-up in comment rendering as well. That was why the comment code needed a rewrite to begin with.
My rights don't end where your fear begins.