Fun project, but am I the only one that finds the zig-zag flow of the "Fb-timeline" difficult to follow -- or atleast more difficult than a linear feed?
What are the advantages of this style of timeline - other than less scrolling?
What are the advantages of this style of timeline - other than less scrolling?
Lets take this to the extream. Lets say you had a serverlog with 1 million entries and you had to parse it by hand for what ever reason. would you rather see
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
or this
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
[Jun 10, 12:32] /index.html 200 54ms nick
Just because I'm browsing my friends activity doesn't mean that I want to waste time trying to follow their god awful timeline with the jumps and the zig zags and the figureing out what came before what.
The other thing you're not considering is that Facebook displays more than just text. If you're displaying images inline as well as text, it's going to be more compact if you interpolate each post in a zig-zag fashion rather than making posts vertically serial.
The example you provided doesn't really illustrate why timeline is bad for a website because it's an example provided in a completely different context.
tl;dr Website design is not command line interface design.
I would expect with a better design the back-and-forth would flow would look a lot easier on the eyes.
Is it just because facebook does it, or do you have some other strong reason for using it.
The main goal is to be able to take anyone's public github profile and assess what they have done in the open source world. For example, a job candidate who gives sends along their profile. Right now their public github profile page doesn't do a great job distilling that information.