3 ms·

> I am the Sourcegraph CEO, and we haven't changed anything about our public code search at https://sourcegraph.com/search https://sourcegraph.com/search. But

> I am the Sourcegraph CEO, and we haven't changed anything about our public code search at https://sourcegraph.com/search https://sourcegraph.com/search. But in this other comment (https://news.ycombinator.com/item?id=41298516 https://news.ycombinator.com/item?id=41298516), you said you have changed public search in two significant ways: > We did cull lots of non-GitHub repositories and repositories with less star. Removing low-star repos (and non-GitHub high-star repos) affects users who are looking for obscure or hard-to-find information that's not found anywhere in "popular" repos. I think most of my searches on GitHub (or via Google) are for things in repos with zero stars. > If you have repositories you want us to add that are below the star threshold [..] How would I go about finding which repos to request, if my objective is to search the "long tail" for information? That seems like I would need an automated search engine first, to discover the repos :-) If I found the repo containing specific, obscure or hard-to-find information I was looking for, what would I gain from writing to SourceGraph asking to add that one repo? By the time I've found the right repo, I've probably found the information I'm going to get from it. Future searches will likely need a different repo, one I don't know about yet. Perhaps that's the nature of long tail searches.

mdaniel 2y ago
I see this same problem in the search engine space: upstarts need both long-tail sites indexed, and need the ratelimit/compute to actually follow those long tail sites I wish Presearch <https://nodes.presearch.com/ https://nodes.presearch.com/> all the best because that's the world I want to live in, although their current implementation is why I'm just clapping for them and not running nodes: > This software is currently not open source and you are relying on our assurances that nothing malicious is happening underneath the hood. Anyway, I mention this because if (e.g.) Sourcegraph supported federated queries, you could actually run a source code indexer to help offset some of the compute, ratelimit, and storage that is presumably jamming up their board members

mdaniel 2y ago

I see this same problem in the search engine space: upstarts need both long-tail sites indexed, and need the ratelimit/compute to actually follow those long tail sites I wish Presearch <https://nodes.presearch.com/ https://nodes.presearch.com/> all the best because that's the world I want to live in, although their current implementation is why I'm just clapping for them and not running nodes: > This software is currently not open source and you are relying on our assurances that nothing malicious is happening underneath the hood. Anyway, I mention this because if (e.g.) Sourcegraph supported federated queries, you could actually run a source code indexer to help offset some of the compute, ratelimit, and storage that is presumably jamming up their board members