You are viewing a single comment's thread from:

RE: 5K Powered by Coffee β˜•πŸ‘Ÿ

in Actifit β€’ 22 days ago

We also !HOPE for a #HiveEngage fork, especially as arcange's Hive Engine app has been having problems since the start of this day (UTC). πŸ€”πŸ€― I and @savvyplayer are currently not able to view most recent comments that neither of us have replied to yet. πŸ€―πŸ˜…

!WEIRD
!INDEED
!PIZZA

Sort: Β 

That had nothing to do with Engage. Hive nodes are now being targeted for the same kind of coordinated attacks that the Hive-Engine nodes have been suffering. Yesterday no posts at all would load on the Ecency website for the same reason. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!PIZZA
!WEIRD

There currently is a technical issue with the #HiveEngage app again, so in the meantime, I and @savvyplayer won't be able to easily find your (as well as other Hive authors') old comments that neither one of us has been able to reply to yet. πŸ€”πŸ€―πŸ˜…

!WEIRD !INDEED !HOPE !HUG

Β 15 days agoΒ (edited)Β 

It's so interesting that I keep missing the times when Engage is having issues. 😁 πŸ™ πŸ’š ✨ πŸ€™

!HOPE
!HUG
!INDEED
!WEIRD

The #HiveEngage app is now working (properly) again! πŸ€”πŸ˜Ž

Your "autocorrect" made you miss adding an I between that keep on your comment. πŸ˜†πŸ˜…

!INDEED !HOPE !WEIRD !PIZZA

Good to hear, and for me too.

No autocorrect was involved in the omission of the 'I'. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!PIZZA
!WEIRD

I almost typed "not" !INSTEAD of "now" on my previous comment! πŸ€”πŸ€―πŸ˜†

It was your "quick typing fingers" then (like what @savvyplayer started telling you more than a month ago) that caused your comment to miss an I !INDEED. πŸ€”πŸ€―πŸ˜…

!WEIRD
!HOPE

Yikes, that could have been catastrophic!

Indeedy, that's how it happened. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!WEIRD

Those attacks on the Hive Witness nodes (not just #HiveEngine Witness nodes) themselves are probably the reason why @savvyplayer experiences problems publishing any comment or voting using the #Ecency mobile website (whether main or alpha) !INDEED. πŸ€”πŸ§˜β€β™‚οΈπŸ€―

!WEIRD
!HOPE
!HUG

Yep, exactly, so now we have some notable issues in both layer 1 and layer 2. I'm really hoping that they can be mitigated. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!HUG
!INDEED
!WEIRD

Those issues also seem to affect the #dustsweeper bot whose Hive account I send recurring HIVE transfers to (as balance top-ups), such that the bot is supposed to inform the sender very soon after the transfer about how much balance they have. πŸ€”πŸ€“ My third (recurring) transfer was already about 3 hours ago (so the first two transfers were two days and one day ago, respectively) but the bot still hasn't told me my balance. πŸ€―πŸ€―πŸ˜…

!WEIRD !INDEED !HOPE !WINEX

Yes, I used to do that with that dust-fluffer bot, and I probably should again at some point. Interesting, and yes, it is almost certainly because of the Hive-node issues. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!WINE
!WEIRD

The #dustbunny bot's Hive account is heavily struggling with fluffing all those dust votes, as seen with its Voting Power having been less than 80% since more or less a year ago. πŸ€”πŸ€― That's as opposed to #dustsweeper whose VP is just sitting at 100% (for which I want to suggest to give away some as "bonus" votes for its users). πŸ’ΈπŸ€―πŸ€“

!INDEED !WEIRD !HOPE !WINEX

The poor bugger. I should delegate more, though I'm more than a little overextended at the moment. I delegate to the other fluffer bot too, and it sends me some HIVE, and sometimes HBD, regularly. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!ALIVE
!BBH
!HOPE
!INDEED
!WEIRD