Re:Show HN: What parts of your code are not original
by nunobrito on Saturday February 06, 2016 @09:17AM
(#11047800)
Worse thing is sometimes getting 30 different projects with the same snippet of code but the code was written by neither, it was simply copied from Stackoverflow and then applied by each developer on their code.
Have you had a chance of trying out the report?
If you are scanning open source, there is a trick to ignore matches from the repository where it comes from.
Just create a file called "ignore.txt" inside the samples folder and on that file include the keywords that blacklist positive matches. For example, if scanning the "Adblock Plus" code then add as keyword "adblockplus" on the ignore.txt file and no matches from repositories containing "adblockplus" on their URL will be listed.
Works good for discovering which parts of an already open source project are not really original.
Re:Show HN: What parts of your code are not original
by sdevlin on Saturday February 06, 2016 @11:50AM
(#11048441)
Why did you need to write an implementation of Mersenne Twister?
Re:Show HN: What parts of your code are not original
by bpicolo on Saturday February 06, 2016 @11:51AM
(#11048450)
"No open source code."
Re:Show HN: What parts of your code are not original
by Kluny on Saturday February 06, 2016 @03:16PM
(#11049597)
Yeah, we got that. But why did you need a Mersenne Twister?
Re:Show HN: What parts of your code are not original
by tbabb on Saturday February 06, 2016 @07:10PM
(#11050760)
My understanding is that Mersenne Twister is kind of a gold standard for non-cryptographic PRNGs. Linear congruential generators are known to be rather poor, and only ideal where speed is critical and the quality doesn't matter.
The reference implementation of the Mersenne Twister was once GPL, although it wasn't anymore at that time. Still, there are only so many ways you can implement a Mersenne Twister. So my implementation got flagged.