… when there is more than 30 unread or new messages. Opening a topic is quick, but when going back to “unread” (or “new”) it takes a long time for discourse to refresh. When messages are less than 30 everything is as smooth as usual. It’s been like this for a couple of weeks already.
hi @Philip it most likely has to do with your history being cluttered up. safari has become a peace of garbage in the last decade. if you clean up your history it might respond far better again.
Or take @nathanletwory lead and try Firefox. I’ve got FF synced across multiple desktop and mobile devices/OSes too. Nice feature. A FF test might be worth the effort as process of elimination.
I would rather not install new software that I don’t “need.” I try to keep my machines as ‘clean’ as possible - and I don’t have any Windows or Android hardware (I used Windows for over 25 years and, to be honest, I’m totally fed up with MS, but that’s of course another story ).
I have this same problem on two different (quite new) Mac’s - I can’t believe that nobody else is using Safari / seeing the problem.
If I would try FF and everything would work - what would that mean / proof? That Safari isn’t “allowed” on discourse…? @sam
I only use safari but I’ve never had that issue, though I’ve been running os Sierra until yesterday. I’ll let you know if I encounter any issues on Mojave
No problems on 10.13.6 with safari 12.0.2
I have 96 new. I’ve tried going back to new by clicking ‘back’ and via the keyboard shortcuts - seems quick enough
Me as well, though I do find it useful to keep 3 browsers (Firefox, Chrome, Safari) on my Macs, but to each is own.
The purpose of the second browser, in your case, is to try and confirm that there is a Safari issue, especially considering that you have two boxes doing the same thing.
Yes, I guess my first explanation wasn’t precise enough… going back to ‘unread’ or ‘new’ is quick and smooth - but when clicking on a new post in the lists I get a delay of about 8…10 seconds before the new post opens.
I think it probably is a problem with Safari (and my Mac’s) as nobody else is having the same symptoms. So instead of installing FF I guess I’ll first try the link you posted. I’m a bit reluctant to do that, though… It would mean a bit of work (passwords, configuration, etc).
Anyway… Thanks for the advice and the link!