Show HN: GitHub News, using a peak detection algorithm to detect trending repos
1–10 of 32 posts
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#2I'm using a peak detection algorithm to find which repos are spiking in traffic and rank the uptrend based on a normalized growth curve. This filters out all the well established repos and actually uncovers new trends and launches. Hope you guys find it useful!
Some notable features, there's also a better interface to search topics on github as well as a curated topics section: http://www.gitlogs.com/resource-guides http://www.gitlogs.com/search
Appreciate any feedback,
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#3Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#4Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#5If this allowed you to filter by language it would be infinitely more interesting.
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#6Good name. Personally I would like to receive a weekly digest for one or two specific languages.
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#7This way you can gain: 1. detect spikes in less popular streams, and decide via the merging function how to compare them to spikes in popular streams. 2. personalization, where each user can potentially get its own stream combining the categories she's interested in.
[1] e.g., by language as also suggested elsewhere, by "category" if you can come up with some definition, potentially by source (e.g. big company) as well.
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#8Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#9Cool concept, would love to see graphs over weekly/monthly timespans or something like that.
Re: Show HN: GitHub News, using a peak detection algorithm to detect trending repos
#10You have reached the Github anonymous user limit, please login with your Github account to continue.
Oof. I was just scrolling down the front page.
---
Edit: After I signed in, I got a bit lower, then got the same message again (telling me to sign in)!
Make / break suggestion: File the stats on a local server. Don't expect the user to query Github or you're going to drop fans fast.