I found this really useful for my articles.
The short snippets would work well as tweets, a tweet bot for article summaries would be cool!
Show HN: TLDR This – Auto summarize any article or webpage in a click
61–70 of 117 posts
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#62I found this really useful for my articles. The short snippets would work well as tweets, a tweet bot for article summaries would be cool!
We are glad that you liked it.
That's a very good suggestion. By tweet bot, you mean when someone tweets an article link to the bot, it would respond back with the summary of that article, right?
Thank you very much for taking the time to use the app and provide your feedback.
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#63I tried in on the HN guidelines and then on the output. So the summary of the summary is: >What to Submit On-Topic: Anything that good hackers would find interesting. which isn't bad really.
We are glad that you liked it.
Yes, if the webpage doesn't have that much content then it would return the most relevant line.
Thank you very much for taking the time to use the app and provide your feedback.
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#64I tried some of my articles and it's not really helpful. I even have a conclusion in my articles which is completely ignored. For example: https://www.karoly.io/amazon-lightsail-review-2018/
Thank you for your feedback. I am sorry to hear it didn't work on the article you tried. I have personally tried it on a number of articles and it seems to provide good results. Also, I have received feedback from a number of users who say that it worked for them. But yes there are some articles where it fails to give accurate results since the "article summarisation" technology is still in its development stage. We…
Can you provide any working examples?
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#65Earlier quoted context omitted.
Hi, - Yes, you are totally right. TextRank is an extractive method. - Ah right. But we aren't storing any information on our servers, just showing selected sentences to the user. - We select the top 5 sentences which have the highest relevancy to the article. I am not an expert in this field so not too sure if that's the best way. Just started with NLP a few days back and wanted to test it out by developing a small a…
> But we aren't storing any information on our servers, just showing selected sentences to the user. If this is in reference to the copyright comment, it doesn't matter -- you're still transmitting/redistributing the content, which is what matters. One way to get around this is to ship the code and have the code execute on the user's machine (i.e. what you're presumably doing with the extension).
Are you a lawyer?
Because there is plenty of precedent for this in available APIs and I've never heard of a case claiming this.
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#66Tried to use this service on the HN comments discussing it. It could not generate a summary of HN comments, now I need to read people's opinions the hard way.
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#67Any open-source libraries that do this, or anything similar to this?
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#68Any open-source libraries that do this, or anything similar to this?
Something like this is built in to macOS.
Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#69Re: Show HN: TLDR This – Auto summarize any article or webpage in a click
#70Earlier quoted context omitted.
> But we aren't storing any information on our servers, just showing selected sentences to the user. If this is in reference to the copyright comment, it doesn't matter -- you're still transmitting/redistributing the content, which is what matters. One way to get around this is to ship the code and have the code execute on the user's machine (i.e. what you're presumably doing with the extension).
Ah right, thank you for the detailed explanation. Currently, we are processing the text using a Python backend. In order to process it on the user's side, I guess we'll have to use Javascript. I will try to fix that in the next version. Thank you very much.
You don't need to move anything to the client side, what you're doing is covered under fair use doctrine.