HN always likes the faster is better, I am a genius absorbing this much information quicker than you. Its been proven over and over that comprehension is way more important than speed of consumption. You guys fool yourselves into believing you can comprehend while reading at breakneck speeds, its way more fun & time saving to be able to imagine, driftaway in thought and understand what you are reading.
Spritz is supposed to improve comprehension too. That's how it was pitched in the original article I read.
Squirt.io – Readability Meets Spritz Speed Reading
121–130 of 213 posts
Re: Squirt.io – Readability Meets Spritz Speed Reading
#122HN always likes the faster is better, I am a genius absorbing this much information quicker than you. Its been proven over and over that comprehension is way more important than speed of consumption. You guys fool yourselves into believing you can comprehend while reading at breakneck speeds, its way more fun & time saving to be able to imagine, driftaway in thought and understand what you are reading.
Re: Squirt.io – Readability Meets Spritz Speed Reading
#123What I noticed using this to read a couple Ars Technica articles was it worked really well for short words. But, if a longer complicated word appeared, at say 600 wpm, I would miss it. It seems like an adaptive algorithm based on word length would improve the speed even more allowing it to go faster on short common words and slow down on longer unusual words. Also, there is bug that sometimes causes two words to appe…
That's what I did with Spree [1] (also posted below). Just a simple word.length*8 seemed to have quite a nice effect on readability. 1. https://chrome.google.com/webstore/detail/spree/aehoaolhojlm...
Re: Squirt.io – Readability Meets Spritz Speed Reading
#124Re: Squirt.io – Readability Meets Spritz Speed Reading
#125I'm pretty sure this is just a big middle finger to Spritz. In the most hilarious way possible. Or am I misinterpreting the acknowledgments? ;)
Uhm, what's the difference between Spritz an Squirt.io? I've looked at both demos and I can't see much difference in the concept. Though the Spritz website is more ... ehm ... bullshit bingo compliant it seems. Am I assuming right that the joke lies in Spritz being a VC funded startup and squirt.io just a weekend hack?
Re: Squirt.io – Readability Meets Spritz Speed Reading
#126I'll also shamelessly plug my open source implementation, OpenSpritz, which now has a healthy and vibrant community! https://github.com/Miserlou/OpenSpritz as well as the Android / Google Glass companion: https://github.com/OnlyInAmerica/OpenSpritz-Android
Re: Squirt.io – Readability Meets Spritz Speed Reading
#127I'd really like to see this model with an adaptive speed. Same speed for all the words isn't always the best. Maybe using an n-gram model to predict how probable the next word is, could pass high probability phrases at a faster rate, while slowing down for "harder" words
There's a good Google Books dataset for doing exactly that, and you can doing something in Hive to get you the lowest-entropy n-grams (with something like https://github.com/lsb/text-entropy/blob/master/passphrase-s... ), and then you can the low-entropy n-grams into a Bloom filter (like http://www.leebutterman.com/passphrase-safety/how-it-works.h... ) and your enormous corpus gets fitted into a few dozen megs of mem…
What's fascinating is that in the entropy/information-theoretic sense, instead of using wpm, one could aim for "constant" information rate of reading (as in bits/token). That's really cool as a concept. I don't know if it would work, obviously.
I'd definitely be up to for hacking this up, but currently a bit too busy. Will ping you at some point though!
Re: Squirt.io – Readability Meets Spritz Speed Reading
#128Re: Squirt.io – Readability Meets Spritz Speed Reading
#129small increases in wpm can be easily achieved by beeline[1] it without the drawbacks rsvp has. [1]> http://www.beelinereader.com/install