---
category: technology
layout: post
title: Nintendo and the Homebrew Arms Race
date: '2008-11-19T11:51:00.000-05:00'
author: Anna Wiggins
tags:
- freedom
- video games
- Gaming
- Technology
modified_time: '2013-10-22T11:19:50.562-04:00'
blogger_id: tag:blogger.com,1999:blog-4209116010564764361.post-7895229798301291259
blogger_orig_url: http://www.stringofbits.net/2008/11/nintendo-and-homebrew-arms-race.html
---
When I purchase a piece of hardware, it is mine to do with as I wish. This is a long-held understanding. If I buy a piece of clothing, I can have it altered. If I buy a car, I can change the tires. If I buy a television, I can kill myself trying to screw with its insides.
It might void the warranty, it might put my life at risk or potentially damage the thing I've purchased, but it is my right as a consumer.
Nintendo takes a different view on the issue. Owners of the Wii have long been able to employ a simple buffer overflow exploit in Twilight Princess to run custom code. This exploit, called the Twilight Hack, allows a user to install, among other things, an application called the Homebrew Channel, which looks like any other Wii channel and lets you run other custom code without using the Twilight Hack again. It's the gaming console equivalent of installing a new stereo in your car.
Since the hack was made public, Nintendo has been trying to thwart it. They have, to date, released three firmware updates that included code targeted to stop the Twilight Hack. The most recent update succeeded at stopping it completely - it appears to detect the hacked save files and delete them, both on boot and whenever you insert an SD card.
So, all of this is standard fare. Whenever a console launches, homebrewers will make it run custom code. The console manufacturer will release an update to prevent this. The homebrewers will work around it. This process will continue in an escalating cycle.
However, Nintendo has delivered a low blow here. Along with the System Menu 3.4 update, they changed their terms of service.