The connection to the server was reset while the page was loading.
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.
Well that sucks
It doesn’t load a full page. Probably have to do that trick with changing it to 20 posts and threads or something. Guess I’ll just check back tomorrow rather than fight it tonight.
No problems here...Mac Pro/Safari.
John/Jim only really need HTTPS on the donation page, login page and sign-up page, etc....encrypting my mundane posts seems like overkill!! ;-)
It is working on HTTP.
But its functionality on HTTP is quite limited at the moment. The stuttering page problem is worse than usual. At a time of day when the server load must be very low (unless hordes of English-speaking Chinese have suddenly become interested in the notion of a Free Republic). Which leads me to suspect a software problem, not a hardware problem.
Are you logged in?
Just kidding.
I just wish I understood what all you guys are talking about!!
This kind of explains what can happen.
What We Know About Friday’s Massive East Coast Internet Outage
https://www.wired.com/2016/10/internet-outage-ddos-dns-dyn/
But I’m good though today.
I always make sure that I don’t have a computer around or an internet connection so that I never have to deal with that.
Threads only partly loading, again. Reduced to 20 displays last time, kept it there. Only the first ten display, can’t scroll further down.
Hope it’s working better for you now now. I talked to John and he said he’d look into it. I see he got some of it fixed already. Thanks.
and fixing problems.
o “Isolate & Replace” is better than “Try this Try that”
Intentional Isolating a recurring software problem is the preferred method of troubleshooting. Therefore we will discuss software Profiling.
o Profiling
Software Profiling means printing out to memory, but usually to a hard drive file, the relevant functions, with specific relevant data, referenced by objects and modules. For example, the debug profiling file may read:
obj DoSomething func DoingIt dataNumber 327 dataName Bob
obj More func DoMore dataMore 489blahblah
. . .
Profiling is real time. Can be turned on/off real time by a simple setting property/variable. Reading such a file is the easiest, and probably the only way to understand quickly how a complex software operates. No more guessing.
o Debug Object
Yes a troubleshooting object is global everywhere. But it is the only global object. It can be local, with more difficulty.
Fortunately when the failure is isolated, solved, and fixed, the Debug Object is removed.
Example is simply: oDebug.printf( blah blah )
o Logging
Faulty problems can be Internal or External, Client or Server or else. Locate all relevant log files, but if possible, a Debug Log file, also called Profiling, should eliminate guessing.
It is amazing how programmers can take years or never, to slowly understand how a specific software operates. By Profiling, in only days not years, can complex software be made easy to understand, then isolate and fix.
o Interrmittency vs Hard Fail
Intermittent problems are far more difficult to solve unless Profiled with Debug files.
o Concurrency
Search & identify all concurrency such as threads, semaphores and such, in the language used.
—
Must be some important news about to break.