Seems to me that TweetMarker will always be faster than Twitter
-- a lot smaller database, and a lot less data to send back to the
client. I think have the requests done serially instead of in
parallel would alleviate the timing problem.
BTW, this is my first time making any comments here. Thanks for
making such an awesome Twitter client for my Android devices!
I'd also like to see Tweet Marker loaded after Plume has
refreshed tweets. I turn off most automatic syncing to save battery
life (I can't recharge my phone during the day) but I switch
between my Android phone, iPad and iPod Touch (both running
Tweetbot). I have to have Plume update in the background every 15
minutes to keep everything synced but that's hurting my battery
Any update on this? My timeline never goes to the Tweet
Marker position because I have auto-refresh disabled (for battery
concerns). Swapping between Tweetbot on my iPad and Plume on my
phone is annoying to say the least since Plume never syncs to the
last read position.
@tb - I believe Tweetcaster just implemented a "jump to last
read" button or menu action so you can manually trigger going to
position marked by Tweet Marker, because they've been having a lot
of problems with their Tweet Marker feature. That might be a nice
feature for Plume to pick up (a menu action to manually trigger the
jump and/or Tweet Marker sync), for those of us who do have
problems with the auto-jump/auto-sync with Tweet Marker, or who
like to have auto-refresh disabled. That would give us manually
control of the whole process.
FWIW, the Tweet Marker/last read feature works much better for
me in recent versions of Plume than it used to. I have refresh set
to "at launch", though, I realize.