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. π π π β¨ π€
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). π§ββοΈπ€
Yes, of course. It's obvious that the displayed message is incorrect, because the previously-selected pair is the one that gets added. When I'm going quickly, I definitely do more than one every three seconds. πππβ¨π€
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
In maintaining apps, intermittent technical problems are usually significantly harder to catch because they are hard to detect and reproduce, so they often rank low on the priority list unless they cause serious damage such as data loss. π€―π€ !INDEED !LOLZ
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
Yes, of course. It's obvious that the displayed message is incorrect, because the previously-selected pair is the one that gets added. When I'm going quickly, I definitely do more than one every three seconds. πππβ¨π€
!ALIVE
!HOPE
!HUG
!WEIRD
Perhaps those incorrect messages are a subtle sign that you should interact with Hive apps (a bit) more slowly. π§ββοΈπ€―π
!BEER
View or trade
BEER
.Hey @tydynrain, here is a little bit of
BEER
from @savvyplayer for you. Enjoy it!Do you want to win SOME BEER together with your friends and draw the
BEERKING
.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
It isn't happening often and it doesn't really harm, right? !HOPE
So it doens't really matter !wine !HUG
In maintaining apps, intermittent technical problems are usually significantly harder to catch because they are hard to detect and reproduce, so they often rank low on the priority list unless they cause serious damage such as data loss. π€―π€ !INDEED !LOLZ