-
Notifications
You must be signed in to change notification settings - Fork 20
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
Someone prank the website? #54
Comments
It looks like someone has stolen the website. www.limetext.org points at an OVH IP address, not GitHub Pages. WHOIS information shows the domain was created 2019-01-18, when this project is much older than that, so I'm assuming someone else snapped up the name and created a fake version of the site. |
Is there any kind of way to get limetext.github.io to rank higher on search engines than this fake one? |
I think the domain expired at some point (maybe 4 years ago?) and was registered by someone else. Have a look at this (looks very fishy): I don't know if there's anything the devs can do about it because there's already quite some time passed since the registration. Maybe there's a small chance because it's clearly designed in a fraudulent way to generate clicks or for black hat SEO. Nonetheless they should get rid of all references to this domain. For example, it's still on the GitHub organization page: |
Done. |
Still, all project repos have the wrong link |
Instead of simply removing the link like what @zoli did on the main project page, I think it would probably be a better idea to replace them with https://limetext.github.io |
@Davester47 right, I changed them to https://limetext.github.io. |
I went to limetext.org, and I noticed some pretty serious problems that don't exist on limetext.github.io. I don't know the relationship between these two websites, but I'm pretty sure you guys control limetext.org too. Here's the problems with limetext.org:
What the heck happened to it? Is it some knockoff pretender website?
EDIT: This seems to be related to #50 except that it still isn't fixed on limetext.org.
The text was updated successfully, but these errors were encountered: