it's on the list of things to do, however one of the challenges is that those sites are always changing or updating their templates. So it's nice to have the most up to date links to hit against.
Goose also pulls all the images down as well to inspect them to try and find the most likely main image for the page.
It will probably be split into an online/offline test. If that sounds like something someone wants to help hack on, the more the merrier!
This is one of the reasons Readability links you back to the original article when you share document inside the service. It keeps a small overlay at the top which you can use to make the page more readable again.
Slightly off topic:
I've been playing around with an idea for a service that would be able to share content this way - would make reading a lot more fun again.
I recently developed a web service that performs these sorts of operations called Linguini (http://linguini.me). The service hasn't been officially launched but it's in beta and usable. It can extract html/blog text through JSON web service calls and can tag names/companies/locations in that text.
One advantage of Goose, (the linked project), is that it tries to also extract the best image from the webpage. None of the competitors do this. I am not sure how good Goose's text extraction is, compared to boilerpipe or diffbot.
A new tool just popped on my radar called justext: http://code.google.com/p/justext/ It was written by the BiWeC web-as-corpus people, who crawl the web and expose it through the SketchEngine for NLP research.
Super nice, I was playing around with the idea of running an article extractor and running the output through festival (with a little clean up the output is surprisingly good, and certainly a lot better than it used to be a few years ago) so that I could hear blog post while I was working.
Is anyone else interested in seeing something like this used with zap reader? Zap reader takes articles and renders them a word at a time in the same spot on the screen. You can adjust the words per minute, I can understand stuff in the 300 to 500 wpm range. I think their ui is not very good and it seems to just read through a page, including navigation and header/footer.
14 comments
[ 3.4 ms ] story [ 45.5 ms ] threadGoose also pulls all the images down as well to inspect them to try and find the most likely main image for the page.
It will probably be split into an online/offline test. If that sounds like something someone wants to help hack on, the more the merrier!
Are there any rules I presume there must be?
Instapaper arguably is republishing, though the copies are private to each user. I suspect they could still be in trouble if sued, though.
Slightly off topic: I've been playing around with an idea for a service that would be able to share content this way - would make reading a lot more fun again.
I recently developed a web service that performs these sorts of operations called Linguini (http://linguini.me). The service hasn't been officially launched but it's in beta and usable. It can extract html/blog text through JSON web service calls and can tag names/companies/locations in that text.
There is some deeper discussion of text extraction tools on Tomaz Kovacic's blog: http://tomazkovacic.com/blog/56/list-of-resources-article-te...
One advantage of Goose, (the linked project), is that it tries to also extract the best image from the webpage. None of the competitors do this. I am not sure how good Goose's text extraction is, compared to boilerpipe or diffbot.
A new tool just popped on my radar called justext: http://code.google.com/p/justext/ It was written by the BiWeC web-as-corpus people, who crawl the web and expose it through the SketchEngine for NLP research.