A cool project from Freescale Semiconductor by Carlos Musich and Luis Garabito: MCU control and monitor with Twitter (PDF)
It demonstrates using the Freescale TWR-K60N512- KIT ($139 from Digikey) and the SuperTweet.net API to pull data from the MCU and publish to a twitter account.
PROTECT IP / SOPA Breaks The Internet
http://vimeo.com/31100268
About this video:
"Tell Congress not to censor the internet NOW! - http://www.fightforthefuture.org/pipa
PROTECT-IP is a bill that has been introduced in the Senate and the House and is moving quickly through Congress. It gives the government and corporations the ability to censor the net, in the name of protecting "creativity". The law would let the government or corporations censor entire sites-- they just have to convince a judge that the site is "dedicated to copyright infringement."
The government has already wrongly shut down sites without any recourse to the site owner. Under this bill, sharing a video with anything copyrighted in it, or what sites like Youtube and Twitter do, would be considered illegal behavior according to this bill.
According to the Congressional Budget Office, this bill would cost us $47 million tax dollars a year -- that's for a fix that won't work, disrupts the internet, stifles innovation, shuts out diverse voices, and censors the internet. This bill is bad for creativity and does not protect your rights."
A quick reminder. If you want to get help with the Supertweet.net API, the quality of the information you provide about the exact nature of the problem you're having is directly proportional to the chance of your problem getting resolved by the Supertweet.net volunteers. The more details you provide, the more likely we will be able to identify and fix your problem. On the other hand, the more ridiculous and incomplete your request is, the more likely your problem isn't going to get resolved.
Specifically, if you think the Supertweet.net services is the problem, we need the exact request (what is being sent over the wire) and the exact response (what is coming back from the server, on the network), with passwords removed of course, but including IP addresses. Your code may be interesting, and we may or may not be able to help with specific coding issues, but what we really need to resolve any service issues is what is being sent over the network and what you're getting back from the SuperTweet.net API, i.e. a capture of what is going over the wire.
In most cases, a tweet like "it's not working" isn't going to get your specific problem resolved. And resending that same useless tweet 50 times isn't going to move things any closer to a resolution either.
Use forum to post the full details of any issues you're having with the service. That's how you will get help: http://www.supertweet.net/community
We had a partial outage of the SuperTweet.net API service and a full outage of the main www.SuperTweet.net site (for logging in and setting up new accounts). The root cause of the outage was immediately resolved and the service restored as soon as we realized www.Supertweet.net was down.
Unfortunately, our notification systems failed, and so none of our (all volunteer) admins were notified of the outage for several hours. We are looking into why all of the notification systems failed and we have added two additional notification systems as backups to hopefully prevent another issue of this type in the future.
We apologize for any inconvenience this outage may have caused.
With the new Twitter API permission model, if you need access to your direct messages in your apps that use the SuperTweet.net API, for existing accounts, you need to re-authenticate to again have access to your DMs. Here is the procedure:
Now, when you sign in, Twitter should inform you that the MyAuthAPIProxy app will have access to your direct messages.
Note: You only need to go through this procedure if (a) you signed up prior to today AND (b) you want to use the SuperTweet.net API to access your direct messages.
Prospectively, all new sign-ups automatically have RW+DM access.
