The web widget doesn't work for @reflog when using his home internet. His widget simply acquires no connections. I watched his console during execution, and it just reports a lot of NAT traversal timeouts.
@reflog reports that he knows himself to be behind a double NAT.
Can we make it work for @reflog? If not, can we detect the network condition that's preventing traversal such that clients (both uncensored and censored) can report it when sending traces at the time of traversal failure?
I think this is a use case for something like Snowflake's probetest service. I wonder what it would report for @reflog...
The web widget doesn't work for @reflog when using his home internet. His widget simply acquires no connections. I watched his console during execution, and it just reports a lot of NAT traversal timeouts.
@reflog reports that he knows himself to be behind a double NAT.
Can we make it work for @reflog? If not, can we detect the network condition that's preventing traversal such that clients (both uncensored and censored) can report it when sending traces at the time of traversal failure?
I think this is a use case for something like Snowflake's probetest service. I wonder what it would report for @reflog...