Twitter to move away from Hashbangs

Post by alexmic » Tue, Feb 21, 2012, 5:20 PM UTC

jamesgeck0 wrote: post #78

Smudge wrote: post #67

Earlier quoted context omitted.

It didn't break back. It just hijacked the browser's history by adding a 2nd page load in order to inject the "!#" into the address bar. Pressing back would, as a result, act like the refresh button.

I don't follow you. Changing the functional behavior of the back button _sounds_ a lot like broken.

I'm not sure that this is the case.

Back works as expected - it takes you to the previous page you were at. Fragment identifiers don't break the back button. That's all from a user perspective's point of view, which is mostly all that matters in the end.

If you look at this from a technical standpoint, then back is a refresh of twitter.com, yes.

Post by kragen » Tue, Feb 21, 2012, 8:38 PM UTC

nikcub wrote: post #3

Good. A lot of developers justified doing it in their own projects because Twitter and Gawker were doing it. Now that one of the headline sites is no longer using it (and will hopefully condem it) we can file this episode to history and never speak of it again. Edit: wouldn't it be awesome if Google (they did start this, afterall) would allow sites using hashbangs to auto-update all indexed URls

I'm particularly happy about this because I spent a bunch of time yesterday trying to get any of the current lightweight web browsers (Dillo and Links2; I couldn't get Arachne not to crash at startup, and I couldn't find the source to hv3) to log into either twitter.com or mobile.twitter.com, with no success at all. m.facebook.com worked, more or less, but no love from Twitter.

Apparently you can't log into Twitter without 64MiB of RAM, which is what Midori uses. Dillo and Links2 use 6MiB.

Hopefully this means they're switching to a more normal HTML interface and will become a web site instead of a DHTML application again.

Re: Twitter to move away from Hashbangs

Re: Twitter to move away from Hashbangs