@help My last few posts aren't appearing in my timeline...thoughts?
I also had Firefox warn me about visiting my own page due to an expired certificate. That one's more of an FYI than a question.
@help My last few posts aren't appearing in my timeline...thoughts?
I also had Firefox warn me about visiting my own page due to an expired certificate. That one's more of an FYI than a question.
@jessekelber @help Two of mine from 0553 and 0604 (NZ time) also refuse to appear, even after repeated minor edits.
@jessekelber @help I can guess that one of my two may have tripped some kind of ‘not on the timeline’ filter because of its subject matter. The other was pointing out an unexpected MB behaviour to @help . I've since changed the time on both and they still aren't on the timeline. Both are on my blog as expected.
@help So it looks like my responses or any post that starts with an @ mention is showing up fine, but my regular posts are…just not there.
@jessekelber @help Oh, yes, actually I posted a photo of cows (from my iPhone) that also hasn’t appeared on the timeline.
@jessekelber @Miraz I’ve noticed this too. Do you two see my non-reply posts? I did three about the photo challenge earlier. /@help
@macgenie Nope I don't see any posts from you Jean. And I see my non-reply posts arrive on the timeline after a huge delay, about 4 hours or so. Same for posts frlm @Miraz, none other than replies. //@jessekelber
@macgenie I don’t see any of your posts about the photo challenge, only replies to other people. / @Miraz @jessekelber
@macgenie @help When I click on your name on the timeline in the Mac app the latest non-reply post I see is from 06/07 October starting “I am not much good at charts”. When I visit your site I see 3 later posts.
@jessekelber @help I've just had a warning from Chrome saying the certificate for my (recently resurrected) page expiring yesterday.
@crossingthethreshold More attention for my posts! But the timeline is much more quiet without all those posts. I hope @manton can figure it out quickly.
@AlanGMarz @dejus @Miraz @jessekelber @amit @crossingthethreshold @frogplate This is resolved now. The issue was our shared certificate, so didn’t affect publishing to custom domain names, but did affect the timeline.