Howdy "Me too Kurt" and Kurt too 🙂
My experiences are firmly pointing at a 'moment' of critical 'failure to communicate' with the server
- JavaScripts running locally on one's device - known as Client-Side Commputing - are how JiveWare operates everywhere it is installed
Most modern websites employ this strategy due to the speeds of modern processors and browser capabilities
- When the JavaScripts ask for a connection to GET something or to SEND something, and cannot make the handshake, they have an IF - THEN routine that returns an error to the script = the script then is written so that it must DISPLAY an error to us, rather than just try again in a second or so.
this is not good programming. It would be very easy to make it try some number of times to conclude that there is some severe connection error - THEN throw up the error message (about 10 lines of script by my estimation)
- the proof of this can plainly be demonstrated when one is composing a reply - and the auto-save feature kicks in at 1 minute intervals
- the auto-save fails to connect > Big Red Error box at bottom of screen for 5 seconds > one continues until done composing and [Reply] is successful
- THUS - momentary server connection failure!!
I can't theorize on why some folks are mistaken for asfahan - that must have no correlation other than both cases cause a Big Red Box Error.
{ there, I said it out loud, so to speak }
Have a good night , boys
ÇÇÇ