There are a number of videos. Mine was a kid that fell off their float out towards the middle of the top third of the screen and panicked. Refreshing and force refreshing hasn't gotten me a new one (or I'm just getting similar ones and don't notice) but there's ~30 on youtube.
I actually spotted that kid as the first possible point of trouble... but you have to wait until the "moments later" card to see him start doing something risky, and then like you said, even when he's tangled in the rope it won't let you click him.
For that guy I waited until he started actually showing IDR signs - no lateral movement, dipping up and down. Even though he's struggling in the rope he's still managing to move around using a bad freestyle.
I think at one point, if you have a shared password for a development DB, production DB, etc. then just keeping those on a pen and paper notebook is your best solution. Usually, for shared environments such as that (although I hope the team can set-up their own DB's for development!), the number of shared "secrets" is relatively small. Some secrets are best not stored electronically, especially if they can give away user data.
As I detailed in my other response to your original question, use an example config file that is version controlled. It includes all the necessary config keys, but example-only values. All team members would then be able to easily create a local config file based on the example that works. You can even document the config with comments in the example file so devs know what is needed and what it's for.
Apple continues to route IPv6 over the default route when connected to a VPN that is v4 only (at least for OpenVPN that is the case, I don't have any experience with others).
So that means if you have a v4 only VPN provider all IPv6 happily goes over the default route.
This is not surprising to me at all, traffic should follow the default route that is given. If you are privacy conscious you should already know how to disable IPv6... Honestly if it is a bug anywhere it is a bug in the VPN providers that they are not providing IPv6 services for their customers.
Thankfully with OpenVPN IPv6 setup is simple, and while it doesn't provide the privacy extensions like SLAAC (you can only get a single static IPv6 address on the other end of the tunnel), it does allow you to easily tunnel IPv6 traffic as well. I personally do this by pushing 2000::/3 across from my OpenVPN server.
On OS X 10.9 I don't have a way to disable IPv6 that I can find. In Network > Advanced > TCP/IP > Configure IPv6, there are only three choices: automatic, manual, link local. And as soon as I configure it with either manual or link local, the wifi connection changes from green to yellow and I no longer have even IPv4 Internet, although it remains identically configured as before. A while ago this popup had an Off option just like the Configure IPv4 menu does.