> the code of conduct simply killed any interest in contributing to it
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.
You could install the YouTube Plus browser extension and check "disable DASH playback" in the settings. Then if you start playing a video for a second or two and pause it, it will buffer the entire thing. The only downside is I think it reduces the maximum video quality for all videos to 720p.
>there's a file that's been modified that's unrelated to what I'm trying to commit
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?
In that case you'd want to use "git add -p" which allows you to pick only parts of a file to stage for a commit. It can be crucial in crafting a really solid project / commit history.
For even more complex cases you could use "git add -i"; however, that command can be tricky to work with and I find it's usually not to helpful to get that far into the weeds.
> Doesn't help us in any way for them to know our size.
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?
Maybe I'm taking your example a bit far, but it seems like you'd have to choose the hashing function carefully, correct?
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?
My favourite weird rule is the one where the bails are already broken and the stump needs to be removed from the ground to affect a run out or stumping. Nice example here from the 2011 world cup: https://www.youtube.com/watch?v=VXChmlp2g0Q
I used to use Brita filters for a long time but one day I looked closely and noticed tiny dark flakes in the water from what I assume was charcoal from the filter. Using new filters still left the flakes in the water so I just stopped using them altogether. Now I've been drinking straight tap water for ages. The taste was noticeably different at first but the tap water is perfectly safe where I live and it saves money.
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?
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).