Changes

The Nintendo 3DS utilizes a similar title-based organization as seen in the Wii and DSi platforms. The same [http://nus.cdn.c.shop.nintendowifi.net/ccs/download/ update server] is being used as was with the DSi, however a new common key has been introduced. The update/shop servers must be accessed via SSLv3.(For curl, the --sslv3 option must be used otherwise connecting will fail)

The Nintendo 3DS utilizes a similar title-based organization as seen in the Wii and DSi platforms. The same [http://nus.cdn.c.shop.nintendowifi.net/ccs/download/ update server] is being used as was with the DSi, however a new common key has been introduced. The update/shop servers must be accessed via SSLv3.(For curl, the --sslv3 option must be used otherwise connecting will fail)

The organization of Title IDs has not been documented fully yet. It's unknown how regions are determined in titleids if at all though there does appear to be evidence that the regions are sequential, similar to how Wii System Menu Updates are ordered: JPN USA EUR KOR and CHN (introduced with the DSi). 3DS has two additional regions: TWN and AUS.

The organization of Title IDs has not been documented fully yet. It's unknown how regions are determined in titleids if at all though there does appear to be evidence that the regions are sequential, similar to how Wii System Menu Updates are ordered: JPN USA EUR KOR and CHN (introduced with the DSi). 3DS has two additional regions: TWN and AUS.(AUS was added with DSi)

System tickets are retrieved via a SOAP request to NUS, instead of directly downloading the cetk with HTTPS.

System tickets are retrieved via a SOAP request to NUS, instead of directly downloading the cetk with HTTPS.