|Downloadable via the Homebrew Browser|
WiiTweet is a Twitter client for the Nintendo Wii that allows you to interact with your friends from your Wii.
It follows Twitter's security guidelines by implementing PIN-based authorization and using HTTPS in every request. Read Authorization Flow below to get a more detailed explanation of how and why WiiTweet gets authorized by you.
IMPORTANT: Modified (scam) versions of this application are easy to build so I encourage you to download WiiTweet only from the link provided at this page or using the Homebrew Browser.
- 1 Features
- 2 Authorizing WiiTweet
- 3 Local password support
- 4 Browsing
- 5 Keyboard
- 6 Authorization Flow
- Browse timelines
- Follow/Unfollow users
- Tweet, favorite, retweet, reply tweets
- Browse favorited tweets
- See followers and followed users
- See tweets you are mentioned in
- Search tweets and users
- Multiple profiles can be saved
- Your language's characters can be added to the keyboard
WiiTweet authorizes itself using the PIN-based authorization as suggested by Twitter and gives you three ways of doing so: visiting an URL using an external device, visiting an URL using the Internet Channel and providing your Twitter username/password. Read Authorization Flow below to get a more detailed explanation of how and why WiiTweet gets authorized by you.
Using an external device
An URL appears on screen, you go there from your computer/phone/another Wii, get your PIN and enter it to WiiTweet.
Using the Internet Channel
WiiTweet launches your Internet Channel and you get your PIN there. You have to go back to WiiTweet and select the corresponding profile to enter the PIN. Slow but useful to people with no access to an external device at the time.
Providing your username and password
You are asked for your Twitter username and password and WiiTweet authorizes itself. This is still PIN-based authorization but WiiTweet gets and reads the PIN automatically. Your password is not stored and you will not need it again to use WiiTweet.
Local password support
If you set a local password it will be needed to access your profile. Use this if you want to protect your privacy from people with access to your Wii.
Your OAuth credentials are saved at your SD/USB. If you do not set a local password they will be stored in plain text. If you set a local password your credentials will be encrypted.
WiiTweet is built around what I call a "river" which is a stack of "units" (which are either profiles, tweets or users) you can interact with. Units have a foreground and a background, to see the background of a unit place the cursor on it and hold B. If you want to browse to the previous river (page) you loaded press (-). Press (+) to browse to the next one. Another thing that could trick you a little is: when clicking on a Tweet, if you click the profile picture (the leftmost 70 pixels) you will browse to the author's timeline, if you click anywhere else the brief tweet prompt will appear.
Keyboard layouts are configurable/remappable allowing you to use any character included in the font WiiTweet uses. WiiTweet comes with a keyboard map with some unicode icons to show this feature off.
|Acc only||Enter acc mode|
The accelerometer keyboard is currently poorly tuned and practically unusable.
Using custom keyboard maps
- Keyboard map files must be placed in the /apps/wiitweet/kbmaps/ folder of your loading device.
- The file must be named keyboardmapX where X is the position you want it to be.
- If you place a keyboardmap0 file it will overwrite the default keyboard.
- Do not skip positions. If you have a keyboardmap1, a keyboardmap2 and a keyboardmap5 file WiiTweet will not load keyboardmap5.
Making custom keyboard maps
Use this script to generate keyboard map files.
Note: This is intended to be a simplified explanation of what happens during authorization. Consider reading Using OAuth at the Twitter developers site or the OAuth 2 specification for more technical information.
Twitter uses OAuth to provide authorized access to its content because it does not require users to share their passwords with 3rd party applications (such as WiiTweet), increasing account security.
How OAuth works
When registering WiiTweet Twitter gave me two random, unique strings to identify it. Such strings are used as signatures. When a new user wants to authorize WiiTweet it sends a "Somebody wants to authorize me" message to Twitter and signs it, letting Twitter know WiiTweet sent the message. Twitter answers with a "Prove me that's true" message containing an URL WiiTweet must ask the user to visit.
In the mentioned URL the user is asked (if he/she is not already) to log in. This is the only time the user has to provide his/her username and password and these are only provided to Twitter. The user is prompted to authorize WiiTweet and gets a PIN after doing so. That PIN is a "If WiiTweet gets this PIN then it was true" check.
Back at WiiTweet the user is asked to enter the PIN he/she got from Twitter, which is sent back. Twitter answers with two random, unique strings that identify this user-application relationship. Such strings are used to sign every action an user does within WiiTweet, letting Twitter know they are authorized by the user.
Changing your Twitter password will not terminate your relationship with any application you authorized using OAuth. You have to revoke the access through your account settings at Twitter's website.