Is TidBITS broken, or is it me?

Looking at the latest issue page in Safari, all of the articles are missing. I tried clearing the cache, disabling extensions, and toggling the “show full articles” link - nothing works. But TidBITS does look perfectly fine in Firefox, and an old tab that has been open since February does display the articles.

Is this something on my end, or is everyone seeing the same thing?

1 Like

Some other things I just noticed -

  • one of my extensions (not sure which, either Ghostery or StopTheMadness Pro) was blocking the “accept cookie” prompt. But getting past that made no difference, the articles still didn’t show.
  • Logging out of the TidBITS site fixed it - the articles show as expected.
  • Logging back in breaks it again :frowning: - in firefox too.

Interesting issue, looking forward to learning the solution.

Meanwhile, I put the link in Orion and Firefox (not using Safari at the moment) and they worked fine.

I’m a tad confused by these bullet points… Logging in/out of what? Apple Account? Mac account? Tidbits account? there are so many things to log in and out of these days…

Clarified that bullet point - thanks - it’s logging out of the TidBITS site. (maybe related - I was spontaneously and simultaneously logged out of TidBITS in both Safari and Firefox shortly after posting my previous message - I did nothing, I was just suddenly no longer logged in)

Odd indeed. I’m not an under-the-website-hood kind, but until those who are can respond, all I can think of would be along the lines of:

  • upon trying to log in did you get that ‘checking if you are human’ checkbox? (maybe related)
  • if you are using LittleSnitch or some other technology to selectively block connections that would be something to investigate
  • maybe something in Safari Settings is interfering
  • you already tried turnning the extensions off, and updating them?
  • what happens if you view the TB site as an app

Well, whatever the reason, it cleared itself up. Everything is fully back to normal.

2 Likes

This happened to issues #1793 through #1797 for logged-in users for a few hours on Tuesday morning. The fix turned out to be to just open the issue for editing in WordPress; it wasn’t even necessary to save a change.

My developer has no idea what might have caused it, but we’re keeping an eye on things.