-
Notifications
You must be signed in to change notification settings - Fork 207
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
bundler.cn ? #1333
Comments
This has probably more to do with Google search I think. I recall in the past we had some awkward chinese websites that looked like Perhaps it may be useful to add an additional page at rubygems.org, displayed |
I hit this also - was super confusing because the page was all in Chinese and I couldn't figure out why until I noticed the URL. |
Weird! Looking at whois information, I'd say it's not ill-intentioned, so maybe we could contact owner and ask to take the site down and potentially contribute Chinese translations upstream, if the separate domain is just some leftover not intended to be consulted by anyone? It's seems very out of date. Domain seems to expire next year, so maybe this gets auto-fixed eventually? I'm also curious about which terms make this site show up high in the list. |
For me, a Google search for 'bundler check' shows the |
Wow, I have no idea why google is ranking the cn site first specifically for |
Actually, I think GitHub is banned in China, and owner seems to be CNNIC, so unlikely they'll contribute anything. Alternatively, maybe Google can fix this for us? |
|
I see, well that's good. In any case, I tried a potential improvement at #1335. Will check back in a couple weeks if something has improved. |
I'm seeing bundler.cn appear in Google search results, higher than bundler.io for some terms.
It's partially translated but most links still point to the normal Bundler URLs.
I assume bundler.cn isn't sanctioned, although it's been around since 2018:
https://web.archive.org/web/20181015000000*/https://www.bundler.cn/
There's probably nothing that can be done, so feel free to close, but I thought it worth a mention.
The text was updated successfully, but these errors were encountered: