{"id":342,"date":"2011-06-29T08:16:57","date_gmt":"2011-06-29T15:16:57","guid":{"rendered":"http:\/\/kai.mactane.org\/blog\/?p=342"},"modified":"2011-06-29T08:16:57","modified_gmt":"2011-06-29T15:16:57","slug":"the-difference-one-site-can-make","status":"publish","type":"post","link":"https:\/\/kagan.mactane.org\/blog\/2011\/06\/29\/the-difference-one-site-can-make\/","title":{"rendered":"The Difference One Site Can Make"},"content":{"rendered":"<p>Only a year ago, I was against infinite scroll. In design meetings, I&#8217;d point out the way it breaks various aspects of the scroll bar. (You can&#8217;t tell how far through the full data-set you are; dragging the &#8220;thumb&#8221; down causes it to suddenly change place,&nbsp;etc.)<\/p>\n<p>But now, I almost <em>expect<\/em> it when I&#8217;m scrolling through certain types of web pages. <strong>It&#8217;s slightly disorienting<\/strong> to me when I bump into the bottom of a page and have to manually click &#8220;next&#8221; or&nbsp;whatever.<\/p>\n<p>What happened? In a word: New&nbsp;Twitter.<\/p>\n<p>Okay, it&#8217;s not really &#8220;new&#8221; Twitter any more (it was rolled out <a href=\"http:\/\/en.wikipedia.org\/wiki\/Twitter#Growth\">from September through October of 2010<\/a>&nbsp;&mdash; less than a year ago, but those 9 months are an eternity in Internet time). But still, that roll-out was the impetus for my change in opinion. Twitter, a site I use every day, changed its UI and started doing infinite scroll. And now that interaction is a part of my daily life, and somewhere along the way, I got used to it. And now I <em>expect<\/em> it, at least in certain&nbsp;cases.<\/p>\n<p>And it&#8217;s because one site changed its interface. And because that one site is one I use many times every&nbsp;day.<\/p>\n<p>Logically speaking, there&#8217;s no reason why I should expect, for example, Google&#8217;s search results or my Dreamwidth reading page or TechCrunch&#8217;s front page to behave like Twitter does. One site&#8217;s UI shouldn&#8217;t&nbsp;&mdash; and doesn&#8217;t&nbsp;&mdash; have a damn thing to do with any other site. But <strong>the things we use frequently shape our habits<\/strong>, and that includes habits of&nbsp;thought.<\/p>\n<p>As a side effect of my having gotten used to Twitter&#8217;s infinite scroll, I&#8217;ve gotten far less inclined to check the position of the scroll-bar &#8220;thumb&#8221; to see how far through the page I am&#8230; except on the kinds of pages that I <em>expect<\/em> to not have infinite scroll. For example, an article or story has a natural end, and it just makes sense for a calendar to be paginated.<\/p>\n<p>But blogs? Or search results? Or anything that doesn&#8217;t have a natural break-point in it? There&#8217;s no reason why these things should require me to find the &#8220;load more&#8221; link. And there&#8217;s <em>really<\/em> no reason why that link should load stuff in a whole new page. Dynamic pagination with <a href=\"http:\/\/kai-mactane.dreamwidth.org\/?skip=40\">URL parameters like &#8220;?skip=40&#8221;<\/a> was always a kind of awkward idea; it&#8217;s just that there didn&#8217;t used to be anything better. But now there&nbsp;is.<\/p>\n<p>Right? I mean, that really <em>is<\/em> the case, isn&#8217;t it? I don&#8217;t just think so because one of the sites I use every day has retrained the way I think&#8230;&nbsp;right?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Only a year ago, I was against infinite scroll. In design meetings, I&#8217;d point out the way it breaks various aspects of the scroll bar. (You can&#8217;t tell how far through the full data-set you are; dragging the &#8220;thumb&#8221; down causes it to suddenly change place,&nbsp;etc.) But now, I almost expect it when I&#8217;m scrolling [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[23,8,9],"_links":{"self":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/342"}],"collection":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/comments?post=342"}],"version-history":[{"count":1,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/342\/revisions"}],"predecessor-version":[{"id":343,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/342\/revisions\/343"}],"wp:attachment":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/media?parent=342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/categories?post=342"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/tags?post=342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}