-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect and mark servers that enforce but prevent chat reports #437
Comments
So maybe reusing green or yellow is not the best idea... |
Orange exclamation sign? |
I thought of something like that - a yellow or orange exclamation sign of some kind. But that would still be a lose-lose situation: the user may not notice the difference between yellow/orange and red exclamation sign and the server doesn't get to show a good status to the user, despite their (likely) best intentions to disable chat reporting and annoying warning. |
Anyway, initial tooltip idea:
Perhaps initially it can use the same "insecure" icon with just a changed tooltip. |
以上字段的简体中文翻译(Simplified Chinese translation)应为:
|
Idea
In 1.20.2, the server-side toast removal was done. We discussed this and it seemed like a sensible thing to do.
However, as a result there may now be servers that both enforce chat signing at the server level and prevent chat signing at chat conversion level. NCR should account for this and show the proper indicator/tooltips by that.
Reasoning
Described above
Other Information
It probably needs new tooltips, but I'm not sure if it needs a new icon - could reuse the yellow one.
The reliability of such indicator is also a bit questionable, but I still think it is possible:
Edit: I forgot the part where NCR announces the green state, in this case - if the two heuristics are met - the state can be shown as green.
Related to #177 but it is more theoretically described there
The text was updated successfully, but these errors were encountered: