Face it. For someone who is used to Web2 and a username and password that are both simple going to Hive where you have a username and FOUR private keys and FOUR public keys it can be more than just a little confusing. Then when you have to add a Hive Keychain to make it usable and there are multiple keychains out there that are each supported by different apps....
It is not an easy onboarding transition!
My alternative? Baby steps.
Let people post information on the blockchain through a surrogate account. In my case that is the 
First off a Supabase
For those of you who don't know Supabase is an online database. You can take information you get entered in online (or through an app) and send it off to be stored in SupaBase. It is quite a pain to setup but once you get the hang of it..well, it provides free storage for a database.
In my case it acts as a great place to throw data that people might have to get stored BEFORE going on the HIVE blockchain.
I'm using the SupaTest app to send data along to the database every 4 hours because (a) it gives me sample data to use and (b) if the database is inactive then it goes dormant. I'd rather the database stay active :)
Once the data is ON SupaBase its time to get it to Hive
But I don't want crap so...
This app grabs the data from SupaBase and then does a brief check to make sure the data is in the right format and nothing looks out of place. If it looks right then it goes on to HIVE as a small (8kb or less) JSON. In laymans terms it goes on the blockchain but it doesn't go anywhere that people will see it unless they really go searching.
In that way if someone posts something that shouldn't be there it isn't going to be visible to anyone right away. Later on I'll make code which goes in and checks the data and gives it to me in a more readable format for me to make a proper post on the Great Little Dragons page.
In that way people can start off with Web2 and still have a voice on HIVE...even if it is me writing down the words for them. The idea is that I can make apps which are HIVE adjacent and easy to start off with and then as people get used to using them and seeing their information being used in a positive way they can make the jump to their OWN Hive Username once they are invested rather than have the hurdle on their very first day on HIVE.
Personally I think it is a more user friendly way to introduce people to the Hive infrastructure. Especially if they get glitter tokens when they are on Web2 but they can only cash them in once they make the jump and do the learning curve to Web3.
But that's a sneaky little tidbit I'll introduce them after they have been active for a while.
The other benefit of this route is that people who start but vanish after a very short time.... well, their effort doesn't turn into wasted HP and a wasted account. If they start and vanish I'll take their HP :) Honestly though I hope people don't vanish and actually keep using the system once they learn how useful it really is.
So, that's today's work.
What's tomorrow's work? No idea but probably making my first dragon so I can start making the training pages and training apps, followed by a second dragon so they can battle and a system in which people in this group can cheer on their favorite dragon and win GLD tokens each week.
But....
.... This is all still a work in progress.
Stay tuned for more updates :)
