Actually, the fallout from the HardFork has settled, long ago. The problems we're seeing now are ongoing tweaks to Hivemind, which require no Hardfork. I do wish all of it would settle, though. 😕
Yeah. I get it, and I even sort of understand it. But there's the old duck thing.
Since the hard fork the speed of transactions has been going steadily down. We can have a new marketing slogan "As fast as ETH without the GAS fees!" How does that work for you?
I watched the wheel spin for 10 minutes on this post on LEO before I decided that I was either going to have to pay GAS or go to a different node/front end/something that is entirely my fault. I copied and pasted my ORIGINAL TEXT to Peak D, checked one more time to see the wheel spinning on LEO and hit publish. Since there is no Cancel button there I backspaced the area clean and exited the page.
Now I have a duplicate post. WTF?
So here's the deal with the duck. Performance across all front ends has been shit since the HF. Ergo it walks like a duck. Nodes and selections have been shit since the HF. It smells like a duck. Duplicate post after 10 minutes. That means I waited 10 minutes to see if the front end/node/anything but the HF might work this time.
Just let the record show that I had to switch front ends AGAIN to yet another FE to see if the comment I made actually showed up.
In other words, it took four frontends to complete all this. I'm sure glad the hard fork worked perfectly and all our consensus for life witnesses are right on top of this shit.
Let's onboard some people, what do you say? Long as we can hold total transactions down far enough we can do it. We can't handle 3500 users in a timely manner. How do you think it will look when we start adding zeros on the back?
Actually, the fallout from the HardFork has settled, long ago. The problems we're seeing now are ongoing tweaks to Hivemind, which require no Hardfork. I do wish all of it would settle, though. 😕
!ENGAGE 20
ENGAGEtokens.Hard-fork stuff still around to haunt us?!
!ENGAGE 20
ENGAGEtokens.Yeah. I get it, and I even sort of understand it. But there's the old duck thing.
Since the hard fork the speed of transactions has been going steadily down. We can have a new marketing slogan "As fast as ETH without the GAS fees!" How does that work for you?
I watched the wheel spin for 10 minutes on this post on LEO before I decided that I was either going to have to pay GAS or go to a different node/front end/something that is entirely my fault. I copied and pasted my ORIGINAL TEXT to Peak D, checked one more time to see the wheel spinning on LEO and hit publish. Since there is no Cancel button there I backspaced the area clean and exited the page.
Now I have a duplicate post. WTF?
So here's the deal with the duck. Performance across all front ends has been shit since the HF. Ergo it walks like a duck. Nodes and selections have been shit since the HF. It smells like a duck. Duplicate post after 10 minutes. That means I waited 10 minutes to see if the front end/node/anything but the HF might work this time.
QUACK! QUACK! QUACK!
Just let the record show that I had to switch front ends AGAIN to yet another FE to see if the comment I made actually showed up.
In other words, it took four frontends to complete all this. I'm sure glad the hard fork worked perfectly and all our consensus for life witnesses are right on top of this shit.
Let's onboard some people, what do you say? Long as we can hold total transactions down far enough we can do it. We can't handle 3500 users in a timely manner. How do you think it will look when we start adding zeros on the back?
And yet, I still want @bigtom13 to post. Engage you do, but, maybe a post? Xo
I hope you are well @bitom13 I dont' see a newer post then this to check in on, but hello trying to pop into Hive again in my busy days :)