Filippo Valsorda
where else to find them
website:https://filippo.io
github:FiloSottile
bluesky:filippo.abyssdomain.expert
mastodon:@filippo@abyssdomain.expert
speakerdeck:filosottile
youtube:c/FilippoValsorda
twitch:filosottile
what they talk about
where they keep going back
- GopherCon2 editions2023–2025
all 6 in the filters
on a stage with
all 8 in the filters
who talks about the same things
- Mathilde Raynal4 talks
- Marcus Bointon10 talks
- Yolan Romailler3 talks
- Sam Burns4 talks
- Johnny Boursiquot9 talks
- Eleanor McHugh20 talks
| title | conference | date |
|---|---|---|
| The Go Cryptography State of the Union | GopherCon 2025 | 2025-08-26 |
Go 1.24 ships a ML-KEM + X25519 hybrid as the default key exchange in crypto/tls (also in SSH 0.38) so connections get post‑quantum protection without extra… | ||
| High-Assurance Go Cryptography | GopherCon 2023 | 2023-09-26 |
Go cryptography uses concrete artifacts: a Wycheproof JSON test corpus pulled via go mod, a test-only package that fetches and runs vectors in CI, and a… | ||
| "The Cryptography State of the Union" | GothamGo 2023 | 2023-06-09 |
Recent work lists concrete changes and results: a new crypto/ecdh byte-oriented API replaces the error-prone X/Y surface, TLS 1.0/1.1 are disabled by default… | ||
| Go Security | GopherCon Europe 2021 | 2021-05-26 |
Go security panel describes concrete work: a fuzzing in standard library rollout that becomes beta imminently to run fuzz targets like tests; a centralized… | ||
| Secure and reliable development with Go | Google I/O 2021 | 2021-05-18 |
Talk lists concrete changes: a first‑party vulnerability database plus a proposed Go audit that uses static analysis to report only relevant vulnerabilities… | ||
| Panel With the Go Team | GopherCon Europe - Iceland 2018 | 2018-06-01 |
Go team reports the user base nears 2 million and community size jumps 76% growth in 2017, with a survey of ~77,000 respondents reporting membership feeling… | ||
| Fighting latency: the CPU profiler is not your ally | Golang UK 2017 | 2017-08-16 |
CPU sampling misses wall‑clock latency caused by blocking so a service that looks CPU‑light still shows high request times; using runtime/trace +… | ||
| nothing matches | ||