my bad, was there some rules for this? I wrote a detection algorithm to find which are the top trending repos that were not featured on HN and I sometimes pick out a good one to feature. I thought it was be nice to spread the word on some of these under appreciated projects.
It _would_ be nice to spread the word on these under appreciated projects, but not to lump your own promotion in with it. This is basically the same thing as blog spam, which is disallowed under HN rules. [1]
>Please submit the original source. If a post reports on something found on another site, submit the latter.
You should just submit the link to the Github repository you want to share, not to your own site. You appear to do this all the time - stop.
Just found this trending on Gitlogs but it was never posted on HN before. Actually noticing a lot of Chinese Repos trending on Github lately. Most likely launched on their on their own version of hackernews ;)
I think someone else mentioned this as well, but unfortunately Github ties the "staring a repo" to the write permission. I think I can try to separate it out so it can ask for that scope when a user wants to use that feature.
Thanks for the response! Github is definitely a little unclear on the permissions side of things. Might help clear things up if you mention what you are doing with the permissions somewhere.
That's definitely something on my mind originally. But since I can't get traffic data from Github, the best thing I can do is to filter out the highly established repos and weigh new repos higher in the rankings. You can see that even with just 150+ stars gained for a brand new repo this system will show it at the top top of the rank despite other popular repos that might have gotten 700+ gains on that day.
However, that said I do plan to improve discoverability even more with traffic data since now I can atleast measure views on gitlogs.
Hey thanks for the tip, it took me a while to find it but apparently react-router 1.x had an issue https://github.com/reactjs/react-router/issues/1661 and I had to upgrade to react-router 2.x I'll push out a fix soon
Right now if a repo is trending down (from the moving average) it will have a negative score and won't be showed at all.
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.
Hi DC2, actually I do cache some of the results, first 10 days and top 50 repos per day. I think I didn't expect people to scroll as far as they did. I'll up that cache later
Thanks, I actually did build something like that. My original inspiration was Google Trends (thus the UI) but the data wasn't very useful, traffic on github is very spiky, even on a log graph it didn't look good.
