Coloring the software version red is redundant as there is already a bright red icon in the flags. Also the grammar of the tooltip could be improved (see the inline patch for my suggestion).
diff --git a/js/models/relay.js b/js/models/relay.jsindex 2a4fe17..f4ea7c6 100644--- a/js/models/relay.js+++ b/js/models/relay.js@@ -56,7 +56,7 @@ define([ output.push([flag,"cloud_download_"+size[0], "This relay is more useful for building general-purpose exit circuits than for relay circuits."]); } if (flag == "Not Recommended") {- output.push([flag,"not_recommended_"+size[0], "This relay is running a not recommended software version."]);+ output.push([flag,"not_recommended_"+size[0], "This relay is running a software version that is not recommended by the directory authorities."]); } }); return output;
Some minor suggestions:
is:
"This relay is running a software version that is not recommended by the directory authorities."
better:
"This relay is running a tor version that is not recommended by the directory authorities. If you are the operator of this relay please update tor."
Trac: Resolution: fixed toN/A Status: closed to reopened
Not sure if URLs are possible but giving the (potential) operator specific information on how to get rid of this red warning, like "What version is recommended?" is certainly good.
As the flag description in the tooltip, I think I do like "This relay is running a tor version that is not recommended by the directory authorities." but I don't think this is the place to give an extended recommendation to the operator.
Do you think this could be a good place for recommendations for relay operators if we make sure it's prominent enough? This would probably be related to #6787 (moved).
Ok lets change it to (as you suggested)
"This relay is running a tor version that is not recommended by the directory authorities."
"...software version..." is a bit to generic I think.
On the relay page I would change
"Not Recommended"
to
"Not Recommended Version"
(hoping that this is not to long)
"Not recommended" might suggest that people blacklist this relay in their client torrc - which is not what we are trying to say.
On the relay page:
Red sign would fit better next to the "Platform" string, since this is technically not a flag, that would make it also more obvious to understand what is wrong with this relay.
might suggest that people blacklist this relay in their client torrc
This is a scary enough thought to consider changing this. What about "NoRecVer"? It's a little cryptic but the tooltip is still there to explain and it's then a similar length to the others. I don't think this is any worse than V2Dir or HSDir.
might suggest that people blacklist this relay in their client torrc
This is a scary enough thought to consider changing this. What about "NoRecVer"? It's a little cryptic but the tooltip is still there to explain and it's then a similar length to the others. I don't think this is any worse than V2Dir or HSDir.
Please do not make this more cryptic.
Moving the sign to the platform string and changing it from "not recommended"
to
"runs not recommended version"
should be fine.
Unlike V2Dir and HSDir this is not a flag and this information is actual actionable information to relay ops.
Removing the psuedoflag and instead adding the warning next to the platform string.
I actually found the pseudoflag really useful, because it shows up in the relay table, so I can search all my relays at once and check if any are out of date.
Removing the psuedoflag and instead adding the warning next to the platform string.
I actually found the pseudoflag really useful, because it shows up in the relay table, so I can search all my relays at once and check if any are out of date.
Maybe we can append the flag to the nickname in the search results?
Also I'm in favor of replacing the flag icon with a label. Labels are text with some styling which scale better than images and prevents the introduction of another instance of #19538 (moved).
Lastly, i noticed Onionoo doesn't add the recommended_version field to bridge details documents. Should i open another ticket for this or is this intentional?
Lastly, i noticed Onionoo doesn't add the recommended_version field to bridge details documents. Should i open another ticket for this or is this intentional?
The reason is that the bridge authority does not recommend versions, so that we'd have to take version recommendations from relay network status consensuses and apply that to bridges. There may be other issues. But I see how this would be potentially useful. Please open an Onionoo ticket for this if you want this feature to be added to Onionoo.
By moving this icon to its own column in #21635 (moved), I think it's quite noticeable even in black :) We don't want the red = bad = blacklisting thing we talked about starting in comment:11...
By moving this icon to its own column in #21635 (moved), I think it's quite noticeable even in black :) We don't want the red = bad = blacklisting thing we talked about starting in comment:11...