What happened earlier.....?

[#1]

@Anonymous 

I actually mentioned this exact same issue on 09/0/19 on post 33 of this very thread!!

(at the time I did check and yes my settings were the same as you).

I wasn't signed in either.

I think it's normal for us to see ourselves when we're logged in and check users online....?

[#2]

@DS I get the opposite sometimes - I am permanently signed in, not hidden, and I sometimes don't appear in the list.

[#3]

Tis a bit daft!!

Bit like JonoH, he's here when at home, but not here when he's at work!

[#4]

I have just tried to "Mark all post as read" using the Options drop down, but it is no longer working as explained earlier here but it was earlier this morning!

[#5]

That's odd, the options are now available again.

[#6]

Lithium are finding nothing wrong, Instead of creating this ever-expanding thread with loads of issues that are potentially unrelated and impossible to track, could we please create a new thread for each individual issue you come across and tag me in, I'll then raise a ticket for each problem. 

[#7]

Lithium are finding nothing wrong

Erm, Khoros;)

So, the destination IP has no bearing on this. That rare day, noted further back on this thread, where I had quick loading pages, not waiting for other users signatures (TLS handshakes to their sites), no issues spotted, it all worked very well, but others (namely those involved on this thread) were seeing issues. But Khoros found nothing...?

Instead of creating this ever-expanding thread with loads of issues that are potentially unrelated and impossible to track,

I can the logic in this, but it's all contained in 'here'

could we please create a new thread for each individual issue you come across and tag me in, I'll then raise a ticket for each problem.

But this could cause several users, seeing issues at the same time, all starting separate issues on the same subject. Thus multiple reports could create more work for the mods to merge... this may be an unfortunate outcome.

Anyway, happy to partake in starting several topics if this will help restore my viewing/posting pleasure:)

[#8]

The problem is @DS when I tell Khoros the symptoms... they might not all be linked to the same issue, then they can't replicate it and then I can't get it fixed. 

If your post identifies an issue someone else is having they can just say me too, and that's fine, but this thread has become an exhaustive thread of everything that's wrong with Khoros, and is not about a specific thing. and so the support agent doesn't know what parts of it to read.

[#9]

Yes @JonoH but they only need to look back, say at the IP that worked for me (back then) and the IP's where I had issues. Surely this is a starting point? Look at why those IP's cause, or appear to cause the oddities mentioned herein? I was bouncing around a few back then.

Let's say they 'shut' what can a good one, then see if others (yourself included) start to see weird unexplainable oddities too?

If it was something at my end, then surely it would be g-l-i-t-c-h-y all the time? But that day, back then, I was actually having a great experience, although short lived.

As I said, happy for others or indeed myself to start several topics on the various issues as seen by us (at this end). But if they don't get picked up quickly, or indeed Khoros don't rewind the clock to see why it happened, are we wasting our time when it could be utilised elsewhere? One could say spreading the various issues across multiple threads could be seen as a way to hide the common issues.

Take the first post.

So I was mid-reply earlier, finished the reply and hit post..... was greeted to this

This should not have happened. I was logged in (so back then 'they' knew I was in here), I took great care to create a post and upon hitting post I was greeted to the above. Nobody warned me the forums were going off for maintenance.

But when I sat and waited, to see if I'd wasted my time, they came back, with the remainder missing from my post, but luckily I could post up to where it auto saved. The remainder remained missing, gone, a waste of my time.

Then the oddities started (look as the user id's on post 1)

Please read the first page, it was others too. They fixed something (what by the way?) and broke other parts of it. Surely I should be able to post without 'fear' that my post won't go in to the public domain

The maintenance looks like it created the first reports, thus are they not in the right place? (others were reporting other issues, which one could put 1+2=3 and thus there was one cause, with several different outcomes.

The other users posting elsewhere could well have been having issues too, so posted, but the cause could have been the maintenance, thus should they be merges under that one cause, or dotted around?

Page 2 could be seen as a consequence of what happened during the downtime.

Some of page 3 seemed to be related too.

I probably messed up and should have started another topic for post 34. Happy for a mod to go back and split it from there if this would help? But I wasn't sure if more maintenance had taken place.

Post 35 could have been related to post 1, I don't know, but the oddities continued.

You acknowledged issues on post 38, so I thought this would be a good place to continue to post the continuation of the oddities. Again, maybe another topic should have been started, but would the mods have merged it back? IDK

You even wrote:

It's working perfectly for me, Lithium have stated that they can't replicate the issue and require further information. @HarryB seems to still be affected, 

So, you were fine, like you seem to be, but another employee witnessed this. Was his device checked? What was the results of the analysis? What fixed it for Harry?

You replied on post 50 too, so one could assume you were happy to continue reading reports on this thread.

Users then bounced issues and possible solutions on page 5, all appear to be related to the issues first reported in the first 4 pages.

On post 74, after you made me aware the Lithium rebranded, to which I wrote:

Then a few days later I actually started this very thread......

So, I thought I'd finally solved why the forums went down and the consequence of the (unknown) changes.

But, I thought it was all related and I got that wrong. I'm not trying to create hassle, just trying to solve it.

(by all means pick a post that you think answers my first post and ask a mod to tick it and lock this down:))

[#10]

@DS 

To a large extent you are talking about operational niceties.  Having run massive IT services I would not see this as a business critical service, which needed exceedingly graceful system shutdown procedures for maintenance slots.  I agree it would be nice if there were warning messages advising when maintenance is due, but that is a different matter.

Also with web applications there is rarely the sense of a persistent state which could be used to determine that a user is still connected.  Walk away from your PC, leave it doing nothing and it is likely to look no different from you sat there actively bashing your keyboard.  It is not as though every key stroke is being sent back to the server as you type.

I understand your sentiments, but I do not think that they fit this technology stack.

As for works better some of the time and not all of the time, well a lot of detailed evidence has been reported here but I discern no analysis of the evidence, just periodic kicking of the tyres seeing nothing with the telescope held to the patched eye.  It working better after a service restart does not really inform what was wrong before the service restart. Pingdom.com traces report marked wait delays, redirects and long receive durations.  I have not seen any comment on those points from Lithium or whatever they want to call themselves today.

I very much suspect that some of the issues are environment and browser related, which is why I asked for a clear list of required information to be provided.

[#11]

Thanks @Townman

What I'm trying to say, it would be nice to post on here without the issues that others and I face. I don't understand how some on the same browser on a Plusnet connection don't also see the same. When it's bad, it's really bad. It isn't practical for me to use ethernet, but resort to this more and more, but the issues can and do crop up. If it works okay one minute, but then it goes wobbly, what can it be?

I get it isn't a major issue, I don't need to post, but when I choose to post, it would be nice to have an uninterrupted experience. I've not frequented the BT forums for many years now, but do remember them alerting us in advance to forum maintenance. Forewarning would mean they don't need to check our online status, plus many on here post and don't sign out, thus leaving their ID in a dormant state. I've seen some run into 0000's of minutes. I clear all of my browsing too, to rule out any stray cookies clinging to the forums, but the posting/reading/loading issues can continue. The post that created this thread was possibly with me (and LithiumSR) being the only ones actually on here, so doubt it was many users giving the odd forum status (as per page1, lower image).

It is not as though every key stroke is being sent back to the server as you type.

I do wait now, though I shouldn't need to, until the auto save catches up, hoping that once I hit post it actually posts. Then if it doesn't I hope the auto save can be reloaded. It have to wait 5 mins for the next auto save to 'kick in'. This adds more time to my reply, rather than typing and posting. So I can wait an additional 5 mins before moving on.

I understand your sentiments, but I do not think that they fit this technology stack.

If 'it' worked fine every time, then I'd be happy. I wouldn't need to report these issues. I'm grateful others witness the same.

As for works better some of the time and not all of the time, well a lot of detailed evidence has been reported here but I discern no analysis of the evidence

And I often think am I wasting my time. Are there more out there, knowing nothing will come of it, thus don't report their issues? Do they think this is normal and thus don't know any better?

I have not seen any comment on those points from Lithium or whatever they want to call themselves today.

Hence why I thought, one location, one place for them to 'dig in to', rather than me here, you there, etc.

I very much suspect that some of the issues are environment and browser related, which is why I asked for a clear list of required information to be provided

I've openly posted, more than once, the browser in use, the add-ons in use, ethernet or wifi, but others similar to me do not see this, whereas I can. If it transpires my connection (via PN) to the www is still at fault, then I can no more, or do I clock out for the last time with PN. My laptop is fully up to date, I check this more and more to rule out my end being the cause.

I'm this >< close to quitting here, the next big 'hiccup' might well push me.

(and PN too, but that's not for this topic).

[#12]

If you have intermittent issue posting, I would tend to look for a wifi issue.  I get them from time to time in very precise parts of the home and I have 3 APs.

[#13]

Yes I should have worded that better @Townman. But can't go back to edit it now

Most of my issues on here are over a wired connection. I've moved my setup around and thus use a shortest ethernet cable as possible (2 metres). It's easier for me to be 'free from wires', and doing other things elsewhere appear to be fine. It's mainly on here when I 'clunk click' to browse/read/post, rules out any wifi issues.

I will say this though, whilst posting. If 'they' go back, 'they' will see I have dropped to my mobile data (tethered to this laptop) and do not see the same issues as I do when going via the PN network.

But Khoros and/or Jono don't see this. HarryB did once, so is this actually my fault?

[#14]

Just some observations since yesterday evening, here's the IP's I've been bouncing around to get to these forums

143.204.181.103
99.84.8.51
143.204.192.45
143.204.192.111
143.204.192.25
99.84.8.85
13.33.232.121
143.204.192.45
143.204.192.111

With varying results. However, I have done one thing which has improved my viewing pleasure and that's to swap back to my BTSH6

(could the PNH1 really have been, in part, a reason for the oddities contained in this thread - too early to tell, but it is certainly better)

[#15]

The forums have not been bad since my reply above and I thought I'd cracked it by using the BTH6, but as of roughly 45mins a go the waiting for the various URLs (lower left hand corner, as posted previously) has returned.

Not point popping tracerts up, but did notice slight delays (not massive) during the journey on these IP's:

195.166.143.141
195.166.143.140
194.72.16.70
109.159.253.161

The destination IP's vary more than I recall

(the add-on Flagfox doesn't tally with the trace route results)