Show HN: GitHub News, using a peak detection algorithm to detect trending repos
gitlogs.com
gitlogs.com
I'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,
Ideally you (well, really I :-P) also want star/follow activity from people you follow bundled in any update that's also reporting the projects discovered by your peak detection algorithm over that same period of time. There'd likely be some overlap in the report but you could indicate that in your report. This also gives you more incentive to login with GitHub which is a little lacking right now.
Anyway, thanks for doing this and great job :-)
You 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.
Otherwise, it looks really good, and the algorithm results are refreshing.
This 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.
I'm interested in the peak detection algorithm.
However, that said I do plan to improve discoverability even more with traffic data since now I can atleast measure views on gitlogs.
Where git = github
Looks great though! Already found something sweet.
Another feature request, can you add an up/down trend indicator?
Can I ask which peak detection algorithm you used?
The algorithm basically looks at the moving average, the new watchers gained and the number of total watchers. It'll calculate the the rate of change in new watchers and compare that against what it expects given the lifecycle of where the repo is at. So a brand new repo adding 150 stars per day will beat out an established repo that adds 250 stars per day.