Rush Browser

🧵Most people assume: “If a Handshake name works in https://, that means it’s legit.” But this is a misunderstanding of how the web works. HTTPS was built inside the ICANN DNS world not for decentralized roots like Handshake. Let’s break it down. 👇

@anewformofmusic 😍

Interesting development . I had picked Commando to be a key part of the Bitcoin2 wallet . I would like to make ' Rugged ' a key word of the Bitcoin2 Wallet - once @RushBrowser is open sourced and BTC2 can connect to Handshake & Bitcoin2 names there . Seems Commando2 is in works !

Handshake Australia would like to acknowledge the builders/creators/founders of this protocol in help by celebrating 6 years of the Handshake protocol running… Also a massive thanks for the backers/supporters/namers in believing in its future! From me and the team at hnsAU.. Happy 6th birthday 🎊 #hns #handshake $hns #web3 #digitalidentity #ownthedot

@HNS_token @rahulsutariya Yes it will be there.

@rahulsutariya @RushBrowser Is there a detailed operation tutorial?

RUSH + IPFS = Hassle-free Web Builder for $HNS TLD Owners Build and go live in 1-2-3. No need for NB or SS. No nameserver changes. A TXT record on-chain → your website is live. Decentralized. Simple. Ownership-first. Built for the $HNS - powered by @RushBrowser

@Mayaank_Roy 😔

😂🤣😂🤣😂🤣😂🤣 I just can’t laugh anymore 😂😂😂🤣🤣🤣😂

Upcoming Release 2.3 – @RushBrowser We may integrate the BOB wallet extension directly into Rush, since Chrome no longer supports it - bringing a full HNS wallet natively into the browser. 2.3 is currently in testing, and if all goes well, we may launch it asap.

If the Handshake wants long-term independence, collision-freedom, and native identity, then giving it its own protocol is the natural direction. 🤝

hns:// gives Handshake what HTTPS never can: Native verification DANE trust without CAs Zero name collision risk Direct resolution without DNS hijacking A protocol identity of its own This is how Handshake becomes Handshake, not “alternative DNS inside ICANN’s rules.”

🧵Most people assume: “If a Handshake name works in https://, that means it’s legit.” But this is a misunderstanding of how the web works. HTTPS was built inside the ICANN DNS world not for decentralized roots like Handshake. Let’s break it down. 👇

Donors, drop your Web3 domains below - whether they have an active redirect or are fully live sites. We’ll be adding them all to the app! 🤝

@bankrolls_eth @namehunter_eth It’s meaningful because open-sourcing builds trust in Web3 and invites more devs to contribute, improve features, and add ENS/HNS integrations. $2k is just a community signal. Plus, we promote all donors in-app and honor them on our official donors page.🤝

@RushBrowser @namehunter_eth This is interesting. I have had a look and you have a target of only $2,000, if you do not mind me asking how can this be meaningful? Thanks!

Thank you @namehunter_eth for the $100 donation toward our open-source goal and for supporting the ongoing development. 🤝

Rush 2.2 has a Home button (keeps reloading) bug and a Bookmarks (clear all) bug, and these issues affect overall smooth performance. A fixed stable build drops in 1 hour - avoid downloading until then.

🙏 Support the project: rushbrowser.com/donate.html Just $1,420 left until we can open-source Rush Browser. And remember - at $200 donation, We’ll build your own custom 2.2 browser, white-labeled with your brand. 🤝

⚡ Performance Boost Rush 2.2 is faster - improved DNS handling, better DANE caching, quicker tab switching, and optimized internal pages. 🐞 Stability Fixes Everywhere A large set of bug fixes and behavior improvements make this the most stable Rush version yet!

Rush Browser v2.2 is now live! Please consider donating to support development → rushbrowser.com/donate.html Only $1,420 left before we can open-source Rush! 💡 Donate $200+ and get your own custom browser based on v2.2 - your name, your logo, no Rush branding. Fully yours!