Profile_bird

Hey there! Adium is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving Adium's updates.

Already using Twitter
from your phone? Click here.

Adium

  1. Double Yahoo! messages will be fixed in b8.
  2. @weirduncledave It already has it.
  3. 1.3.5rc1: http://tr.im/pfaB libpurple changes (2.5.7): http://tr.im/pfam pidgin-facebookchat changes (1.51): http://tr.im/pfao
  4. Working on adding libpurple 2.5.7 to a 1.3.5 release. More work than expected, Facebook plugin's update added a new library requirement.
  5. 1.4b7, fixing the Yahoo issues (and a few others, like growl lag) http://beta.adium.im
  6. @Zerthis Advanced > Message Alerts
  7. Yeah, all of the site seems down. Hg mirror: http://tr.im/oMtM 1.4b6 download: http://tr.im/oMtR 1.3.4 download: http://tr.im/oMtX
  8. @jrome http://trac.adium.im/wiki/U...
  9. For the record, it will take about 584 942 417 years to reach that if Twitter's tweets per second quadruples.
  10. Adium's safe from the Twitpocalypse, yes. In fact, we're fine until tweet #18,446,744,073,709,551,615.
  11. @MrMorganMiller Make sure you have at least 1 contact; the next update to 1.4's beta will fix this.
  12. @nealtucker Sort Alphabetically in the view menu.
  13. Twitter changed how OAuth permissions are granted for desktop apps, so currently Adium doesn't work. B7 will fix it whenever it's released.
  14. @wezfurlong yMous is a great one - http://bit.ly/h9ALz
  15. @solace A debug log would be helpful on http://trac.adium.im - but if it's ejabberd, I'm betting it's why.
  16. @solace Are you running an old version of ejabberd, or one that was improperly upgraded? Its bugs can cause that.
  17. @Rombus It's 0.75s, part of the Growl flood control. Thinking of ways to reduce the impact.
  18. @solace How do they "suck"? Haven't had any problems at all…
  19. @kleinmaetschke You can use a style that supports mention highlighting.
  20. @jackolas Hm, anything in the console? I've only seen it when an error presented itself in the back end.