Apparently it is reachable. I think this state means nothing to the user. Maybe it’s just a matter of rewriting the status? @ttk2 ping me about this so that I can refresh my memory on what this state means.
That’s a good point, I still think that it is confusing to the user since they will be expecting the neighbors screen to show physical neighbors. We may want to consider a gateway-specific exit interface in the future. For now, I’m guessing we can just filter them out pretty easily right?
Seeing this for the first time didn’t really confuse me much. However, it might make more sense as yellow prior to registration.
Personally, the entire “submitting registration request” isn’t needed once the error message comes back as denied. As a user, this message is kind of annoying since everything prior to registration was acting like I could register and then it region locks. Not sure how difficult it would be to know these are region locked before registering.
The techy in me loves this. The user in me had no clue what it was other then exit nodes. The tester in me probably needs it and while I love that one of my neighbors ipv6 is “leet elf” it might need other names.
That’s a good point. I’ve forgotten all the exit listing state machine states, but IMO once the exit has been contacted (GotInfo?), there’s no reason we shouldn’t be able to display whether or not the region is OK. I believe this would be somewhat involved to implement though so we can just put it in the backlog for now since it is not a critical feature.