Spencer C. Imbleau

> According to this: https://wpt.fyi/results/webtransport?label=experimental&label=master&aligned serverCertificateHashes should be supported in FF 127 I tested FF 127 (Nightly), mentioned earlier. Specifically, The first connection gives this error: (related to https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream/getReader ?)...

> Its the most likely explanation since the issue occurs during the handshake. > > Definitely requires some more testing to confirm though! How can I help to narrow that...

Anyone that feels comfortable with testing this with a LetsEncrypt/ACME cert?

> The main issue with using WT in prod is that WT in itself isn't really production ready yet :/ Ah yeah, I was meaning "experimentally ready". My game still...

I'll help give #144 a nudge, as I agree that is the biggest blocker. For the time being I could circumnavigate #251 by testing on Chrome only (I already do,...

Why not eliminate the `Trunk.toml` entirely for Cargo.toml environment configuration? It serves virtually the same purpose, but the `Trunk.toml` adds noise to the root. Other, mature bundlers, such as [`cargo-lambda`](https://www.cargo-lambda.info/)...

re: Cargo.toml config - Personally I see more people using the Cargo.toml than a bespoke file. I think it should've been the default from the beginning, personally. Examples: - [`cargo-apk`](https://github.com/rust-mobile/cargo-apk?tab=readme-ov-file#manifest)...

Let's plan to support both. As far as the cargo features go, I want to avoid confusion. Anything that would exist in the `Trunk.toml` should preface with `package.metadata.trunk`, ```toml //...

> Yup, that sounds great. Personally I would also be keen on seeing: > > ```yaml > # Trunk.yaml > $schema: "trunkrs.dev/config.schema.json" > profile: > release: > features: ["prod"] >...

> Thinking about "when", I would prefer to finish up `0.20.0` first, and then work on that for `0.21.x`? Would that work for you? Sure, this feels like a great...