Prior work established the benefits of server-recorded user engagement measures (e.g. clickthrough rates) for improving the results of search engines and recommendation systems. Client-side measures of post-click behavior received relatively little attention despite the fact that publishers have now the ability to measure how millions of people interact with their content at a fine resolution using client-side logging. In this study, we examine patterns of user engagement in a large, client-side log dataset of over 7.7 million page views (including both mobile and non-mobile devices) of 66,821 news articles from seven popular news publishers. For each page view we use three summary statistics: dwell time, the furthest position the user reached on the page, and the amount of interaction with the page through any form of input (touch, mouse move, etc.). We show that simple transformations on these summary statistics reveal six prototypical modes of reading that range from scanning to extensive reading and persist across sites. Furthermore, we develop a novel measure of information gain in text to capture the development of ideas within the body of articles and investigate how information gain relates to the engagement with articles. Finally, we show that our new measure of information gain is particularly useful for predicting reading of news articles before publication, and that the measure captures unique information not available otherwise.
A wee old women came in and said "I've a question. Why does page 7 in all the books I take out have the 7 underlined in pen? It seems odd."
"What?" I say, thinking she might be a bit off her rocker. She showed me, and they did.
I asked if she was doing it, she said she wasnt and showed me the new book she was getting out that she hadnt even had yet. It also had the 7 underlined! "I don't know, maybe someone really likes page 7?" I said, assuming of course that there is a serial killer in the library.
I checked some other books. Most didn't have it, but a lot in this genre did - they're "wee old women" books (romances set in wartime Britain etc). Lots of underlined 7s. The woman who pointed it out shrugged and went on her way, "just thought you should know".
My manager came back from doing arts and crafts with some of the kids and I decide to tell her about the serial killer in the library.
And that’s how I found out that a lot of our elderly clientele have secret codes to mark which books they’ve read before.
Our computers do it automatically but many have been doing it since before that was possible, so Esther might underline page 7, while Anne might draw a little star on the last page, and Fred might put an “f” on the title page. Then when they pick it up, they can check!
It’s quite clever really but now I’m dying to just underline page 7 of every new wee old women book we get in.
So, good news: there’s not a serial killer in the library whose MO include the number 7 and wartime romances. Bad news: people are defacing books rather than just asking us to scan them (smiling face with smiling eyes)
I'm now concerned that the amount of people enjoying this thread means there's going to be a new spate of readers using secret codes - apologies to librarians everywhere!
(although, in truth, I find it hard to be annoyed about it - better than torn pages and felt pen graffiti!)
(Also, I am new to the library job, hence why I hadn't seen it before! The library and our customers are great though (smiling face with smiling eyes))
Just had another victim of the page 7 vandal returned!!!
(Now checking every book that looks like it might be their taste...)
This is such an interesting little story including some cultural anthropology.
Our tech columnist tried to skip digital news for a while. His old-school experiment led to three main conclusions.
A somewhat link-baity headline, but overall a nice little article with some generally solid advice. I always thought that even the daily paper was at too quick a pace and would much prefer a weekly or monthly magazine that does a solid recap of all the big stories and things one ought to know, that way the stories had had some time to simmer and all the details had time to come out. Kind of like reading longer form non-fiction of periods of history, just done on a somewhat shorter timescale.
Gentle Reader gives you the freshest content in an easy-to-read format with no clutter and no ads. Add your favourite websites and Twitter accounts or discover new articles by exploring what other readers are bookmarking based on your interests. That way you can save time and hassle by efficiently combining RSS feeds, Twitter feeds, bookmarking and read-later services all in one app. What's more you have complete control over if, when, and how you discover new information with our unique matching function.
This is an interesting looking app. Sadly no Android version yet, so I’m taking a peek at it on the web. An interesting melange of features, but certainly not perfect for my needs yet. Has some interesting discovery type tools, but I’ll need to dig in further to test these out.
One of their default feeds, while solid, appears to only allow a synopsis sentence or two instead of the full feed, so it’s not the best example for the site to feature.
Now that the social network is changing what shows up in your feed, you’ll have to go elsewhere for current news.
I’ll particularly agree with how good I find Nuzzel to be, though I will say that I do take heavy advantage of a variety of highly curated Twitter lists which I’m sure helps the algorithm for the quality of news I get back out of the system.
I would prefer more transparency about how those that use algorithms are doing so.
Some of these don’t amount to much more than glorified RSS feed readers, and I’m shocked that the state of the art of the area isn’t much further along than it was a decade ago.
As of October 30, 2016, I’ve slowly but surely begun posting what I’m actively reading online to my blog.
I’ve refined the process a bit in the last couple of weeks, and am becoming relatively happy with the overall output. For those interested, below is the general process/workflow I’m usi...
I totally fell down on the job last year (compared to my goal), but I did read a lot of additional material online instead and lot of what I did read, (but didn’t necessarily finish toward my goal) was of a highly dense/technical nature. We’ll do better this year.
After more than five years of operation, the Readability article bookmarking/read-it-later service will be shutting down after September 30…
I really wish I’d heard about this before September! And certainly before today… I know I used it fairly frequently in the early days of the service. I do remember that they did have a some nice functionality for sending articles to the Amazon Kindle too. Not sure how much data I may have lost in this particular shutdown, but I do wish I’d had a chance to back it up.
I am glad that bookmarks are one of the post types that I’m now saving by posting on my own site first though. For more of my thoughts on these post types, take a look at:
Today, we’re excited to announce that Instapaper is joining Pinterest. In the three years since betaworks acquired Instapaper from Marco Arment, we’ve completely rewritten our backend, overhauled our mobile and web clients, improved parsing and search, and introduced tons of great features like highlights, text-to-speech, and speed reading to the product.
Thoughts on post types/kinds relating to reading within the Indieweb construct
This morning while breezing through my Woodwind feed reader, I ran across a post by Rick Mendes with the hashtags #readlater and #readinglist which put me down a temporary rabbit hole of thought about reading-related post types on the internet.
I’m obviously a huge fan of reading and have accounts on GoodReads, Amazon, Pocket, Instapaper, Readability, and literally dozens of other services that support or assist the reading endeavor. (My affliction got so bad I started my own publishing company last year.)
READ LATER is an indication on (or relating to) a website that one wants to save the URL to come back and read the content at a future time.
I started a page on the IndieWeb wiki to define read later where I began writing some philosophical thoughts. I decided it would be better to post them on my own site instead and simply link back to them. As a member of the Indieweb my general goal over time is to preferentially quit using these web silos (many of which are listed on the referenced page) and, instead, post my reading related work and progress here on my own site. Naturally, the question becomes, how does one do this in a simple and usable manner with pretty and reasonable UX/UI for both myself and others?
Currently I primarily use a Pocket bookmarklet to save things (mostly newspaper articles, magazine pieces, blog posts) for reading later and/or the like/favorite functionality in Twitter in combination with an IFTTT recipe to save the URL in the tweet to my Pocket account. I then regularly visit Pocket to speed read though articles. While Pocket allows downloading of (some) of one’s data in this regard, I’m exploring options to bring in the ownership of this workflow into my own site.
For more academic leaning content (read journal articles), I tend to rely on an alternate Mendeley-based workflow which also starts with an easy-to-use bookmarklet.
I’ve also experimented with bookmarking a journal article and using hypothes.is to import my highlights from that article, though that workflow has a way to go to meet my personal needs in a robust way while still allowing me to own all of my own data. The benefit is that fixing it can help more than just myself while still fitting into a larger personal workflow.
A Broader Reading (Parent) Post-type
Philosophically a read later post-type could be considered similar to a (possibly) unshared or private bookmark with potential possible additional meta-data like: progress, date read, notes, and annotations to be added after the fact, which then technically makes it a read post type.
A potential workflow viewed over time might be: read later >> bookmark >> notes/annotations/marginalia >> read >> review. This kind of continuum of workflow might be able to support a slightly more complex overall UI for a more simplified reading post-type in which these others are all sub-types. One could then make a single UI for a reading post type with fields and details for all of the sub-cases. Being updatable, the single post could carry all the details of one’s progress.
Indieweb encourages simplicity (DRY) and having the fewest post-types possible, which I generally agree with, but perhaps there’s a better way of thinking of these several types. Concatenating them into one reading type with various data fields (and the ability of them to be public/private) could allow all of the subcategories to be included or not on one larger and more comprehensive post-type.
Not including one subsection (or making it private), would simply prevent it from showing, thus one could have a traditional bookmark post by leaving off the read later, read, and review sub-types and/or data.
As another example, I could include the data for read later, bookmark, and read, but leave off data about what I highlighted and/or sub-sections of notes I prefer to remain private.
A Primary Post with Webmention Updates
Alternately, one could create a primary post (potentially a bookmark) for the thing one is reading, and then use further additional posts with webmentions on each (to the original) thereby adding details to the original post about the ongoing progress. In some sense, this isn’t too far from the functionality provided by GoodReads with individual updates on progress with brief notes and their page that lists the overall view of progress. Each individual post could be made public/private to allow different viewerships, though private webmentions may be a hairier issue. I know some are also experimenting with pushing updates to posts via micropub and other methods, which could be appealing as well.
This may be cumbersome over time, but could potentially be made to look something like the GoodReads UI below, which seems very intuitive. (Note that it’s missing any review text as I’m currently writing it, and it’s not public yet.)
Ideally, better distinguishing between something that has been bookmarked and read/unread with dates for both the bookmarking and reading, as well as potentially adding notes and highlights relating to the article is desired. Something potentially akin to Devon Zuegel‘s “Notes” tab (built on a custom script for Evernote and Tumblr) seems somewhat promising in a cross between a simple reading list (or linkblog) and a commonplace book for academic work, but doesn’t necessarily leave room for longer book reviews.
I’ll also need to consider the publishing workflow, in some sense as it relates to the reverse chronological posting of updates on typical blogs. Perhaps a hybrid approach of the two methods mentioned would work best?
I’ll keep thinking about the architecture for what I’d ultimately like to have, but I’m always open to hearing what other (heavy) readers have to say about the subject and the usability of such a UI.
Please feel free to comment below, or write something on your own site (which includes the URL of this post) and submit your URL in the field provided below to create a webmention in which your post will appear as a comment.