You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
One of the reasons why we wrote our own flashing code for Wii bootloader flashing is because I took one look at Nintendo's (BroadOn's?) existing API for it, and determined it was completely unfit for purpose and dangerous.
It is now well documented that they later bricked a non-trivial fraction of Wiis worldwide, whether they had BootMii or not, when they pushed a dummy bootloader update whose only purpose was to overwrite our installed version (but which unconditionally applied to everyone).
My flasher not only had the two-copy safety that their design called for (but which their updater was not safely implementing), but also included a novel trick to provide *three-copy* atomic safety. Powering down at *any* time during BootMii installation is, in principle, safe.
That one near miss was a bug in this stuff in some corner case Wiis, which ended up corrupting one of the (eventual) main copies. However, my code checked and refused to run if *any* copy was not valid, so the affected user could do no further damage. Their Wii was fine.
All they saw was a first install attempt (I forget if it failed or reported success) that didn't work in practice, followed by all subsequent install attempts failing with a safety check error. After fixing the bug I added even more paranoia to make sure it didn't happen again.
"loading unauthorized software on your wii has a high risk of damaging your hardware"
Well, they technically aren't wrong. Statistically, most users were probably breaking into their Wii to pirate games, and *those* tools definitely weren't written by people following the guidelines I blogged about.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
