Sort: Β 

I'm on a seafood diet.
When I see food I eat it.

Credit: happyme
@savvyplayer, I sent you an $LOLZ on behalf of svanbo

(4/10)
NEW: Join LOLZ's Daily Earn and Burn Contest and win $LOLZ


Congratulations, @svanbo You Successfully Shared 0.200 WINEX With @savvyplayer.
You Earned 0.200 WINEX As Curation Reward.
You Utilized 2/3 Successful Calls.
wine_logo



Contact Us : WINEX Token Discord Channel
WINEX Current Market Price : 0.033



Swap Your Hive <=> Swap.Hive With Industry Lowest Fee or Highest Reward : Click This Link
Read Latest Updates Or Contact Us

Your comment there is a duplicate of one of your comments under the "grandparent" comment. 🀯 That shows how "excited" life is for you! πŸ€£πŸ˜‚ !WEIRD !INDEED !HOPE !PIZZA

Yes, there was some kind of !WEIRD glitch. I don't really understand what has happened...
!HUG !PIZZA

Perhaps you just accidentally replied to the wrong comment (and tried to delete it but weren't able to do so successfully) !INDEED. πŸ€―πŸ˜… !WEIRD !ALIVE !PIZZA

No I didn't. I replied to the right comment, but probably was already in the next one before it really went through and the glitch was that it posted at the next one I was going to answer !WEIRD !INDEED !wine

If I recall correctly, there was a glitch on the #HiveEngage frontend where a comment gets published on the next comment on the user's Hive Engage feed !INDEED. 🀯 Perhaps @tydynrain can also share his experience here! 😎 !WEIRD !HOPE !PIZZA

That seems plausible, since I've seen very similar behavior with token actions on BeeSwap. If I go too quickly when adding assets to pools, the visual message will be for the token pair that I just selected, and not the previous pair which was the actual transaction. It's really weird, and it's easy to replicate. I can see that happening with comments too via Engage. 😁 πŸ™ πŸ’š ✨ πŸ€™

!HOPE
!INDEED

I think that as long as the transaction that you actually wanted to publish is the one that gets through, then we can simply ignore the incorrect messages that get displayed, especially if we try to perform transactions too often (more than once every 3 seconds which is the block time on the Hive blockchain as a good estimate). πŸ§˜β€β™‚οΈπŸ€“

!WEIRD !HOPE !ALIVE !HUG

oh really? That means it wasn't only with me that this has been happening? !wine !HUG !BBH

Yes, and with the many Hive projects Arcange has been managing, it is unlikely that such intermittent problem will get fixed soon. πŸ€―πŸ€“ !WEIRD !INDEED !HOPE !PIZZA