Re:Show HN: GitHub News, using a peak detection algorithm to...
by ecesena on Thursday March 10, 2016 @04:11PM
(#11262354)
I can recommend you to "split" your stream of repos in multiple streams [1], and then create a function to merge multiple streams into a single one.
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.
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.