I have a device that tweets using the API. It is a microcontroller that is hooked to garage doors http://www.toyz.org/GarageBot
http://www.toyz.org/images/GarageBot_sm.jpg It is a small box mounted on the wall in the garage as shown in the photo. Unlike a full PC, it has no hard drives and draws very little power. There is no screen or keyboard. All interaction is via the net. Plug it in and it boots and starts doing its thing. You don’t need to think about it. I added LEDs to provide some indication that the device was running. oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. It's too bad Twitter doesn't provide a way for the user to authorize Basic Auth for their own Twitter ID under certain terms, or some other lightweight Twitter API option. By forcing oAuth, Twitter has substantially raised the bar for API interaction and particularly for embedding Twitter into lightweight devices. Twitter used to be a uniqely lightweight API - not anymore.
