hmmm - I guess I'm spoiled by mobile web clients like Dabr and Tweete linking the thumbnails in the timeline. I haven't used Tweet Deck or Twhirl for a while but I thought they did the same thing.
On 3/11/10, Levi Wallach <[email protected]> wrote: > What do you mean? Twitpics is not twitter but a website. It's true that > some twitter clients link to images, but none as far as I know actually > embed the images inline with the possible exception of Brizzly, but that's > just a web client, not a native one. Anyway, no WebOS client does this, > although with Twee if you click on the post it will load a new card that has > a thumbnail of a linked twitpic... > > Levi Wallach > blog: http://twelveblackcodemonkeys.com > tweet me @dvdmon (http://twitter.com/dvdmon) > > > On Thu, Mar 11, 2010 at 2:20 PM, ldouglas <[email protected]> wrote: > >> Is it also expanding twitpics, etc? >> >> -----Original Message----- >> From: "Levi Wallach" <[email protected]> >> To: [email protected] >> Sent: 3/11/10 12:16 PM >> Subject: Re: [Treo] Selective disable Tweed update >> >> This is definitely a problem with Twee and with Spaz. It seems as they >> update there doesn't seem to be a way to tell them to remove older tweets >> from memory, so you end up with a large list of items which bog down >> things. I've ended up eventually getting the dreaded Too Many Cards >> error, >> then I close and reopen, and make sure the JS heap has been cleared (via >> JStop), and that at least temporarily fixes the problem, but I definitely >> think there's an issue here. It seems a bit bizarre to me, I mean >> basically >> what you are dealing with is what about 200 or 250 bytes per tweet? Even >> with 100 tweets, that's what, 250K? These shouldn't got down the Pre >> which >> I think has something like 40MB of ram left over after system stuff runs, >> right? I don't really get it...
