#1 is a nice, simple frontend for the Readability API. Just enter the URL of a page with something you want to read on it, and it extracts the content without any sidebars, ads, or other junk and gives it to you in an easy-to-read format.
#2 is Squirt, a speed-reading application that takes the text of any webpage and displays it to you one word at an adjustable speed. The default is 450wpm I think, but after you make an adjustment, it remembers what speed you want for next time. If you need to read a part more carefully or go back because you missed something, that’s easy. Hit the spacebar to pause and it will show the context, then use the left and right arrows to move around. Hit the spacebar again to resume speed reading. Another awesome feature is that it tells you exactly how long it will take to finish if you don’t stop, so you can decide if it’s worth your time or not.
The two work really well together, as squirt alone will sometimes grab text you don’t want. What I do is “Clean” a page by clicking on the bookmarklet, and then sometimes hit “Squirt” to speed read it.
2 is Squirt, a speed-reading application that takes the text of any webpage and displays it to you one word at an adjustable speed. The default is 450wpm I think, but after you make an adjustment, it remembers what speed you want for next time.
Which speed are you using at the moment and how long did it take you to come to that speed?
I started at 350 and that’s still what I use most of the time. For light, non-technical articles, I can do 450, but it’s a bit uncomfortable to focus that hard and I do miss things occasionally. I can usually tell if it was important or not though, so I know if I need to go pause and rewind. After playing with speedreeding off and on for a few years, I’ve come to the conclusion that it’s definitely possible to read faster than I normally do with equal comprehension, but that there really is a limit and the claims you see from speedreading courses are hyperbolic. The thing I like about Squirt is that it eliminates the need to use a pacer.
It still doesn’t work. It could be an extension, but I was guessing it was just the browser. I’m using Chrome. javascript:alert(“test”) seems to work if I type it direction or use a bookmark. It doesn’t work if I copy and paste.
Did you try copy/pasting my link into a bookmark? That’s what I was recommending, sorry if that wasn’t clear. When I copy/paste anything starting with javascript: directly into the URL bar, the javascript: part gets dropped.
Here are two bookmarklets that have really helped my article-reading workflow. I named the bookmark for #1 “Clean” and #2 “Squirt”:
#1 is a nice, simple frontend for the Readability API. Just enter the URL of a page with something you want to read on it, and it extracts the content without any sidebars, ads, or other junk and gives it to you in an easy-to-read format.
#2 is Squirt, a speed-reading application that takes the text of any webpage and displays it to you one word at an adjustable speed. The default is 450wpm I think, but after you make an adjustment, it remembers what speed you want for next time. If you need to read a part more carefully or go back because you missed something, that’s easy. Hit the spacebar to pause and it will show the context, then use the left and right arrows to move around. Hit the spacebar again to resume speed reading. Another awesome feature is that it tells you exactly how long it will take to finish if you don’t stop, so you can decide if it’s worth your time or not.
The two work really well together, as squirt alone will sometimes grab text you don’t want. What I do is “Clean” a page by clicking on the bookmarklet, and then sometimes hit “Squirt” to speed read it.
Try it out and let me know what you think!
Which speed are you using at the moment and how long did it take you to come to that speed?
I started at 350 and that’s still what I use most of the time. For light, non-technical articles, I can do 450, but it’s a bit uncomfortable to focus that hard and I do miss things occasionally. I can usually tell if it was important or not though, so I know if I need to go pause and rewind. After playing with speedreeding off and on for a few years, I’ve come to the conclusion that it’s definitely possible to read faster than I normally do with equal comprehension, but that there really is a limit and the claims you see from speedreading courses are hyperbolic. The thing I like about Squirt is that it eliminates the need to use a pacer.
1 didn’t work for me.
For example, trying it on tvtropes.org got me http://tvtropes.org/pmwiki/pmwiki.php/%3Chttp://justread.mpgarate.com/read?url=%3Ehttp%3A//tvtropes.org/pmwiki/pmwiki.php/Main/HomePage
Looks like this is a bug with the way LW parses markdown. You need to remove the angle brackets just inside the quotes.
That fixed it. Thanks.
Hmm… Yeah, that’s not right. Maybe there was a problem when I pasted it? Here it is again.
Only other thing I can think of is you may have a browser extension interfering.
It still doesn’t work. It could be an extension, but I was guessing it was just the browser. I’m using Chrome. javascript:alert(“test”) seems to work if I type it direction or use a bookmark. It doesn’t work if I copy and paste.
Did you try copy/pasting my link into a bookmark? That’s what I was recommending, sorry if that wasn’t clear. When I copy/paste anything starting with javascript: directly into the URL bar, the javascript: part gets dropped.