Live data from Hacker News

Squirt.io – Readability Meets Spritz Speed Reading

squirt.io

51–60 of 213 posts

Re: Squirt.io – Readability Meets Spritz Speed Reading

#51
post #36

Earlier quoted context omitted.

Just tap the WPM and it'll give you options

I think the parent wants to be able to set a default instead of having to select it each time.

Edit dispatch('squirt.wpm', {value: 400, notForKeen: true});

Re: Squirt.io – Readability Meets Spritz Speed Reading

#52
post #50
post #45

What 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…

Slow down on long words would be very helpful, I just tried it with some german news text[1] at 600wpm: Worked great except for words that occured like Kinderbetreuungsmöglichkeiten US-Geheimdienstausschusses Bundestags-Innenausschuss Bundeswirtschaftsminister Bundesarbeitsministeriums [1] http://www.deutschlandfunk.de/nachrichten.353.de.html

Do you think german words like this would benefit from automatic syllable colorization -- slightly changing the shade of grey to make the syllable boundaries more obvious?

Re: Squirt.io – Readability Meets Spritz Speed Reading

#53
post #6

I'm pretty sure this is just a big middle finger to Spritz. In the most hilarious way possible. Or am I misinterpreting the acknowledgments? ;)

Yes. Squirt.io is engaging in the best kind of cultural warfare: Creating something valuable and sharing it with the world, undermining the profiteers who want to lock (other people's ideas) behind a paywall, who (attempt to) justify their claim with slick marketing brochures

Re: Squirt.io – Readability Meets Spritz Speed Reading

#54
post #13

This project may consider a name-change, as googling for this after it's gone from the HN homepage will trigger ... interesting results. Especially if you're trying to show this to a co-worker in the office. Note to my boss: I'm sorry!

Welcome to humanity. Every verb is a euphemism for a sexual act.

Re: Squirt.io – Readability Meets Spritz Speed Reading

#55
post #45

What 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

#58
post #52
post #50

Earlier quoted context omitted.

Slow down on long words would be very helpful, I just tried it with some german news text[1] at 600wpm: Worked great except for words that occured like Kinderbetreuungsmöglichkeiten US-Geheimdienstausschusses Bundestags-Innenausschuss Bundeswirtschaftsminister Bundesarbeitsministeriums [1] http://www.deutschlandfunk.de/nachrichten.353.de.html

Do you think german words like this would benefit from automatic syllable colorization -- slightly changing the shade of grey to make the syllable boundaries more obvious?

Not sure. E.g. 'Kinderbetreuungsmöglichkeiten' means 'child care possibilities', that's three words in one. I suppose the brain just needs more time to parse that. But just counting characters to determine delay won't cut it, since 'Mississippi' is quite quick to parse.

Re: Squirt.io – Readability Meets Spritz Speed Reading

#59

I feel like it ruins the cadence, in my head anything I read with this sounds like it's coming from a robot.

Yeah, I tried reading an excerpt from http://deadspin.com/when-englands-greatest-genius-took-over-... and not only did it sound odd in my head, I felt like I wasn't really reading any quicker than I normally would.

I think that perhaps a line-by-line reader would be appropriate, rather than word per word.

Post reply on HN