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
And it's always fun to see the official names for things. Remember the STM release exploit? That bug is in the leaked code. The real code has the same structure as my decompiled version, and the bug is exactly what I thought (missing return statement), but the names differ.
And yes, the RSA sigcheck really was a strncmp call. But anyway, what is actually useful in a leak like this? Not much, really. Nevermind that you can't legally use any of it, it's not really adding much practical information.
The only thing that comes to mind is that having the PLL register documentation (which is always one of the most nigh impossible things to reverse engineer black box) might allow someone to try to overclock a Wii. Maybe. Not sure if it's possible.
Really, these leaks are mostly just fun because you get to *see* what they were thinking, and also things that got dropped. Did you know that the Wii was supposed to support using Wiimotes with GameCube software? There is supposedly a hardware SI emulator in the Hollywood.
Apparently BroadOn planned to do this... by sticking the entire USB and Bluetooth stacks in Starlet SRAM. Gee, I can't imagine how that didn't work out... Though if you tried hard enough and cut a lot of corners, *maybe* you could squeeze something in. Anyone want to try?
But Devolution already does this in a more flexible way anyway... So again, we're past that. So while I certainly find it *interesting* to read a full Hollywood ACR register documentation, it isn't going to lead to any breakthroughs.
Now if the leak *really* contained full Verilog for the GPU, for example, that could help resolve long tail emulation mysteries... But no sane emulator developer is going to want to taint their project like that. But it doesn't, so this is a moot point.
Must be nice to be able to see that stuff in the open though, right? Like getting the answers to a test to see you got almost everything right :)
They aren't. Signatures are only checked at install time, so channels don't actually need to be signed as long as you have some exploit path to get them installed.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
