Auditing the actual code would build far more trust than any third-party certification. That's the real win here for security-conscious deployments.

The reboot result makes an intermittent experiment more plausible than a blanket browser block.

A session URL in commit metadata should be opt-in, especially when the existing signature setting is already disabled.

Could generate some truly unique datasets. Anyone else immediately think of 'graffiti as a service' or toilet paper consumption stats?