@BrowseGPT was also intended to be able to generate images for users in that channel, although we never finished the integration.

I appreciate the feedback here from users, but we can't vote to make site decisions on the fly. The chat system will be revamped though to fix leaving rooms not removing them from the sidebar.

Categories is another separate topic, Personally, I'd rather not introduce an AI specific category unless a lot of AI flooding the site became a problem. To me, that seems better suited for chat (like BrowseGPT works via DMs)

The intent is that leaving any channel should remove it from the sidebar, so I'll need to see about fixing that. I can also see an argument to remove it from the default channels, given how it's not used much anyway.

But we can't just unilaterally remove it only because it'd be popular to do so. Some users for instance might not have any other way to access AI than via the DNS, and it shouldn't be our role to restrict that.

I said this in the other thread, but the point of that chat is to have a place for AI generated images to go. Removing the channel would likely mean people just put them in other channels instead.

But there's also the separate problem of neither of these chat rooms are really used. And users are able to leave any room to free up sidebar space / stop receiving messages. Site slowness is unlikely to be affected either way.

It is possible in theory to have AI models that are trained only on licensed / open source images. In that regard, there would be no "stealing" concern.

Of course, the theory is different than the practice however, and in practice big tech companies are just training on whatever image data they can get their hands on.

"Art" is such an abstract term that I think it's very easy to see how automated or computer-generated "art" is still a form of art. It's not too different than other forms of algorithmically generated art in the last 2 decades. Eg. https://en.wikipedia.org/wiki/Algorithmic_art

That being said, if you're talking about the "AI Art" chat channel on this site, I can also understand the argument to rename it. The entire point of that channel being separate is to make sure that AI generated images don't clutter the main "Artist" channel, after all.

Broccolini (not Broccoli! :P) is a homebrew project, and if it becomes "good enough" it's possible it could be submitted and accepted on the eShop / PSN / similar places.

As far as security, this would likely be less of a concern due to how the renderer works compared to a "real" web browser. This is because Broccolini doesn't use executable memory, and behaves just like "another" game or app. It's possible that an app like this could be included even on the eShop, given there are other similar apps (such as FUZE4)

It's a separate topic, but security is also likely only one aspect of why the Switch doesn't have a "real" browser. Probably other factors including the licensing terms with the third-party company that makes the browser (NetFront NX), and a desire to have users use the eShop instead of web apps.

But like I mentioned last time, the built-in browser is going to be the best thing the Switch 2 for quite some time. Broccolini is a Switch 1 app after all, and the resources that a system-level internal browser has access to will always be more powerful than an external app.

If you do try changing the time, I also suggest trying to change the timezone, as the Switch always keeps track of "true network time".

I'm still recommending this!

Reminder that this exists and still works well! Everytime I use this feature it surprises me. You can basically use it like a touchscreen laptop with the kickstand and a usb keyboard.

Switch 2 takes it even further, as you can use the joycon as a mouse too.

As far as I know, this is some kind of recent (new-ish as of the Switch 2) check that blocks out the browser. I have had it appear before, but not often.

If you could start keeping a log of when it happens, that might be helpful to figuring out how it works. The DNS service was ran for a few years before even realizing the browser timeout was exactly 20 minutes, just due to a lack of research.

In theory, the "Feature is not available" notice is similar to what the console says when the browser is outdated, or hasn't been online regularly (as in, connects to Nintendo's servers) in a while. That's why I typically recommend trying to connect normally, using Google DNS, or updating.

If it's always happening around the same time, that might even point to a "quiet hours" kind of functionality, but I think that would be unlikely. The intended purpose of the Switch browser is to allow the user to connect to the Internet after all. If you have access to a PC, it'd be interesting to see if CaptiveDNS works during the timeout: https://github.com/browseDNS/CaptiveDNS

Also I have no problem with these kinds of questions! Talking about web access on the Switch 2 and similar devices is definitely one of the goals of this forum, and why I started working on Broccolini in the first place.

Broccolini (my work-in-progress browser app) still doesn't really work that well, besides for using Wikipedia or other simple sites.

It does support Wii U and Switch via homebrew, and it's possible it could come to the eShop one day, but it needs to support more sites/features first!

If you want to get the web browser unlocked/improved on Switch 2, the best avenue is to try asking Nintendo, or by signing the petition.

I don't think there's anything wrong with hoping Nintendo/Google add YT to Switch. Access to YT (and other Internet sites) is definitely a "first world problem", but lack of that access can also be extremely limiting, especially if devices in the home are limited. Yeah, there's larger problems in society, but we can always hope to see those resolved as well.

If I had to guess, Google and Nintendo are trying to work out some kind of fair licensing deal to decide who gets what percent of the money involved in the S2 YouTube app. And the same might be able to be said about ACCESS Co (the makers of the Switch browser) and Nintendo. What feels like a limiting social issue to users is actually tech executives trying to ensure they're well-paid.

But customer's complaining is an important part of that equation. If every Switch 2 user complained about this at once, they definitely would be financially incentivized to try and address it faster. Keeping the customers happy is part of making money for them, after all.

I suggest contacting Nintendo customer support and letting them know that you are interested in a fully-fledged browser, or at least the YouTube app. Google said the YouTube app is coming still, but that was many months ago.

To my knowledge, it's not yet known why this screen sometimes appears. I think rebooting / updating is a good fix for it. It seems to have started around the Switch 2's release.

The browser does have checks to sometimes ensure it's on the latest Switch version, but the "This feature is unavailable" screen seems like it's a new/different (or even enhanced) mechanism from that.

I'd also recommend trying to connect normally without the DNS, eg. on Automatic or Google DNS (8.8.8.8) once, to allow the console to "phone home" and verify that for itself that it's up to date.

When you get these kinds of issues, try tapping on the captcha / clicking on it a lot until it pops up with a "Got an issue?" link, and then report through that that the captcha isn't working, and the page isn't loading.

If enough people do this from their Switch browsers when there's an issue, Cloudflare might be able to fix the issue. It sends info to them about what methods the browser supports, which they can use to update the captcha check.

I just made some changes that might help with the issues, let me know if they seem to be happening less frequently. Ultimately, we're going to have to announce some downtime to migrate the forum in the near future to truly address the slowness/503's.

To be clear, this "This feature is not available" notice is separate from the 503 errors on this website (which we're looking into). The issue mentioned in this thread appears to be new behavior in the new Switch update, which is not yet fully understood.

I recommend re-configuring the Wifi access point, rebooting, updating the Switch, connecting and using the Internet without the DNS configured, etc, to try and troubleshoot this "Not supported" DNS pop up problem.

Sorry, it sounds like a new kind of error. Let me know if anything seems to help resolve it.

If you (or anyone else) has a PC on the same network, it might be interesting to try CaptiveDNS, and see if the same issue occurs: https://browsedns.net/topic/2072/release-captivedns-access-the-browser-on-the-switch-locally-self-host-instructions

Can you try connecting to the Internet without the DNS, and doing a system update? (whether or not an update is available doesn't matter). A reboot might also help. Is this on Switch 1 or 2?