4 ms·
Sourcegraph CEO here. Excited to show this to HN folks. Huge credit to Farhan Attamimi and John Rothfels on our team for creating it. Happy to answer any quest
by sqs 10y ago
Sourcegraph CEO here. Excited to show this to HN folks. Huge credit to Farhan Attamimi and John Rothfels on our team for creating it.
Happy to answer any questions here about how we built the Sourcegraph Chrome extension, future plans, issues, etc.
We will be adding more languages soon (beyond Go and Java). Email me at sqs@sourcegraph.com if you want to beta test JavaScript, Python, Objective-C, C/C++, Ruby, or Scala. Or just install the extension now and it'll be automatically updated with more languages in the future.
You can install it directly from https://chrome.google.com/webstore/detail/sourcegraph-browser-exten/dgjhfomjieaadpoljlnidmbgkdffpack https://chrome.google.com/webstore/detail/sourcegraph-browse....
- zodvik 10y agoWhat information does the extension send back to your servers?
- sqs 10y agoIt doesn't send code from the GitHub page to Sourcegraph; it actually only works if the repo is already mirrored on Sourcegraph (which obviously requires your explicit permission for private repos). It will send the name of the repo (e.g., "google/golang" or "JodaOrg/joda-time"), so that Sourcegraph can see whether that repo is mirrored. If the names of your repositories alone are sensitive data and you don't want to trust us, then you shouldn't use the extension. (Repo names can leak to third parties via the HTTP referer header, even in an alternate universe where this extension never existed.) The unpacked code is available at https://sourcegraph.com/sourcegraph/sourcegraph/-/tree/client/browser-ext https://sourcegraph.com/sourcegraph/sourcegraph/-/tree/clien... if you want to poke around. And you can always check the Chrome network inspector to see the exact data structures.
- zodvik 10y agoThanks! That clears it up.