-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
feat(ProxyManager): mass-importing proxies #5069
Conversation
…use (to fix detekt)
…feat/mass-proxy-importing
* Added multi atlas support * Fix detekt * Stop using the test atlas size
…from clipboard and from file mfw it's just a 4 line change, why didn't I do this before when I added the endpoints?...
…ented imports & fix indentation
…o feat/mass-proxy-importing
private val FALLBACK_PING_SERVERS = listOf( | ||
"mc.hypixel.net", | ||
"crescentkingdom.com", | ||
"gratopia.gg", | ||
"terranova.mc.gg", | ||
"play.arcanecloud.net", | ||
"ping.liquidproxy.net" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we will not use this. The LiquidProxy Ping Server serves it's purpose to respond with the IP address of the proxy, without we are not able to detect the outgoing IP of a proxy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh. But what about the server list idea? Aren't we supposed to reuse the server list as ping servers? because I can tell you that no one would want to join a server which shows their IP as the MOTD or the kick message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are you talking about?
Mass-importing proxies (see #4606 for previous PR)
Because I want to mass import proxies from a text file that is splitted by a newline (
\n
)Fixes #4599
reopened because izuna forgot to change the base branch for some PRs before deleting the nextgen-1.21.4 branch