Sort: Β 

Oftentimes, I think that after I reply to the most recent comment notifications on #Ecency and I see #HiveEngage being down, then that should mean I should end that particular commenting session early (and then just try to catch up using #HiveEngage on my next commenting session if possible). πŸ˜…

!ALIVE
!LOLZ

Sounds like a good plan I'd say. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!ALIVE
!LOLZ

I wonder if that's your plan too, or you simply try harder to sort through #Ecency comment and mention notifications to see if any of the notifications there hasn't gotten a response from you yet. πŸ€―πŸ€“

!PIZZA
!HOPE
!ALIVE

I will usually see what I can find using Ecency's notifications, if that doesn't work, then I sometimes try other frontends. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!ALIVE
!HOPE
!PIZZA

There's something weird happening on the #Ecency frontend, where I see my reply on a parent comment getting successfully published, but then noticed the same parent comment on #HiveEngage still showing up as having no replies from me yet. 🀯🀯

!ALIVE
!STRIDE

It takes Engage a little time, several minutes at least, to catch up with the status of comments and replies. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!ALIVE
!STRIDE

I was referring to the fact that #Ecency shows that my comment was already published, but when I saw the same parent comment on #HiveEngage and open the comment again on Ecency, my comment didn't exist. 🀯🀯

!PIZZA
!ALIVE