News for hackers. Stuff that matters.
Re:Twitter's UX: Separate the hits from the geekhacks by adamhowell on Tuesday October 19, 2010 @02:53PM (#1808273)
I don't usually quote pg, but I think in this case it's relevant:

"Old Twitter is what you'd get if an engineer brought New Twitter to Steve Jobs, and Steve beat on him relentlessly to simplify it."

(http://twitter.com/#!/paulg/status/25998745559)

To me adding a file upload button, a To:/CC: field, a link field, etc. etc. would be even worse.

The beauty of an API is that power users can download and/or signup for apps that add on to the original service in the exact, fussy way they want. And non-power users can just type into a textarea.

Re:Twitter's UX: Separate the hits from the geekhacks by kyro on Tuesday October 19, 2010 @03:44PM (#1808439)
I noticed upon clicking that link that Twitter has broken my back button functionality. I get redirected to the Twitter home page, and subsequent clicking of the back button takes me back to pg's status.
Re:Twitter's UX: Separate the hits from the geekhacks by semanticist on Tuesday October 19, 2010 @09:25PM (#1809572)
If you click 'back' again before the Twitter home page loads, it behaves correctly. (That is, basically double-click 'back' from pg's tweet.)

I guess it's because Twitter is inserting things into your page history to make its AJAXy interface work with forward/back buttons. These things are a mixed bag of useful and fragile.

Re:Twitter's UX: Separate the hits from the geekhacks by patrickaljord on Tuesday October 19, 2010 @04:45PM (#1808681)
That's a firefox bug.
Re:Twitter's UX: Separate the hits from the geekhacks by kyro on Tuesday October 19, 2010 @05:21PM (#1808812)
I'm using Safari.