Last night there were some concerned Hive users, panicking out there for fear they had lost their accounts when they couldn't see their posts on their preferred front-end dApps.
This is a reasonable reaction! The reason is that we're all a bit tramatized by the predatory platforms of Web2, who without notice and most often without recourse, take down accounts. They conduct their business, and it is their business, like that every day. But that's not Hive. That is not who we are.
Part of my work on Hive is as an educator, not an expert, certainly not a dev, but an educator. This means I actively learn & teach, learn & teach, learn & teach. In fact, I just left the Web3 Con - Amsterdam to arrive in the smallest county in England where I start full-day classical chamber music rehearsals. Mind you, it only took me one flight, four trains, and a 40-minute Uber ride to reach my tiny hotel to get some rest near the rehearsal hall.🥱
At our Hive conference stand for Web3 Con - Amsterdam the day before my first rehearsal with British Clarinet Ensemble in Ashwell, England.
I hadn't put my bags down in my room before I saw in the CWH Discord server that one of our crew was in distress, thinking his posts were long gone from Hive. Thankfully, @gregscloud stepped in to offer a kind explanation that his work safe and sound in his account on the blockchain, so the crisis was averted.
But I'll be honest, I had a bit of the same concern myself when I was posting last night when I found my work was not publishing. I assumed it was an expired permission with my Hive key manager. No, that wasn't it. I tried different Hive dApps. Same result. Then I tried different devices. Bingo! I could see all was well.
So what had happened? The system worked! When I tried another device, I was looking at the same data, but through a different server or api node. You say, "So nothing was wrong?" That's right. It's just a node thing. Let me explain.
"So nothing was wrong?" "That's right. It's just a node thing!"
Each Hive node maintains a full copy of the blockchain, but some may have temporary issues. When we exercise the user feature to switch nodes, we're simply connecting to a different mirror, so to speak, of the same blockchain data.
Don't care why, but just a quick tire change ⚙️? I got you, boo! Here's a responsive mobile view on ecency to get you back on the transaction and posting road in a flash.
So, as you see, the drop down menu above gives you an easy access list of commonly used Hive RPC nodes you can switch to, including api.hive.blog, which is a default for many front-ends. In this example, I chose hive-api.arcange.eu
I have one more thing to share, but first let's credit the CWH Crew for their work today.
@andysporring
@bobbyb58
@drmelanie
@gregscloud
@hillarycad.witch
@shadowspub
@wailing.fong
It's good to see ya'll here.
Much love!😘
Alessandra