add a blog post about the crypto/tls QUIC API

[marten-seemann]

TODOs until publication:

• [x] decide on a title
• [x] create a header image
• [x] get reviews from the libp2p team
• [x] email Filippo and give him a week or two to read / comment on this blog post
• [x] wait for the Go 1.21 release
• [x] wait for the go-libp2p release that includes quic-go v0.37

Intended publication date: ~mid August

I'm not 100% sure if we should include the last paragraph here. It doesn't contain a lot that we haven't said publicly (mostly on the QUIC GitHub issue), but do we want to surface it here?

[MarcoPolo]

Meta point, reviewing this as a GitHub PR is kind of painful. I would much prefer Notion, Google Docs, or even my own GossipPad. (Joking on the last one)

[marten-seemann]

Meta point, reviewing this as a GitHub PR is kind of painful. I would much prefer Notion, Google Docs, or even my own GossipPad. (Joking on the last one)

Noted. Will use Notion next time. cc @dhuseby @p-shahi as an example for a workflow that doesn't work well on GitHub.

[marten-seemann]

@p-shahi Should we move forward with this blog post? How do we get a header image created?

[p-shahi]

Should we move forward with this blog post? How do we get a header image created?

Yes let's move forward w/ this however, let's publish https://github.com/libp2p/blog/pull/101 this week and this post next week.

For the header image, I will ask Cake's Internet.dev team

[marten-seemann]

@p-shahi I've incorporated all feedback, except for one comment. Could you help me get this blog post out this week?

[github-actions[bot]]

Images automagically compressed by Calibre's image-actions ✨

Compression reduced images by 14%, saving 59.97 KB.

Filename	Before	After	Improvement	Visual comparison
src/assets/crypto_tls_header.png	428.36 KB	368.39 KB	-14.0%	View diff

63 images did not require optimisation.