A strange thing just happened.
I had edited the prior post a few minutes before without a problem. Then I was going to make another edit but the Edit link no longer worked; it directed me to the main Dreamwidth page.
That page showed me as logged out. But my subscription filter links were still working, and one of them showed a post I think I hadn't seen before (so possibly not a browser caching issue though I'm not certain). Usually those links no longer work when I'm logged out. That filtered reading circle page still showed me as logged in.
In my other browser, I was still logged in, and there the Edit link worked ok.
I logged back in in the first browser, and things worked like normal again.
I had edited the prior post a few minutes before without a problem. Then I was going to make another edit but the Edit link no longer worked; it directed me to the main Dreamwidth page.
That page showed me as logged out. But my subscription filter links were still working, and one of them showed a post I think I hadn't seen before (so possibly not a browser caching issue though I'm not certain). Usually those links no longer work when I'm logged out. That filtered reading circle page still showed me as logged in.
In my other browser, I was still logged in, and there the Edit link worked ok.
I logged back in in the first browser, and things worked like normal again.
no subject
Date: 2020-10-27 08:00 pm (UTC)From:Hard-refreshed (Ctrl + R); still no comment. No indication it existed. Checked my DW Inbox: it showed the comment. Clicked the link to view it from there; still no comment. Unscreened it from the Inbox, then clicked through to it again. Finally it showed up.
This after editing a reply I made to you months ago on my journal in which the edited comment never showed up, either, though the Inbox indicated it existed and had indeed been edited. Like literally never showed up at all, to this day it's still missing.
Still not sure where to go with errors like this, though lacking any other info on what's causing them I'm leaning hard on it being CloudFlare having caching/refreshing issues.