Different issues during registration on Hive

Back then, I used to experience a lot of issues when trying to onboard people on Hive, but the introduction of different unique methods eventually put a stop to that.

---

---

Before I continue in case someone sees this post as excessively pointing out issues and names, I have on-boarded nothing less than 20 members, so everything here is based on experience

---

---

When I joined the Hive platform, I was faced with the issue of registration refusal via the Ecency weblink. I was told that my IP address had already been used, and I was surprised because it was my first time registering on the platform. I had to opt in to the Hive Onboard link, which is no longer available to everyone but only to a select few.

Back then, I didn't even know there was anything called registration tickets, which are made available by accumulating a certain amount of HP. I got to know this during one of the many troubling days I was onboarding someone. I tried every possible means I could, but nothing worked. I was prompted to go to one of the community Discord channels, and a Pakistani member helped out and explained to me how tickets work in onboarding people.

The Ecency IP address issue still exists but fluctuates. There have been people I onboarded, and the registration went through with ease, while for some, it refused to register on their phones, saying the IP address had already been used. You may not notice this issue if you're not familiar with the Ecency frontend. I really wish they could permanently fix this issue because, even if it's about securing the system and ensuring no multiple or spam accounts are registered, there are still genuine people who get stuck and find it frustrating to register.

When Ecency became a big issue, I heard about the introduction of onboarding through Inleo. I was happy, but hey, the initial process was tough and troublesome.

First of all, the site was mainly designed for high-performance phones, so any phone with 2GB RAM or below would have to fight a world war to scale through the registration process. This may sound like an exaggeration, but I'm speaking from the troubles I passed through while onboarding people. The site was prone to displaying the “Error, we are fixing it already” message, and it was so frustrating because one had to start the entire process all over again. I remember I owned a 2GB RAM phone at that time, and I experienced a lot of these issues — and most of the people I onboarded back then had 2GB RAM phones as well.

After a successful registration, the next stage was to claim the keys, which was a bit complicated, especially when introducing someone who wasn't familiar with the internet. I wish it had been as simple as it is now.

Now, I love the introduction of the Keystore method. The idea is so good — one doesn't need to go through the stress of dealing with so many obstacles just to complete a registration. I recently found out that the Keystore password has the same strength and capacity as the master password we used to know.

Well, the only people who need to up their game are Ecency — they should fix the IP address issue once and for all — and Hive Onboard, which is associated with PeakD. They should return the onboarding process to the normal open method and not keep it restricted to only the people they assigned it to.

Also, individuals who have registration tickets should, from time to time, generously announce their willingness to onboard anyone through the Hive Onboard site.

Thanks for reading!

This is my entry to Digi-prompts of the week

Photos used are screenshots (mine)