News for hackers. Stuff that matters.
Re:Survey of popular Node.js packages reveals credential leaks by ddbennett on Sunday December 06, 2015 @06:08PM (#10687120)
No too much load, really. We (Bitbucket) already have pre-receive hooks for a handful of other things. The trick would be defining the rules properly to have a reasonably low false negative rate while avoiding work inhibiting false positives (or allow for a mechanism to override it with, say, a force push).

Of course, 93% of our repositories are private so this feature may not be exceedingly useful to our customers vs other things we could be spending our time on.

Edit: I shouldn't have said not useful, rather, comparatively there may be more value in us pursuing other work first. E.g., provide a mechanism for 3rd party pre-receive hooks via our add-on system.

Re:Survey of popular Node.js packages reveals credential leaks by ebiester on Sunday December 06, 2015 @06:14PM (#10687141)
It is still useful. Even if the repository is private, it can be shared with people who shouldn't have that private key.
Re:Survey of popular Node.js packages reveals credential leaks by voltagex_ on Sunday December 06, 2015 @07:21PM (#10687390)
Interesting to see that percentage of repos is private.

Is BitBucket separate from Atlassian? Are you hiring? ;)

Re:Survey of popular Node.js packages reveals credential leaks by ddbennett on Sunday December 06, 2015 @07:57PM (#10687485)
We're very focused on professional teams working on private projects -- but you can't see that because they're all private. Bitbucket is sort of like an iceberg: 1. you can only see a small percentage of the of the total mass; 2. it is blue.

Yes, we're part of Atlassian and we're hiring in San Francisco.

Re:Survey of popular Node.js packages reveals credential leaks by voltagex_ on Monday December 07, 2015 @01:21AM (#10688181)
Can't afford to move to SFO unfortunately - any plans to expand remote work?