Skip to main content

Troubleshooting Twitter @Anywhere's write permissions

With the recent launch of @Twitter's @Anywhere API there have been a number of developers having issues with the follow button and the Tweet Box not working. This stems mostly from a bug where new applications created on would default to read only access.

If are having problems using @Anywhere try this simple step by step guide.

  1. Check that your application has "Read and Write" as the "Default access type". If not edit your application settings so it does. You can do that on
  2. Check that your @Twitter account's access token for said application has "read and write access". If not revoke access and re-authorized from the website you are testing @Anywhere from. You can find out the access type on
  3. Delete your cookies. Specifically the "twttr_anywhere" cookie for the domain hosting the @Anywhere code. You can read more about clearing your cookies
Have you had any other issues with @Anywhere? What solutions have you had?


  1. I have an issue but not a solution yet. On firefox 3.6.3, once your initialise the twitter anywhere object and the Iframes are created, the page becomes slightly wider. this creates a scrollbar for side scrolling which is a bit annoying

  2. Sounds like you are putting the @Anywhere code somewhere where the inserted iframe is wider then the element it is being inserted into. Try playing with your CSS.


Post a Comment

Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

In_reply_to_status_id mentions:

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…