With the never ending issues with HiveEngine, the problems seems to be fixed on TribalDex by switching nodes.
One of the issues is that HiveStats seems to have issues because we cant change nodes? Is that a potential fix for us? #feedback
With the never ending issues with HiveEngine, the problems seems to be fixed on TribalDex by switching nodes.
One of the issues is that HiveStats seems to have issues because we cant change nodes? Is that a potential fix for us? #feedback
Listened to your last pod today and heard you say that the 'engine.beeswap.tools' node is the one you never have any problems with.
Is this the one we should be using?
(I prob understand less about the role of Hive-Engine nodes than you).
yeah it's right here. of course, i take the screen shot and tribal dex goes down lol
Yeah I was going to say you can trade the orderbook using beeswap as well now.
But of course it doesn't work when I go to try and screenshot.
Sigh.
it seems to work well
What I use now
I understand your frustrations on Hive Engine in general. But I would like to again highlight that the problem we are currently having is not related to Hive Engine (blockchain) itself but related to some nodes that are commonly used and not having a facility on hive-engine.com to switch nodes. Of course I'm not defending #hiveengine completely because I know there are a few problems with scalability and centralization. But my point is that the current problem is not related to that.
In the blockchain world this problem is very common to see nodes going down or overloaded or being attacked. That's when we switch to another node. That doesn't mean that the entire blockchain is affected. Tomorrow if api.hive.blog is having issues continuously for a few days, it doesn't mean that Hive itself is down and Hive itself has never ending issues.
I don't think a lot of people on chain that are on the dev side of things understand what this sounds like:
"It's not a problem, change the node."
We are never going to keep people here on chain if this is the answer we give them because quite simply, 99.9% of the population has no idea what 'changing a node' means.
It's not up to the world to conform to us, we need to make it stupid simple for the world. If we want actual adoption.
I definitely agree with you. It has to be stupid simple. We cannot expect everything to be very simple in the blockchain world and that's also one of the biggest problems in crypto adoption. Below is a very common phrase in the crypto world. Not with just Hive Engine. As I said earlier, it can also happen to Hive when api.hive.blog goes down because it is one of the most used nodes.
"It's not a problem, change the node."
Nodes are a very common thing in the blockchain world and that's one of the things that differentiate web2 and web3. This facility is both a boon as well as bane. It is more like if we don't like a node switch to another. hive-engine.com is just one interface that was having problems, people should know to switch to tribaldex or other wallet interfaces that work.
There should be other volunteers willing to create alternative user interfaces that can help during node issues. Nobody is ready to do it because there is no proper incentive for that.
the issue is, hive is very unique in the blockchain space because of the social elements to it. so a large audience of who we attract is not always blockchain savvy.
they just want things to work.
it's imperative that we get these apps to switch nodes automatically, so that the user experience is flawless for the people we are trying to attract.
we only have one time to make a first impression, and i can almost guarantee the majority of those that have join the chain these past few weeks, have more than likely already given up and moved on.
Definitely agree with you on that. I understand the fact that the experience should be seamless. But some of the apps that had issues are mostly centralized with limited facility. But blaming the entire blockchain and calling it down or having issues is what concerns because as I said, if Peakd is down we don't blame Hive for not having a seamless experience. We move on to Ecency or hive.blog. I heard people using tribaldex with the right nodes did not have any issues.
I completely agree with you on the User experience part but that a different topic and the current issue is not related to user experience directly. Even if the node issues are resolved, there will still be some elements of these user experience issues which definitely needs to be addressed.
It just seems like....
Everything is having issues. lol
Yeah the last two weeks have been a royal pain
Lol funny. It works for me.
Yeah I was having problems with that too and they told me it was an issue on my end, lol. I was like nope, try again.
Thank you for troubleshooting this.