Has anyone else’s OP colour changed?

[BleachedJumper]

I can’t tell if I’m just going a bit mad, but it looks like a different shade of green and I feel all out of sorts!

Agree with not enforcing infinite scroll. I far prefer to load the thread and read it at my leisure. I'm on a fast connection and a thread of 1000 posts is just never going to cause a crash at my end.

@KatyMumsnet For users accessing threads through bookmarks, notifications, or any direct links to specific posts, you’ll see a ‘load older posts’ button. This prevents the thread from jumping around when you land on a specific point. However, if you’re visiting a thread for the first time using a general link, such as from the trending or active, all posts will still load as usual.

This isn't working properly. If I click on a thread in Threads I'm Watching, it now just takes me to the last post (no matter how many posts in the thread I had not read) whereas previously it took me to the last post I'd read which was obviously a lot more useful and presumably how it is intended to work.

My colours seem to be back to normal, though, so that's nice.

I'm not a fan as it makes it awkward and difficult to actually scroll down to the bottom of a thread using a mouse.

Also, when I click on the new "Load Newer Posts" button @KatyMumsnet , it's actually loading older posts. Is that because I have my threads Flipped?

Agree with not enforcing infinite scroll. I far prefer to load the thread and read it at my leisure. I'm on a fast connection and a thread of 1000 posts is just never going to cause a crash at my end.

Agreed. The change is making things far slower for me now. I read a thread, add a reply or put it on my watch list, go off and do something else, come back later to see if there are any updates, see from the list of Thread I'm On that there are at least two replies, click on that, all I see is the OP and the final post on the thread. So then I have to click on See earlier posts at least once, on a fast-moving thread probably twice, to see what's been posted since I was on the thread before. Offputting, and as others have said, not designed to get people to read the full thread before posting something that's already been said many, many times. This is not going to improve the standard of discussion.

This is not going to improve the standard of discussion.

So true! There are already tons of people who can't even be bothered to read the OP's posts before wading in with their response. This really won't help!

Honestly the infinite scroll makes navigating long threads really bloody awful on a PC using a mouse. And the loader says "Loading newer posts" when it's loading older posts for me because I have my threads flipped. And it has a weird greyed out table appearing behind it when the message appears before the posts load, it looks like it's broken until it actually loads the posts.

Is this why the display after posting a message has been screwed up?

Erm … All my attempts at posting are coming out as double posts …

Well, they were. This one didn’t.

The only app or website I consistently have trouble with is this one. Occasionally BBC News might go down, or Reddit. But this site is going wrong so much more.

Can you please ensure that you have more than one person on your IT team, and that they have more than one GCSE between them? Why do other sites consistently perform better than here? Are you not embarrassed by the constant stream of complaints, and the deluge of complaints on days like this one?

No other website seems to have the problems you do.

The thing is, we're not the people that MNHQ are trying to please, their revenue doesn't come from us. We are part of the offering, as it were, to advertisers that do pay them. It will only bother MNHQ if there is a significant and long-lasting drop in users interacting with the site, as that will reduce their advertising revenue.

This "dynamic scrolling" is shit. It makes "find on page" useless because the post(s) you are looking for might not have loaded.

we have tested this internally and with users before releasing as we do with all our releases

And it didn't throw up any of the many problems people are posting about...? Really?

I think that's rather harsh tbh.

Since January, we've had 3 total instances of downtime - 1 for 16 minutes, 1 for 15 minutes, and 1 for 30 minutes. Reddit had 51 minutes of downtime yesterday (https://www.reuters.com/technology/reddit-down-thousands-users-downdetector-shows-2024-11-21/). Our servers respond in less than 200ms to 99% of requests. There has been some slowness that's caused by 1k posts per page which is related to the volume of data when showing 1k posts - hence why we're building infinite scroll.

There have also been some freezing / crashing issues which we've narrowed that down to a bug in Safari that is experienced across the internet on sites with ads (https://discussions.apple.com/thread/254843801?sortBy=rank). It's a feature called "Privacy Preserving Ad Measurement" that needs to be toggled off in your Safari preferences. The label for that is really misleading - it's actually more private to have it turned off than on.

We A/B test pretty much every major feature release. The release of infinite scroll yesterday was itself was an A/B test.

All that said we are disappointed not to have caught these issues in our internal testing. Certainly won't deny that!