MrCoffee7 3 days ago | prev | next |

This looks great! It had an unspecified error and did not generate a summary for "Grok3 Launch" article with over 1000 comments. Was that too much content for it to summarize?

Also, it looks like the "more" button at the bottom does not work. It takes me to another page that just looks like the regular user interface, without any Summarize button for each article.

spicy_ranch 3 days ago | root | parent |

Hey, thanks for checking it out!

Yeah, the webpage parser (https://github.com/mozilla/readability) doesn’t work well with social media sites like Twitter/X. It can summarize up to about 37,500 words, as long as the website is parsable.

I haven’t gotten around to adding pagination for the “More” pages yet. It currently only handles the home route/front page (https://news.ycombinator.com/). The cost of summaries does add up, especially on longer articles, so I wanted to limit expenses until I can find a way to keep it running while at least breaking even.

codenote 3 days ago | prev | next |

That's an interesting attempt! I think it's a good approach for prototyping using Gistr (https://www.getgistr.com/) Are you the developer of Gistr?

spicy_ranch 2 days ago | root | parent |

Yeah I created Gistr recently. I've just been playing with different ways to use the summarizing tech. I found this way easier than having to install the chrome extension I made and setting up an account.

codenote 2 days ago | root | parent |

Indeed, allowing users to try it through a demo product, rather than having them install a Chrome extension, makes it more accessible. This is insightful from a product marketing perspective. Thank you!

creativenolo 2 days ago | prev | next |

This is great.

For summaries my preference-where I have the option to set it-is for a bullet pointed list over a condensed paragraph. Easier to scan and typically does better at conveying the flow of the source too.