| 2 Jun 2025 |
 hexa | it supports 1.1 and 1.2 and all clients use 1.2 | 20:48:11 |
| hexa | at least the last time I checked, which was early januar | 20:48:29 |
| hexa | * at least the last time I checked, which was early january | 20:48:30 |
| hexa | interesting profiles would support h2/h3 with 0rtt, but the offered ones lack ipv6 | 20:49:02 |
| hexa | see https://manage.fastly.com/network/subscriptions | 20:50:51 |
 Arian | having to choose between TLS1.3 and Ipv6 is wild | 20:51:18 |
| hexa | hm, no … that's not it | 20:51:20 |
| hexa | https://manage.fastly.com/network/tls-configurations | 20:51:31 |
| Arian | Okay that’s one mystery down. But why is half our traffic HTTP 1.1? | 20:51:39 |
| hexa | that is surprising to me | 20:52:08 |
| Arian | https://manage.fastly.com/observability/dashboard/system/overview/details/Tb10gX/7mNUQGZO6YxAd2jpokgWxS?mode=historic&view=data | 20:53:15 |
| hexa | oh, I confused h1/h2 with tls11/12 | 20:54:39 |
| hexa | and while we offer tls11/12 all clients use tls12 | 20:54:50 |
| hexa | * oh, I misremembered the numbers for tls11/12 as h1/h2 | 20:55:11 |
| hexa | so one thing we could add is a https record with alpn information | 20:55:34 |
| hexa | and see if that makes a dent, though I would be surprised if it did | 20:55:54 |
 emily | does Nix itself speak h2? | 20:58:23 |
| hexa | I would hope so, since it relies on curl | 20:58:43 |
