It's basically the Hive Power and the HBD that you claim (from any Hive blogging app such as #Ecency itself, #PeakD, or automation Hive apps such as #HiveKeychain and #HiveVote) from pending rewards on your Hive account. 🤓
!WEIRD !INDEED !HOPE !PIZZA !WINEX !ALIVE
Yes, that's what I figured, but I'm just curious why they started appearing all of the sudden. Another update I guess. 😁🙏💚✨🤙
!ALIVE
!HOPE
!INDEED
!PIZZA
!WINE
!WEIRD
I don't think that there is another way for those notifications to pop up on the #Ecency frontend except with a frontend update !INDEED. 🤯🤯😅
!WEIRD !HOPE !PIZZA !WINEX !ALIVE
Usually yes, though it could have been dormant/unused code that became 'activated' with particular conditions. 😁🙏💚✨🤙
!ALIVE
!BBH
!HOPE
!INDEED
!PIZZA
!WEIRD
That's unusual but possible, and is a !WEIRD way to think as the cause of those new notifications exclusive to the #Ecency frontend !INDEED. 🤯🤓
!HBIT
savvyplayer, you mined 0.9 🟧 HBIT and the user you replied to (tydynrain) received 0.1 HBIT on your behalf as a tip. You can receive 100% of the HBIT by replying to one of your own posts or comments. When you mine HBIT, you're also playing the Wusang: Isle of Blaq game. 🏴☠️ | tools | wallet | discord | community | daily <><
What's more, you found 1.0 ⚪ BLAQ pearl as a bonus treasure token!
Your random number was 0.0757420212209654, also viewable in the Discord server, #hbit-wusang-log channel. Check for bonus treasure tokens by entering your username at block explorer A, explorer B, or take a look at your wallet.
There is a treasure chest of bitcoin sats hidden in Wusang: Isle of Blaq. Happy treasure hunting! 😃 Read about Hivebits (HBIT) or read the story of Wusang: Isle of Blaq.
I don't consider it weird at all, as all sorts of crazy stuff happens with code. Some bugs appear very rarely because their trigger conditions occur very infrequently. Depending on the application, there are often notable sections of dormant or unused code, especially for old projects. 😁🙏💚✨🤙
!INDEED
!WEIRD
!ZOMBIE
Those "dormant or unused" code or "old" code likely cause intermittent problems which are usually hard to catch and fix, where rebasing code often helps fix them (even if doing so takes a lot of time) !INDEED. 🧘♂️🤓
!WEIRD !HOPE !PIZZA !WINEX !ALIVE
Exactly, completely rewriting or rebasing older code is usually a very good idea. 😁🙏💚✨🤙
!ALIVE
!BBH
!HOPE
!INDEED
!PIZZA
!WEIRD
I think that most dev teams just have the right number of team members to finish whatever is on the project plan, so when an unexpected problem pops up during development, delays occur !INDEED. 🧘♂️🤯🤓
!WEIRD !HOPE !PIZZA !WINEX !ALIVE