Either I'm not seeing a lot of detail in the linked article, or it's just not there. This one has more info:
BBC News - FBI targets cyber security scammers
Facebook, which called the claim “an egregious fraud,” asked a federal judge in Buffalo today for an order requiring Ceglia, 37, to provide expedited fact-finding, or discovery, in the case."
Link to Original Source
How many commits do you suppose Linus Torvalds has made over the years, between the original BitKeeper revision control and the more recent Git?
Point / counterpoint. However, I still like the fact that Firefox+NoScript doesn't download "pages full of crap" *at all*. Give me Chrome+NoScript and I'd be one happy camper.
I just checked Chrome out for the first time, and yes it does render pages quickly. But it's no faster (to my naked eye, at least) than Firefox with the NoScript extension running. And since Firefox+NoScript is also blocking scripts, Flash applets, etc. from running, it seems to me that it would be safer than Chrome anyway. YMMV, but I think I'll stick with my Firefox a bit longer.
Which just brings us right back to my second point - how do you *prove* it without access to the source?
Are we to believe then that, unlike every single piece of virus-scanning software ever, this binary scanning utility will never encounter a false positive? What happens when it shows some product as containing OSS, but it doesn't?
And with that in mind, even if you *do* identify a product as containing OSS, how do you prove it without access to the source code? The company could simply claim it was a false positive (regardless of whether or not that happened to be true), and you would be left with the burden of proving the tool wasn't flawed.
Of course, there are also the false negatives...
It's gone now.
It's not completely gone - it's just been relocated here.