Last I read (man page) there was a way to signal tor to shutdown (when being run as a relay) so it would not accept new circuits and just let existing ones run their course, and after some time tor would exit, thus preserving a persons existing browsing session.
I don’t recall seeing an option like this when running the Snowflake Proxy. When I first began running it about two weeks ago it almost immediately took on users. But I had to reboot after a week or so. When it came back up I think it took ~ 2 hours to be used again. Not such a huge deal to me but I thought I’d ask. Mainly I’m sure it’s a bummer to be browsing the web and suddenly your snowflake on-ramp goes away. Not sure how Tor Browser recovers from that. I guess it sees the circuit is broken and negotiates a new snowflake connection.
Also, I went looking for an option to find my snowflake ID/fingerprint to see if I could use it like a bridge, i.e. enter its fingerprint before connecting, but it seems this is not possible. I thought this might make my browsing experience a tiny bit faster. Is that possible? Planned?
Finally, with regards to nomenclature, I understand what guards are, versus middle relays and exits. I also understand there’s a diversity of methods to get into the tor network, aka pluggable transports. Aren’t bridges and snowflake proxies also guards? I mean, bridges and snowflake proxies aren’t used as middle nodes best I can tell from my reading.
Thanks.