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
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
Ibetweenthat keepon 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
It's not like no one can comment on Hive anymore though when #HiveEngage is down (though we !HOPE that it remains accessible all the time). π€π§ββοΈπ€―
Your "quick typing fingers" might cause your hands to become "quick moving hands" !INDEED! ππ€―ππ
!WEIRD
!HUG
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
When the price of HIVE rises significantly again, it would take off a lot of dust-fluffing load from the #dustbunny bot !INDEED. π€π§ββοΈπ€π€
!WINEX
!HOPE
!WEIRD
The "other bot" to the "dust fluffing" #dustbunny bot is the "dust sweeping" #dustsweeper bot. ππ
It's !INDEED a source of HIVE (and sometimes HBD when out of HIVE) to delegate Hive Power to the #dustsweeper's Hive account, though the daily amount received by each delegator heavily depends on how many users of that service top up their dust-sweeping balance for the previous day. π€π§ββοΈπΈπ€―π€
!WEIRD
!HOPE
!WINEX