4 ms·

I like the concept, but I feel that your algorithm for generating an initial summary needs a lot of work. For example, I was experimenting with the API: The in

I like the concept, but I feel that your algorithm for generating an initial summary needs a lot of work. For example, I was experimenting with the API: The input page: http://bookflavor.com/dukan-diet-2-steps-lose-weight-2-steps-forever-pierre-dukan-0307887960 http://bookflavor.com/dukan-diet-2-steps-lose-weight-2-steps... The API results: http://gistpoint.com/get?u=http://bookflavor.com/dukan-diet-2-steps-lose-weight-2-steps-forever-pierre-dukan-0307887960 http://gistpoint.com/get?u=http://bookflavor.com/dukan-diet-... Rather than choosing a snippet of the main text, it chose a few words from one of the menu items... If you can fine tune the algorithmic generation of snippets in the API this could be very useful. Keep up the good work!

ultrasaurus 15y ago
Passing it through readability.com first improves it dramatically: http://gistpoint.com/get?u=https://www.readability.com/articles/ocp6wcn9 http://gistpoint.com/get?u=https://www.readability.com/artic... It would be nice if the API would take a parameter for the approximate number of words to return, so a 100 word vs a 500 word summary.
- NathanKP 15y ago
  Good idea... I'll check Readability's API's then, perhaps using a combination of both API's will generate good snippets of the pages on my site.
quan 15y ago
thanks for the kind words, it's probably a problem with the fulltext extraction. If the fulltext is extracted correctly, the summary extraction should be good. Btw, I use the ruby-readability gem for the fulltext extraction.