Not entirely true. As long as you hold the copyright to all of the code (there are no contributions from other people), you can change the license however you like. The important thing is that this only affects commits after the licence is changed. All earlier versions are permanently available under the license they were released with.
Step 3 is where the issue occurs. The last party to submit their value has control over the output. Any complex calculations can easily be passed off as network lag. One solution I can think of is to pass the values round in a circle, one by one. This would require each party to share their value before they have seen all other values. At the end each party would share their calculated values to verify they match. Probably other solutions as well.
I would usually describe it as grey. There have been a few times where a sunset or the moon have provided some contrast, causing the greenness to become slightly noticeable. Last night was the first time I've seen such an obvious pink.
Sadly it doesn't get dark enough here at this time of year, so my family down south had a better view.
It's the green parts that look white / grey. I believe it's more of an illusions - if you have something to contrast it with, such as the moon, you can start to see a slight green tint. The pink I saw last night was very noticeable though.
It looks like it's the addon's fault, and has already been fixed in the github version. It's also been abandoned, so it's probably not worth keeping around anyway.
It seems to be caused by the FediAct addon, which doesn't make any sense. Disabling the addon fixes the page without needing a reload, so it must be a CSS issue rather than an exception. Edit: it seems the addon is overriding the fadeIn keyframe, but it looks fixed in the github version.
"Curated by"...
seems so.