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. 👇
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:
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. ⚙️
Once your Bridge setup is complete, simply head over to Denser.
That's it! ✨ The application will connect to your Drive, decrypt your keys, and authorize your session.
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. ⚡
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! 🐝👋
