Wednesday, August 25, 2010

Updating Your Twibs Account

Greetings from Twibs!

This week Twibs made some changes to the way you a) log in to your account and b) update your Twitter account information displayed on

Regarding logging in, has asked that ALL applications built upon Twitter switch to what is known as "oAuth" for logging in. We won't bore you with technical details, but know that this method is much safer for users in the Twitter ecosystem.

How logging in has changed
Previously, when you went to login to, you entered your username and password directly from Now, you will need to click the button "Log in with Twitter", then you will be taken to where you enter your username and password, and will then be returned to where you can manage your account. The reason for this is to keep logging in happening at and no where else to reduce security vulnerabilities. So give it a try!

It's now easier to update your account.

Previously, updated your Twitter account information displayed on once a day, but as the system grew, and Twitter grew, many apps were not being updated regularly due to the number of updates our system had to process.

Now, EVERY TIME YOU LOG IN your account information will get updated. We will still do our best to keep your account up to date for you, but this gives you a way to manually update your information such as profile pic, follower count, etc without waiting for our automatic process to happen.

If you have any questions or comments, please email us at

Thanks, and have a great day.


  1. If you would, please update your address - I have lived here for over a year and a half and Twibs still has my address listed as theirs, I still get mail for Twibs, and Google wont remove Twibs from my address on Google Maps.


  2. All the information on this site is either bogus, out of date, or Twibs is no longer live. I tried well over a dozen times yesterday and this morning to register, and the server would never get beyond the "Adding" button. The e-mail address produces an error message thusly: Delivery to the following recipient failed permanently:

    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the server for the recipient domain by []. If you want to grow or even maintain a Web service you need to be on top of your own scripting and servers--and unlike the drop-down list below (where there is no choice for these issues) it is not a Google Account error.