Rick Viscomi

⚠️ @Suzzicks @dwsmart @hemanth it looks like this chapter still doesn't have a lead or an analyst and the [outline](https://docs.google.com/document/d/1CbfJi1AvEJp3N8h_oL6aUJfSroQm0WbzGFIWcRz1dQA/edit?usp=sharing) hasn't been started yet. As @foxdavidj noted, we might have...

Thank you @dwsmart! If needed, would you be able to take on the lead/author role?

No worries, thank you for following up @dwsmart!

Thanks for the update @Suzzicks! Excited to have you back. 🎉 @Suzzicks @dwsmart @hemanth @foxdavidj make sure you all have access to the [planning doc](https://docs.google.com/document/d/1CbfJi1AvEJp3N8h_oL6aUJfSroQm0WbzGFIWcRz1dQA/edit?usp=sharing) and start adding your ideas...

@CodeMartian yes but I'll do you one better. I've just sent you an invite to join the HTTP Archive org, after you accept you'll have edit access to the repo...

@Suzzicks @polyglotyeoja looks like both of you also have outstanding invitations. I've just resent it and you should get an email asking you to approve. Or you can visit https://github.com/HTTPArchive...

Call for translators posted to Twitter here: https://twitter.com/HTTPArchive/status/1288514460945199105

Done. Steps to reproduce for next time: For `almanac.breaches`: - Download `breaches.json` - Create a new table `almanac.breaches_2022` via upload, with autodetected schema - Append the output of this query...

⚠️ @Suzzicks @webmaxru @Schweinepriester @tropicadri @siwinlo it looks like this chapter still doesn't have a lead or an analyst and the [outline](https://docs.google.com/document/d/14riy6CwQslsBtR0iuhMe-V28AycTsTRilq2wn4yzRJU/edit?usp=sharing) hasn't been started yet. We might have to...

Thanks for your interest in contributing to the HTTP chapter this year @paivaspol @tunetheweb @rmarx! We still don't have an author/lead for this chapter, which puts us behind on Milestone...