David Tomaschik

Sorry I didn't get to this sooner. I can't seem to reproduce the issue on Chrome 80. Setting PROOF_OF_WORK_BITS to 12 results in hashing times of ~1-2s per time.

Is this only when the admins are creating/editing challenges, or does it also apply when a player fills in the answer to submit?

Also let's try to remove https://github.com/dima117/Chart.Scatter and move to the built-in scatter chart.

I will wait on the features here to make it to a release: https://github.com/chartjs/Chart.js/pull/6048

@iagox86 Will we have control of the music for BSidesSF this year?

Oh, that's unfortunate... looks like a refactoring and no longer shipping a config broke the Dockerfile. That was a contribution, I'll have to take a look at getting it working...

Seems to only occur when one or more categories has no visible challenges.

Bizarrely, you need to provide a `ssh_key` parameter to avoid this error. Check out [docs/examples/compute/gce/deploy_node.py](https://github.com/apache/libcloud/blob/trunk/docs/examples/compute/gce/deploy_node.py).

Other complexities: - What about after the game has started? - What happens to the newly-empty team, if applicable? - Is there metadata tied to a team that should be...

State would include: - URLs visited - Current workqueue - Configuration/settings Problems: - Output files incomplete? Probably need to store results in memory and serialize them too.