Has any one reported on this?
May 6, 2018 4:15am CST
I was expecting this would be reported as it happens every single day when I try to open a page here the first time. One huge para explaining that there is an error. The second attempt is successful. It can be handled but if this glitch can be taken care of it would make life here a bit more easy.
9 people like this
• Cambridge, England
I get it constantly when using Firefox since their recent update. I never get it when I open a discussion in Chrome. I must conclude, therefore, that it is due to the speed with which a certain browser/connection combination 'talks to' the myLot server. There is certainly nothing wrong with the speed of my connection (rated at 50Mbps but usually more like 30Mbps), so I suspect that the latest Firefox update is at fault. It's almost certainly nothing that @mylotbugs can fix!
3 people like this
• United States
I always run Chrome, but I did see for an hour or so yesterday where some pages took quite a bit to load, and I got the error one time. I've always thought this site has a fairly big signal/bandwidth/whatever, because many people have problems only with this site giving them fits and starts. I doubt Bugsy could do anything either, unless he wanted to stop paying us for a year or so and spend a few kajillion bucks buying a private server farm and completely taking the coding apart piece-by-piece and rebuilding it...which ain't gonna happen. Oh well, I'll live.
• Cambridge, England
@allknowing You very likely won't see it on any other site because myLot works differently to most other sites - it was built with its own custom code. It's not unique in that the pages are generated dynamically 'on demand' for each browser but the way it does it may be different from that of other sites. Anyway, there is quite a bit of 'chat' and handshaking behind the scenes between the browser and the server. If your browser or connection is slower or more 'jittery' than expected (which can be either a browser problem or an Internet connection problem), the server returns an error saying (effectively) that it timed out waiting for a response. Strictly speaking, you shouldn't be seeing an error page like that - most websites trap that sort of error and deal with it in various ways (nearly always not visible to the user). Bugsy did once say that he was going to deal with it but he clearly hasn't got around to it or it was too complex for him to fix easily. Some people have found that clearing their cache helps while for others it doesn't.