<story><title>Show HN: GitHub Trending Repos</title><url>https://github.com/vitalets/github-trending-repos</url></story><parent_chain></parent_chain><comment><author>simonw</author><text>Using GitHub issues to power notifications in this way is absolutely inspired!&lt;p&gt;You get single-sign-in for anyone with a GitHub account.&lt;p&gt;You get both email AND push-based notifications without needing to run ANY of the infrastructure yourself.&lt;p&gt;Your scrapers get to run in their own time and publish via a very well-documented and easy to use API.&lt;p&gt;I&amp;#x27;m totally sticking this idea in my back-pocket. It&amp;#x27;s brilliant.</text></comment>
<story><title>Show HN: GitHub Trending Repos</title><url>https://github.com/vitalets/github-trending-repos</url></story><parent_chain></parent_chain><comment><author>trextrex</author><text>Couldn&amp;#x27;t this be done a lot more simply with a mailing list or RSS feed? Using GitHub issues seems a bit convoluted, although I&amp;#x27;m guessing it&amp;#x27;s probably because it&amp;#x27;s easier to set up and free to use. It seems like somebody should build a service which makes use cases like this 0 config.</text></comment>