Interesting... but maybe not effective for getting people to read your content. I scrolled around with my mouse and nothing was happening so after about 10 seconds I just clicked back.
EDIT: So I went backed and checked it out some more. Completely breaks my back button as they load 20+ URLs while I try to (jerkily) scroll through the text. under ideal circumstances this interface could be really cool, but I found it unusable.
I absolutely despise when sites do this. One scroll gesture and now I can't go back to the site I came from? Another common archetype for this behavior is sites that show a slideshow. I click through 20 slides, and now I can't get back to the page I came from. Webdevs: you can still have permalinks to each paragraph/slide/whatever without completely muddling the user's browser history! Use replaceState instead of pushState to mitigate this problem.
Browsers should evolve to account for this kind of abuse. Holding down the back button should present two options: One to list all the anchors you've been to on the current page (in this case, paragraphs on the page), and one list of your previous history stack that doesn't account for URL fragments/hashes.
> Browsers should evolve to account for this kind of abuse. Holding down the back button should present two options: One to list all the anchors you've been to on the current page (in this case, paragraphs on the page), and one list of your previous history stack that doesn't account for URL fragments/hashes.
Chrome does this (as I discovered when trying to escape this page)
Yeah, I was being polite calling it interesting. And I noticed the same broken back button behavior. When I figured out what it did, I almost edited my post. Really annoying.
