SoylentNews is people
SoylentNews
We are having some difficulties with the site at the moment. We are aware that there is an error being presented about our certificate being expired. We are working on it and appreciate your patience while we iron this out.
Interim measure #1: try to use the non-secure link to the site http://soylentnews.org
Interim measure #2: Accept the expired cert, but be sure to uncheck the 'Permanently store this exception' checkbox (this may not be available to you on very recent versions of Firefox).
If you have other suggestions on workarounds, please submit as a comment. Be certain we are doing all we can to get the site back up and running!
[Update] NCommander reports that: "New SSL certificate has been installed and the site no longer generates certificate errors. I'm continuing to do work to get performance for Firefox to be decent."
[Update 2]: A revised frontend proxy is nearly operational and ready to go into service which will resolve performance issues for firefox
(Score: 2, Interesting) by KGIII on Monday June 08 2015, @12:04AM
I'm continuing to do work to get performance for Firefox to be decent.
A revised frontend proxy is nearly operational and ready to go into service which will resolve performance issues for firefox
Didn't we have enough coding for a specific browser back in the IE6 days? Why do you have to optimize for Firefox, specifically? Of all the browsers that are standard consistent (and FF may not be - I do not generally use it so I do not know) it would seem likely, to me, that Firefox would be that one.
"So long and thanks for all the fish."