This is a limitation of how the browser displays. More info here: https://browsedns.net/topic/359/browser-applets-and-why-videos-don-t-work

You click here: https://wikipedia.org

This channel (ClayKramer) has a bunch of KK Slider covers of popular songs, which I keep listening to lately:

The original and lite Nintendo DS had an Internet Browser on a cartridge in 2007. It came with an extra game pak that gave it additional memory to load web pages, that went into the GBA slot of the DS.

The game case:

Picture of the cartridges:

2007 was before smart phones were popular, and as a kid there weren't many options for going on the Internet, outside of stuff like a family computer or school. So in a lot of ways this browser was the only connection to the outside world. There was also stuff like: seeing friends online in Animal Crossing / other Wifi games, or basic SMS texting, but nothing like portable "real" Internet.

The browser itself had two modes, it could either work as displaying the full website on the bottom screen, with a zoom window that you could move around to read text on the top screen:

Or a more mobile-friendly mode (kind of like Reader view) where the page spanned both screens. This was better for reading text, but did break a lot of web pages.

The browser itself was a version of Opera, which at the time was pretty good at handling most web pages. This is similar to the Wii's browser, except it did not support Flash player (whereas the Wii did!). So stuff like videos and sound didn't work.

In particular one site that worked very well on it was the Smash Bros Dojo, where updates about Brawl were posted by Sakurai every week day.

It is kind of disappointing that the limitations of this 14 year old browser are not too dissimilar from the limitations of the Switch browser. But I've already talked about that a lot in the change.org petition, and how it compares to the 3DS/Wii U browsers.

Anyone else use this browser? Heard of this? There was a newer revision built into the DSi as well, but by the time the 3DS rolled around the browser switched over to WebKit (which is still used in the Switch).

Can you try it? I think it works but would just suck if the timeout happens and kicks you out.

This category is going to be a list of different sub-categories for different game series's. I grew up in the Gamecube era though, so I might be out of touch with what's popular these days.

Some sub-categories I was picturing:
Minecraft
Fortnite
Animal Crossing
Pokémon
Indie Games

But it really depends on if they make sense. Anything else you'd like to see?

this is not good

the bbc news is kind of a downer @pwsincd

@iggy1337 I posted a new topic here about video playback: https://browsedns.net/topic/359/browser-applets-and-why-videos-don-t-work

Webm likely falls under the same boat, although I haven't tested it explicitly. There might be something clever that's doable with GIFs or HTML canvases, but there would still be no way to produce sound.

When using BrowseDNS or Switchbru DNS to access the browser, video playback is unavailable with the following message: "Support Code: 2809-1212 This feature is not available".

However, videos do work elsewhere on the system (eg. the eShop, News app, or even YouTube app). The Switch has several different browser web applets on it, each with different permissions. Here's a table from the Switchbrew Wiki:

Custom DNS settings can allow the last one, WifiWebAuthApplet, to allow the user to browse the Internet. This applet has no whitelist, and allows any URL to be visited. However, it does not allow video playback. This is done intentionally by Nintendo to limit the usefulness of playing videos when using a custom DNS. (For more on how BrowseDNS works, see this this post, or this one for self hosting).

Unfortunately, that means video playback only works if you can serve it from an Applet that only allows a short list of whitelisted domains. As all of these domains are https, there is no chance to bypass this using a custom DNS server.

As of v13.2.0, the whitelisted domains include: nintendo.com, twitter.com, facebook.com and google.com. You would have to have control over a domain or subdomain from one of these to allow video content to play. Previously, sites.google.com could be used (aka SwitchTube), however this is now explicitly blacklisted as well.

The only real hope to get this functionality working is to publicly let Nintendo know that there is user demand for a standalone web browser (like on Wii, Wii U, DS, and 3DS) that supports these features.

If you have a homebrewed Switch, the app BrowseNX also allows browser video playback, but that is becoming increasingly rarer and unfortunately does not match the ease of use of an officially available browser.

I need to make my site more mobile friendly, it's got a very "2015" design.

Wow! That was fast, I need to re-read myself... How did it hold up for 2022 standards?

There's two more sequels but I haven't checked out the most recent one.

For now the closest you can do is make a group and then manually create a group chat with members in that group, or announce something on a thread in the RP section and add the people that show interest to a chat.

But it's a double edged sword: making a public thread to start something will show people how it's done and hook more potential interest beyond just doing everything privately in a chat.

Previously, all new topics in all categories were watched by default for all users. This is now changed so that you will only see "Unread" new topics if you watch category manually. Any posts you make will automatically be watched for new replies. This is more how a normal forum behaves, but it does mean that you should go more "out of your way" to find new topics.

You can manually watch a category for new topics by using the button above. Also, the Recents page will still show everything (unless you also change those settings).

From Wikipedia:

Project Gutenberg (PG) is a volunteer effort to digitize and archive cultural works, as well as to "encourage the creation and distribution of eBooks." It was founded in 1971 by American writer Michael S. Hart and is the oldest digital library. Most of the items in its collection are the full texts of books or individual stories in the public domain. All files can be accessed for free under an open format layout, available on almost any computer. As of 3 October 2015, Project Gutenberg had reached 50,000 items in its collection of free eBooks.

The HTML library can be browsed here: https://gutenberg.net.au/

@proxzi said in books:

If you're looking for a book that's more historically based and quite interesting to read I'd recommend Great Gatsby.

Great Gatsby is also freely available (copyright expired) to read here: https://gutenberg.net.au/ebooks02/0200041h.html

In case it's not immediately obvious, you can also access these forums on any PC, phone, or other device directly at: browsedns.net !

This is one of the primary goals of this site– to try to bridge the Switch and other devices with the greater Internet.

I also tested sleep (not in those logs), the network requests just stop and resume after waking the device. (Which is why counting them to know how "soon" until the timeout seems doable.)

I can confirm exactly 20 min on v14.0.0 as well (waking the Switch from idle each time).

I also monitored the network requests my Switch made, and here are the log files. I have the receipts!

http log: http_timeout_log.txt
dns requests: dns_timeout_log.txt

Here you can see the full 20 minute "session". Every ~1 minute a GET request is made with the user agent "NX NIFM/00".

In between those, every ~3 seconds (!!) a HEAD request is made using the full "Mozilla/5.0 (Nintendo Switch; WifiWebAuthApplet) ..." user agent (that we also see when browing web pages).

These requests are used to determine if the captive portal has been authenticated yet. In a normal flow, as soon as you agree to the terms or log into the hotel wifi, these requests would reply with a special header (X-Organization: Nintendo) which informs the Switch that it's connected to the Internet.

After exactly 20 of the GET requests, and 401 of the HEAD requests, the browser shuts, which is expected just looking at how frequently they occur (401 = (60/3)*20+1). Although it would be interesting if instead of it being a "timeout" if it were more like "try 400 times to connect every 3 seconds, then give up".

Based on this, by counting the number of requests made, it should be possible on our end to tell when the pop up is about to appear. But there still doesn't seem like there's anything that can be done on the networking side of things to interrupt it.

Also interesting is that in the DNS log, a domain name request is only made around every minute. This means in the normal workflow, depending on how the hotspot's captive portal works, it may take up to a minute to be authenticated.