Did you read this post linked above? Release preparation v1.131 - #15 by arrogantrabbit
Virtually no customers are using quic
However, every single customer attempts TFO. Therefore I would channel the efforts to verifying that TFO is working instead, It will be much more impactful. QUIC is only interesting to Google, as evidence by it incessant breakages in the upstream library.
If I was storj I would remove QUIC from dashboard and add TFO status instead.
opened 02:28AM - 13 Jul 25 UTC
Enhancement
**Describe the feature or problem you'd like to solve**
Virtually no customers … are using QUIC:
https://forum.storj.io/t/quic-misconfiguration-in-v1-86-1/23610/25?u=arrogantrabbit
QUIC connectivity is flaky and breaks from upstream library release to release
A lot of SNO see red Misconfigured and waste a lot of time fixing it, with zero benefit to anyone.
On the contrary, every single customer attempts to use TFO.
https://forum.storj.io/t/please-enable-tcp-fastopen-on-your-storage-nodes/22886/183?u=arrogantrabbit
Therefore, there is much more bang for buck for storj and SNO in spending time ensuring TFO is enabled.
**Propose a Solution**
1. Add TFO status to dashboard.
1. Optionally, remove QUIC status from the dashboard, and then perhaps retire is and stop wasting development cycles maintaining it.
How to check if TFO is working: Please enable TCP fastopen on your storage nodes - #184 by arrogantrabbit
2 Likes