The browser's change.org petition is in the top 8 for all Nintendo petitions on the site: https://www.change.org/decision-makers/nintendo-50
Also notably, some of these petitions have been resolved, eg. the Paper Mario one, without an official response occurring:
[image: 1770841039320-5c8ef7d3-064d-4adf-a57e-4b0ebd486432-image.png]
So although it's still rather unlikely for Nintendo to respond at this point, I'd still love to see a direct that announces a "normal" browser app. Because user demand could mean more sales and more money for them! And it could encourage a whole subset of "web apps" like in the Wii/DS days.
Also, instead of using alts to sign (Change.org removes these), the focus should be on spreading the petition, or a desire for a "real" browser, to other places. I would also say though, at this point, most people who want the browser have likely already signed. I like to focus on the reasons a browser is good, eg. in this blog post: https://vgmoose.dev/blog/debunking-criticisms-about-the-switch-browser-4535319561/
Regarding homebrew, I don't develop exploits! I don't have the skillset for it. My focus is on making user-facing apps, or websites like this one. An exploit is not a good fix to wanting a browser anyway though, because it would just be patched, and be a potential security concern on top of that.
I'm not bothered by these threads, and appreciate the enthusiasm, but it's also best to avoid creating repeat topics like this one. We can't do much about the Switch's limitations! There's a lot to be said about the Switch browser, workarounds, sites that work well, etc, however, if you have other discussion topics in mind (eg. an updated "How to" for using Google Drive on Switch 2).
Lastly, BrowseDNS is a generic service that supports other platforms, like Playstation, Apple devices, Android (including Peletons / fire TV / maybe some smart fridges), etc. Just pointing this out to underscore how the DNS itself is a networking configuration, and enabling the captive browser in this manner shouldn't be compared to something like a hacking exploit. I see these two use cases as distinct, with different sets of userbases.
1
