Skip to content
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

expand disconnect reasons #815

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

expand disconnect reasons #815

wants to merge 2 commits into from

Conversation

NotAFile
Copy link
Contributor

add the new disconnect reasons

add the new disconnect reasons
@BR-
Copy link
Contributor

BR- commented Mar 27, 2019

Should we use piqueserver/aosprotocol#15 instead of adding more fixed strings?

@NotAFile
Copy link
Contributor Author

NotAFile commented Mar 27, 2019

There's a few things with that:

  • Those messages aren't localized to the local language of the user
  • There are already installs out there using these new error codes. If we don't add them, they will show up as "Unknown Reasons" instead.
  • It really doesn't hurt to have more reasons here. It's a simple change. Adding that proposal is good but takes more code, so I haven't done it for now.

// exceeded.
// we need to check other usages
return _Tr("NetClient", "You were kicked from this server.");
case 2: return _Tr("NetClient", "You have too many connections to this server.");
Copy link
Owner

@yvt yvt May 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word “you” might be inappropriate here because it’s not necessarily “you” who has the connections (e.g., other people behind a NAT).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had similar concerns but I was unsure how to phrase it instead. "Your IP" might be correct at the moment, but:

  • people, in general, are not that familiar with where their IP comes from, especially in larger networks and with the increased prevalence of CGNATs
  • this is a technical detail and might change in the future

Perhaps "Your location" or "Your network" is a good solution?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like "Your network's public address has too many connections to this server" would be the best solution, even though some users may not understand it, I believe it's best to deliver the most accurate message.

Maybe a text below with additional info could be added including the common reasons this might be happening.

@yvt yvt added this to the 0.1.4 milestone Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants