From Archiveteam
Jump to navigation Jump to search
Miiverse logo
URL http://miiverse.nintendo.net
Status Offline
Archiving status Saved!
Archiving type Unknown
Project source miiverse-grab
Project tracker miiverse
IRC channel #archiveteam-bs (on hackint)
(formerly #miiworse (on EFnet))
Data[how to use] archiveteam_miiverse

Miiverse was Nintendo's social network for the Wii U and 3DS. It had a website, as well as clients on Wii U and 3DS which were restricted web browsers.

The archived data has been compiled into a browsable website called Archiverse.

Vital Signs

Seems to be stable. Miiverse is not available on the Nintendo Switch.

A recent system update to the Wii U contained a message saying the service has ended[IAWcite.todayMemWeb]

Nintendo officially confirmed that the service would end on "Wednesday, 08/11/2017 at 06:00 GMT" in an article released on their UK site August 29th, 2017[IAWcite.todayMemWeb]. There will also be shutdown for the US[IAWcite.todayMemWeb] and Japan[IAWcite.todayMemWeb] at November 7th, 2017 at 10:00pm Pacific Time and November 8th, 2017 at 15:00 Japan time respectively. They provided an ability to request a download of your posts and albums, but it wouldn't include your comments or comments made on your posts. It was also apparently going to be delayed until after the shutdown, and "Some posts or screenshots may not be included in your downloadable post history due to their status at the time the service ends." The link was not accessible to users who haven't logged in with a Nintendo Network ID. A screenshot taken by Miiverse user Wertercatt/Archive Team user Powerkitten is available

After shutdown, Nintendo sent out emails to members that requested an archive. A sample of such emails can be found here: Miiverse/Post_History_Mail. The download links for the archives expired on December 31st, 2017.

Site structure

Example URLS

Useful URL strings

  • ?page_param={"per_page":"2000","order":"desc"} Control the number of posts returned. URLs unfortunately have limits to what you can return at once. See the example URLs here for the maximums. If you put in a per_page value over the maximum for a URL you won't be able to scroll farther to load another batch of posts, so putting the proper maximum in (instead of just a bunch of 9s) is a requirement to be effective.
  • ?page_param={"per_page":"2000","order":"asc"} Send to get the results in ascending order instead. Scrolling this is buggy, as any additional pages of results you load will be in descending order. We probably shouldn't use this.
  • ?offset=20Set an offset to keep going beyond the maximum post count. Seems to be limited to /empathies

Misc Oddities