The Road from Login with Facebook to Login with Hive

In time, many Hivers remarked how platforms like Facebook and Twitter are benefiting from their "Login with..." options that can be included on any website, and immediately offer a login option linked to a huge user base.

Obviously, people are wondering and would like to see a "Login with Hive" out there, outside our ecosystem, especially knowing it would be a much better and forward-looking account system than the borrowed accounts on Twitter or Facebook, and we know that.

So, why they can do it and we haven't been able to do it yet?

Source

Well, unfortunately... size matters. That's why. When someone decides to add more login options on the website besides (or instead of) the email/password combination, they will be looking to cater to the largest audience possible. or to a smaller audience, but targeted to the website profile.

Only afterwards, maybe considerations of which is the better tech or the one that empowers users are reviewed. Actually, if the application is Web 2, they may still have the mentality of centralized control and taking advantage of users, instead of empowering them. We still see this kind of reminiscent mindset in what should be the eve of Web 3.

We can't compete with the traditional social media giants in size of user base, so there's no point in trying.

But maybe for targeted audiences that would use the "Login with Hive" option, we stand a chance.

So... what could be the targets? Let's see some potentials:

• free speech
• photography
• traveling
• cooking
• (alternative?) finance
• defi
• crypto
• blockchain
• blockchain games
• NFTs
• etc.

Let's see my reasoning... So, if on Hive we get lots of interesting travel journals, for example, and they get found organically, people creating such websites would become receptive to adding a "Login with Hive" option on their website that has nothing to do with Hive, otherwise (likely Web 2).

I believe a good step in the right direction is the decision to make Keychain multichain and fund it from the DHF. While I don't expect non-Hive users to ditch Metamask and flock onto Keychain, those who will come in contact with our ecosystem or who will use applications that are multichain (including on Hive), may very likely embrace Keychain. And as their proposal says, it will be redesigned to focus on the dApps on Hive.

Once crypto users become acquainted with our ecosystem and our dApps, they would understand the benefits of having a "Login with Hive" option more easily than someone who is not involved in crypto. The no fees argument on the base layer could be very powerful for some.

But how do you reach out to non-crypto people, other than by targeting various groups like photographers, travel journalers, etc.

Well, we haven't seen the effects of multichain Keychain yet. So let's see that first!

But I was thinking maybe adding a password management component to Keychain would help, if we find a way to get through to the users of this component that instead of having 100 passwords at 100 websites, they can have one set of private keys for all applications built on or connected to Hive. And that a "Login with Hive" option could be added it to their favorite non-Hive app for which they are now storing the password in the management tool. And that would eliminate the need of a separate password.

It's a lot of work though, to try to recuperate some Web 2 users onto Hive this way.

I'm sure more ideas, maybe better ones, can be found.

Posted Using LeoFinance Alpha