13 karma · joined July 5, 2015
It looks like the only plausible way to undo the addition of the CoC is if enough contributors rescind the license to use their contribution. Given that the kernel is licensed under GPL v2, this seems to be a real possibility (GPL v3 prevents this scenario).
I've looked for replacements but haven't found anything that comes close. From what I can gather, much of the functionality that allowed these extensions is now removed from Firefox. I thought equivalent APIs were going to be made available so they could be ported but that didn't happen.
He wasn't fired. The university sent him two warning letters and then backed down from taking any action. He's still teaching psychology there.
What if those unrelated changes are in the same file as a bunch of related changes that you've already made? Do you undo all the changes you've made in that file apart from the random bug fix and then commit, or leave them intact resulting in that bug fix commit containing changes that are unrelated to the fix?
I'm curious as to what you tell a potential customer if they just ask you directly how big your company is? "It's mostly just me..."? Do you just hope that they don't ask that question?
To use your example, it must be 100% certain that a hash with 6 leading zeros is possible to generate with md5.
Also, I'm assuming you don't want clients spending too long on the problem, so it seems like you'd want to have a prediction of roughly how long it would take to compute the answer. Otherwise one client may get lucky after 10 iterations whist another may take 10 million. Are hashing functions predictable in that manner?
I still wonder if it's normal for those charcoal flakes to pass through the filter and into the drinking water, and do they pose any concern?