Indeed, and this wasn't the first time. It's happened probably about 5 times that I can remember. I'm really curious how and why Engage does that. πππβ¨π€
!ALIVE
!HUG
!PIZZA
!STRIDE
!WEIRD
Indeed, and this wasn't the first time. It's happened probably about 5 times that I can remember. I'm really curious how and why Engage does that. πππβ¨π€
!ALIVE
!HUG
!PIZZA
!STRIDE
!WEIRD
If #HiveEngage becomes FOSS, then people who self-host (and fork) it will eventually be able to pinpoint the problem (and solving the problem would be essentially free of charge with the instance operators' and code contributors' help). π
!HOPE !INDEED !WEIRD !ALIVE !WINEX
I'd love to see it, and on both counts. πππβ¨π€
!ALIVE
!HOPE
!INDEED
!WINE
!WEIRD
Whenever #HiveEngage is down (like right now), it's like "being in the dark and seeing only those comments in the front" (seeing only recent comments without replies, and not those beyond). π€―π
!WEIRD !INDEED !PIZZA !HOPE !UNICOIN !ALIVE
I imagine so, and it's something that I thankfully keep missing, as it's working fine tonight. πππβ¨π€
!HOPE
!INDEED
!MMB
!STRIDE
!WEIRD
!ZOMBIE
When I was about to close the web browser yesterday however after replying to as many comments as I can on Hive (with the limited time that I allocated for such commenting session), #HiveEngage suddenly went working again. π€―π
!PIZZA !HOPE !ALIVE !WINEX
Talk about the irony of inverse timing...lol! πππβ¨π€
!ALIVE
!BBH
!HOPE
!PIZZA
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