News for hackers. Stuff that matters.
Re:New Twitter Has Become Browser Poison by russ on Monday January 17, 2011 @04:01PM (#2113455)
Re:New Twitter Has Become Browser Poison by 1337p337 on Monday January 17, 2011 @07:53PM (#2114104)
As much as I love the minimal UI, the mobile version is crippled by comparison. If they flesh out the features (which can be done without bloating it) or they deprecate the old UI like they're threatening, then I'll use it constantly.

The old UI works great and does not monopolize CPU, unlike the new one which, on load, eats 100% of one core on whatever machine I'm using (to say nothing of the really wide horizontal resolution required).

Re:New Twitter Has Become Browser Poison by mike-cardwell on Tuesday January 18, 2011 @05:10AM (#2115309)
Trouble with the mobile version is it doesn't support https for some reason and so can't be used safely on an untrusted network. The normal version supports https though...
Re:New Twitter Has Become Browser Poison by kragen on Monday January 17, 2011 @08:20PM (#2114169)
Yeah, I've been using it today. I want to love it but I can't. No DM count on the screen (to save three bytes?!), no user icons, no way to tell that I've gone over 140 characters.
Re:New Twitter Has Become Browser Poison by sandofsky on Monday January 17, 2011 @09:17PM (#2114285)
Are you using a really low end user agent to try to access the site? I don't know what's turned off for lower end browsers, but I just tested in desktop Webkit. There's a character count in the upper right of the tweet box. There are user icons, unless you clicked the "images off" link.

As for total DM count, that isn't really possible right now. The app is just another API client, and the DM API endpoint only provides the last 20 DMs.

Re:New Twitter Has Become Browser Poison by kragen on Monday January 17, 2011 @10:55PM (#2114504)
No, FF3.
Re:New Twitter Has Become Browser Poison by wahnfrieden on Tuesday January 18, 2011 @01:11AM (#2114825)
Just a tip -- relaunch FF in safe mode (sans extensions etc.) and verify before reporting bugs like that, please.