1. You can currently do a code search with -project: to exclude a specific project; this can be repeated multiple times to exclude a set of projects.

We’re adding support for -site: as well, to do more general exclusion.

2. Having page numbers displayed as part of the search result is on the to-do list, hopefully soon.

Thanks,

– Ken

I dunno. I could spend time and energy trying to publicly shame the people who wrote jhomenet into acknowledging their use of my code. But, quite honestly, this blog is as far as it’ll go. There’s not enough ROI there for me to take it further.

The implication is that, if we assume other developers behave similarly, Krugle is unlikely to be a significant deterrent to someone who casually copies code into a codetree.

On the other hand, I like what you’ve built. Thanks for making it available. And now that I’ve figured out to search on my name, I’m noticing *lots* of reuse of my code.

A feature suggestion: can I say “everything but [these projects]” ? If I’m looking to see for unauthorized use of my code, I’d like to not get hits from things I know about.

Also: index numbers to hop around in search results (e.g. directly go to page 3) would be nice.

Bill

I think there will be many more similar posts to yours, once it’s easier for people to search for code replication across all public source.

What I’m hoping is that open source developers will use this as motiviation to do a better job of providing attribution and complying with licenses. That’s the positive outcome, versus just trying harder to mask the fact that a chunk of code was copied from someplace else.

Should be interesting to see what happens - thanks for giving it a try. And we plan to be around for longer than just a little while