31–36 of 36 posts
what is different about this than the original arc90 readability algorithm with an URL field added to kick off the processing?
This project directly uses the Readability api. I created this as a more simple interface than Readability offers, primarily for my own personal use as a bookmarklet.
http://justread.mpgarate.com/read?url=news.ycombinator.com%2... see also readability. but what I really want is a low bandwidth version of a webpage, to conserve my mobile data plan.
I'm dating myself, but when I first learned about HTML, the idea was that text would be organized so the browser could make it more readable for you, based on your needs. For instance, a deaf person could use a text-to-speech browser, and perhaps the heading tags would help them navigate the document.
Today's web page simply treat the screen as a graphical canvas.
In those old days, I also learned that having a crummy obsolete browser for my crummy obsolete computer actually sped up browsing because my browser was simply incapable of downloading the stuff that ate bandwidth.
Knowing my luck I'd get used to reading with this, then you'd disappear off the internet forever. It'd be nice to be able to self-host.
By the way, does anybody here know of an algorithm (and/or already implemented open-source library/app) that copes well with auto-extracting content from forum-like websites? (i.e. phpBB, StackOverflow, HN, reddit, ...)
You can then easily adapt it for your requirements.
http://justread.mpgarate.com/read?url=news.ycombinator.com%2... see also readability. but what I really want is a low bandwidth version of a webpage, to conserve my mobile data plan.
Don't spose you're putting the source up anywhere? Knowing my luck I'd get used to reading with this, then you'd disappear off the internet forever. It'd be nice to be able to self-host.
justread is written with golang!