Google Login Arrives on Denser
🚀 Google Login Arrives on Denser!
Dear Hive Community, 👋
Following our deep dive article into the architecture of Decentralized Google Login, we are excited to announce that it is now ready for you to use on our Denser blogging application (available here)! 🎉
Our goal was to bridge the gap between Web2 convenience and Web3 decentralization. 🌐 We wanted to give you a way to move seamlessly between devices - desktop, laptop, mobile 🖥️💻📱 - without the constant hassle of manually handling private keys, yet without compromising the core principle that you own your data. 🔑
For those who haven't read the mentioned article, a short note: Decentralized Google Login allows you to save your encrypted keys on the Google Drive associated with your account entirely on your browser side, without our knowledge of the connection between Google and Hive accounts. 🛡️
Here is how to get started and what you need to know about the workflow. 👇
1. Setup First: The Hive Bridge application 🌉
Before you log in to Denser, there is one essential step. ❗
To simplify things at Denser side, we decided to offer there only ability to login using Decentralized Google Login. Initial setup should be performed on: Hive Bridge application where you can configure your keys and protect them by only your known encryption password. Remember or save it - you will require this password on each new device, browser or webpage which integrates this kind of login. 🧠
The process is simple and only needs to be done once:
- Go to Hive Bridge. 🔗
- If you are already authorized there, e.g. by using Keychain, you should disconnect your hive account first. 🔌
Then you need to use Connect your wallet now button and select the Google Drive option from available wallet list. 📂 - Walk through Google Consent screen and allow access to requested properties and permissions. ✅
- Provide the information regarding your Hive account, private keys you want to import and set your encryption password to protect them. 🔐
This process creates a secure, encrypted file on your personal Google Drive. 🔒 For added security, this file is stored in a dedicated application folder ("hidden scope"), which means not even you can access it directly via the Drive interface - only the authorized app can read it. 🕵️♂️ Once this is done, your keys are portable and ready to be used by Denser (or any future app supporting this standard).
If you ever need to manage your stored keys (add/remove keys or destroy the wallet storage completely), you can do so inside the Hive Bridge application settings. ⚙️
2. Login: The Denser Experience 🚀
Once your Bridge setup is complete, simply head over to Denser.
- Click the Login button. 🖱️
- Select Other sign in options. 🔽
- Enter your Hive account name and click the Google account button. 📧
- Finally, enter the encryption password you set in Hive Bridge during configuration. 🔓
That's it! ✨ The application will connect to your Drive, decrypt your keys, and authorize your session.
The Role of Your Password 🧐
You might wonder: "If it's Google Login, why do I still have a password?"
Security is the answer. 🛡️ We store your keys on Google Drive so they follow your Google account across devices, but we never store them in plain text. Google hosts the file, but they cannot read it. 🚫
When do you need the password? 🕒
Only when you authorize a new device, browser or opening an application from different url. You will be asked to enter your encryption password once to decrypt the keys locally.What happens next? ⏩
Once decrypted, the session is stored securely in your browser. Future logins on that device are instantaneous - just one click on the Google button, and you are in. ⚡
Summary 📑
This update is about more than just a login button. It represents how we are building a safer, more modular ecosystem. 🏗️
While setting up the Google drive wallet requires a moment of your time today, it saves you from handling raw private keys on every new device in the future. ⏳ This is particularly effective on Android, where you are typically already logged into your Google account, making the Denser experience even simpler without the need to introduce private keys to yet another device. 🤖
Stay tuned, Hive and enjoy the seamless experience! 🐝👋
Congratulations @thebeedevs! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 60 posts.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Why I should ever share my Hive private key with Google???
Hello! Thank you for your comment!
All your keys are encrypted before sending / reading from Google and only you know the password 😀
You can always check application's source code which is open in opposite to some applications on Hive blockchain.
BTW which tool you used to sign your comment (Keychain / Peak Vault / hivesigner)?
OK, thanks.
I use keychain.
Cool! So it is a similar design, but in our case, you can switch between devices without installing 3rd party software 😀
Hi. If you have a time please read mentioned post: https://blog.dev.openhive.network/hive-139531/@thebeedevs/decentralized-google-login
It explains the big difference in usual soutions matching social and blockchain accounts where usually some server-side application knows the association. Here only you knows which Hive account and keys have been used to setup the wallet, which is stored at Google storage specific to your account. Data are encrypted at client side, using your password - no one can read it then.
Privacy and transparency is one of our goals and I hope this solution will also match your needs...
Is this offering something like Keychain? Obviously there is trust involved with any apps handling our keys and people will be cautious, but we need to avoid giving our keys to sites as much as possible. It sounds interesting anyway.
Hi. Yes we can say so because it (similary as Keychain) allows to store your private keys and then use them to sign Hive transactions.
The benefits and advantages over other wallets being browser extension based is, that our wallet uses cloud storage (associated to the space managed by you: part of your Google drive). So once you analyze this single opensourced and I hope quite well technically described solution, you can use at any app which supports it, any device, any browser. No more multiple copies etc.
Earlier mentioned article explains it in deeper details.