I know in previous years talks were published on YT, I assume this will still be the case this year. Normally the VOC team does miracles to publish incredibly quickly too, so you should be able to have the recorded talks online same-day.
69 karma · joined February 24, 2013
I know in previous years talks were published on YT, I assume this will still be the case this year. Normally the VOC team does miracles to publish incredibly quickly too, so you should be able to have the recorded talks online same-day.
We aim to interpret live 100% of the talks in German (* we do not always interpret things that aren't strictly speaking talks, like poetry readings or performance art, although we try to make these as accessible as we can). We also interpret various talks into other languages - we have a sizeable team working on French and Spanish interpretation, and depending on volunteer availability, we are keen to be target any spoken language. For this talk you are interested in, I'm very confident it will be interpreted into English.
You can find our work on media.ccc.de both on the streams and recorded talks. If you're attending live we have lower latency audio streams available on-site, check out c3lingo.org.
SREs may not have intricate knowledge of the code but they have an array of tools that can mitigate problems, and they're software engineers too, so they can debug this themselves if need be. Their focus however won't be on fixing the bug, it will be on stopping the bleeding. Typically they'll check if this is an issue introduced in a recent rollout and roll that back. In the case of Search they also have an array of tactical tools - someone mentioned that a specific website was causing this, they probably have a way to quickly and temporarily delist this specific result.
The focus will be on recovering ASAP, figuring out the details and the long-term fix later. That later can be during business hours on Monday.
And since the two processes already run as the same user, in the original model there's nothing the target can do that the debugger cannot also do, so this was not a privilege escalation path.
Earthenware pots are pretty specific but should be safe too.
However they also warned, and this applies just as much for paragliding, that competiting in this sport is significantly more dangerous than practicing as a hobby.
In your house, and maybe with trusted friends, keep the instructions sheet with logins and a reference to the relevant password number. "To access my email account, username is foo@gmail.com and use password #5122 from the password list".