Arc90 Lab

That's why we love Arc90's Readability http://lab.arc90.com/experiments/readability/ No longer do we have to care what ugly fonts or color schemes people use when posting blog articles.

Irony yet again, the problem is with the font-stack. I guess you have a version of Helvetica that's not that readable. Only of they followed their own advice and tested it.Though this articles is nothing great and sorta ironic on this site but if you still want to read it - use Readability: http://lab.arc90.com/experiments/readability/ This is how it looks: http://img98.imageshack.us/img98/8523/201012030938.png

I think you need a link there to http://lab.arc90.com/experiments/readability/ : thought you just meant it wasn't readable! Readability is great: before that I was just copy & pasting to a text editor...

I recommend Readability: http://lab.arc90.com/experiments/readability/

Great post but arrgh, use this to read it: http://lab.arc90.com/experiments/readability/

Actually, it's why Readability (http://lab.arc90.com/experiments/readability/) and Instapaper Text (http://www.instapaper.com/extras) bookmarklets exist. They blocks all the ads and non-essential content, ensures columns are wide enough, and standardizes the fonts. They also work great for all those Typepad blogs with odd columns and tiny fonts.

I am with Apple. On the web I use readability (http://lab.arc90.com/experiments/readability) a lot. I am happy to be able to read with fonts readable for me. If I could I'll always surf using readability. For books I believe overriding designer choice by _yours_ is the best solution for a good read.

The Readability bookmarklet is pretty handy in this case. Also works great if you need to cleanup a page from Google cache. http://lab.arc90.com/experiments/readability/

Cool idea. The readability bookmarklet (http://lab.arc90.com/experiments/readability/) does a great job at extracting the main document text without having to compare to other files, though it's currently all client-side.

Try Readability ( http://lab.arc90.com/experiments/readability/ ) It's great for reading large quantities of text on the web.

I've recently started using Readability. Works great! http://lab.arc90.com/experiments/readability/

Gray on black, eh? Great place to plug Readability: http://lab.arc90.com/experiments/readability/

I love the content on this website; hate the horrible design. Before I discovered Readability, I always ended up using "View Source" to read the interviews. http://lab.arc90.com/experiments/readability/

I really recommend you to get the Readability bookmarklet from Arc90: http://lab.arc90.com/experiments/readability/ I don't use it that often, but when I do, it works great!

This may be out of place, and I have no doubt that Douglas Crockford is a genius and an all-around excellent human being. Also, I am pretty firmly in the substance over style camp of web design. Having said that, I find it pretty hard to accept webpages (in 2009!) that have this for design: <body bgcolor=linen> <h1 align=center><font size="+4">JavaScript:</font><br> Thank god for Readability... Updates: Yes, by Readability I mean http://lab.arc90.com/experiments/readability/ It's an outstanding little mini-app. If you don't know it, try it. Second, I want to clarify that what I quoted is literall the entire style for the whole page. I find that mind-boggling. (And, yes, I thought of PG's site.) Finally, the page was written in 2001, so my crack about 2009 isn't quite fair. Still, many people do update their sites.

Worth noting: Readability (http://lab.arc90.com/experiments/readability/) makes these pseudo-blog-posts readable. Also, nice article, but why not post it on your blog?

nice idea and nice realization, too! it works pretty good! if you can't read the password after you've typed it in, try to mark it with SHIFT + LEFT-/RIGHT-ARROW or SHIFT + HOME/END :) by the way: the guys from arc90.com cook up pretty cool things in their labs, like the greatly useful Readability bookmarklet http://lab.arc90.com/experiments/readability/

> That format may be printer-friendly, but it is significantly less readable on-screen. The text fills the browser window, making each line far too long to read comfortably. Best of both worlds: Open the "printer friendly" version of an article and execute the readability javascript bookmarklet: http://lab.arc90.com/experiments/readability/

I highly recommend this plugin for anyone visiting forbes.com: http://lab.arc90.com/experiments/readability/

A few of the responses here and in the blog comments are up in arms about your suggestion to treat mobile and desktop users the same. The comments that intend to contrast the differences between processing power, dimensions, and available network resources of "desktop" versus "mobile" devices are predicated on the notion that users do want you to send gobs of data that consume more resources when they are on desktop machines. In general, however, they don't. Witness the comments in "Your social widgets are losing you visitors right now" (http://news.ycombinator.com/item?id=1771607) and the popularity of Readability. (http://lab.arc90.com/experiments/readability/) Something I think (self-apologetic and self-described) Web "designers" and "UX experts" in the West don't realize is that bandwidth caps still exist even for home use, and in some places they are the norm. Given the reactions, it seems when people read the suggestion "serve the same content to all browsers", they see "serve mobile users the same content that you serve on your created-with-the-desktop-in-mind ('full') Web site". Perhaps this should be reworded to explicitly say the inverted form: "serve the same content on your full Web site as you serve on your mobile Web site." Surprise! Mobile users aren't the only ones who like to view content created with ease-of-consumption in mind. [Cue dissent pointing out that I did use the word "consumption", followed by some bullshit suggestion like "Mobile users…

Couple other links. Web version: http://marksy.arc90.com/ Small Writeup: http://lab.arc90.com/2013/02/20/marksy/

Marksy is both an online service (http://marksy.arc90.com) and a Chrome Extension (https://chrome.google.com/webstore/detail/marksy/glncdocnokppgopgpblpe… which lets you quickly convert between different markup languages. The full writeup is here: http://lab.arc90.com/2013/02/20/marksy/

That comment is incredible. Not only did Arment openly credit Readability for competitively spurring him, let's go back to the origin of the Readability bookmarklet (long before the app)- http://lab.arc90.com/2009/03/02/readability/ Our latest experiment was partly inspired by Marco Arment’s awesome Instapaper application (and equally awesome Instapaper iPhone app).

With more spark line: http://lab.arc90.com/2009/07/09/hashmask-another-more-secure-experimen…

Arc90 Labs had a similar thing around the same time too: http://lab.arc90.com/2009/07/09/hashmask-another-more-secure-experimen…

The "Reader" button appears to be a fork of Readability (http://downloadsquad.switched.com/2010/06/08/think-safari-reader-looks… Also of note, the original Readability was actually "partly inspired by" instapaper (http://lab.arc90.com/2009/03/02/readability/)

My old bookmarklets still work and the old site still seems to work fine (http://lab.arc90.com/experiments/readability/). It would be pretty foolish of them to break everyone's existing endpoints like that.

Sounds like someone needs to tell the Dyslexic Association of America about Readability (or maybe a dyslexic programmer should tweak it first). http://lab.arc90.com/experiments/readability/

Use Readability[1], and stop nagging. [1] http://lab.arc90.com/experiments/readability/

The readability bookmarklet works on code examples too: http://lab.arc90.com/experiments/readability/