The Github Follower Problem • Hacker News Board

Re: The Github Follower Problem

#21

Post by technoweenie » Thu, Jun 02, 2011, 12:08 AM UTC

dimmuborgir wrote: post #18

Lot's of good suggestions for GitHub coming up lately through various blogs. I think it's high time GitHub put a public Brainstorm/Suggestions interface with possibility of voting the entries. There's a GitHub profile on GetSatisfaction but there's no activity there.

No need. We see a ton of stuff on Twitter, HN, Convore, etc. Our own list of major project priority aligns pretty well with a lot of the feedback we receive.

Re: The Github Follower Problem

#22

Post by nitrogen » Thu, Jun 02, 2011, 1:18 AM UTC

icco wrote: post #7

icco wrote: post #2

I totally agree. Although my issue is more that I watch a ton of projects. It'd be nice to filter our dashboards, maybe group projects or people we follow.

Interesting, my post gets down voted and then someone later makes the same point and doesn't get down voted... hn, you confuse me.

Occasionally, a downvote can be caused by someone accidentally pressing the downvote button on their phone or tablet when trying to scroll or upvote.

Re: The Github Follower Problem

#23

Post by sayemm » Thu, Jun 02, 2011, 1:30 AM UTC

I really like what http://www.githits.me is doing. I think it's a great way to improve your programming skills too by looking at great code written by some of the top github users.

Re: The Github Follower Problem

#24

Post by zalew » Thu, Jun 02, 2011, 1:59 AM UTC

BitBucket has the same problem with following projects. When I follow a project, I get messages about every person who starts/stops following it, so my main feed is mostly dozens of 'John Doe began following SomePopularProject'

Re: The Github Follower Problem

#25

Post by eLod » Fri, Jun 03, 2011, 6:16 PM UTC

I wanted to give this a shot. I first thought making a chrome/safari/etc. extension/plugin/etc. to filter your feed on the github dashboard (it may be a viable option), but i settled on making api calls (and using public data only).

I pushed it to http://gfnf.heroku.com (source is at https://github.com/eLod/gfnf). The interface obviously lacks some detail, but still usable i think. You can create filters and set what to include based on languages, users and repositories. Without requirements those events are selected that matches any of the conditions (e.g. OR). With requiring user(s) for example only those events get selected whose actor is in the filter.

Of course backed with the right data this should be much easier.