10:45pm - battery @ 44%; downloaded AIM & beejive
.
.
.
12:45am - battery @ 3%
hmm... i was testing both rather heavily. received some errors. i'm sure the servers are overloaded.
but damn, my battery life!! i'm sure the allure will wear off in a few days and i won't be all over it.. or will i?
Tweetie won't get push just because the developer wants it. It's a Twitter thing (twitter runs their servers, Tweetie just grabs content). And because Twitter's servers would be the ones pushing an update to your phone, it'd have to know a) what phone to push it to (handled by the app) but more importantly b) what app to push it to as there could be several Twitter apps installed on your phone.
Then you have to think of the logistics of who's going to pay for the added server load. You'd have to admit that the developers of Twitter apps are basically making their money off the services of Twitter (which is pretty much unheard of in most circles), and now they'd be asking more from them. Twitter is stuck between a rock and a hard place in figuring out how to support the MILLIONS of users needed to make sure the service ran smoothly.
Basically what it all boils down to is that right now, Twitter makes no money, and until it does, push notifications will suck due to unreliability and inadequate server power.
Anyone know if AIM in Beejive offers a huge advantage over the official AIM client? I pretty much only use AIM, with the occasional use of Live Messenger, but I'm kind of tempted to get Beejive. It's just hard to justify when the free AIM client also has push notifications now.
AIM Free is beyond glitchy anyone else seeing this even rebooted
Hmm. Tweetie just has to run their own server. It's not that expensive to setup a virtual server and since it's not a free app I see no issues with this. Then what happens is that twitter connects to the tweetie virtual server where your login details are stored. The virtual server connects to the apple push notification server which maintains an IP connection to your device.
twitter message in -> tweetie server -> apple server -> iphone.
So it's not a twitter issue it's a tweetie issue.
Beejive dosen't work here.
Error
Connection failed on all fallback ports
Beejive dosen't work here.
Error
Connection failed on all fallback ports
I got the beejive update and I have not been able to log on to yahoo messenger since! It keeps saying "Error Connection failed on all fallback ports". I have no problem getting on through Windows Live though. I want to try to delete the app, then re-download and see if that fixes the problem but not sure it's a good idea because iTunes is still showing an older version of the app.
Anybody else having this problem with Yahoo (or any other messenger)? If so how did you resolve? Is there something I can do, or is it just something on the back end that I can't do anything about?
Also anybody know if the update is available should I be able to delete current version then re-download again with version with push?
yahoo changed something on their system my Adium stopped working these last few days until they updated the software.
yep, yahoo sometimes kinda sucks
I understand that, but for example... you quit the app and after 24 hours you have to re-start the app to sign in. I think that is stupid.
I understand that, but for example... you quit the app and after 24 hours you have to re-start the app to sign in. I think that is stupid.
I have the same problem. I had a friend send me a message which got pushed to my phone. When i jumped on my computer to chat, it still sent the messages to my phone. Was very annoying. Any one have any clues on how this can be changed?
Hmm. Tweetie just has to run their own server. It's not that expensive to setup a virtual server and since it's not a free app I see no issues with this. Then what happens is that twitter connects to the tweetie virtual server where your login details are stored. The virtual server connects to the apple push notification server which maintains an IP connection to your device.
twitter message in -> tweetie server -> apple server -> iphone.
So it's not a twitter issue it's a tweetie issue.