-
Notifications
You must be signed in to change notification settings - Fork 101
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
Remove or edit github pages #68
Comments
IIRC we discussed something along these lines with @mirohs and I am not sure if everything listed is technically possible due to missing permissions. Any insight @mirohs ? If permissions are the issue, then we shall contact ICANN and request transfer of ownership/permissions (or alternatively wait for the domain to expire). |
I'm quite sure that ICANN is not involved here. We are talking about a simple subdomain, that is managed by github.io, aren't we? When thinking about my suggestions above, the most simple and propper solution would be:
This could be done within a single .htaccess file. Therefore the GitHub page for the old GH repository has to be re-generated. For doing this, we must have access to the old GH repository or Eugen Kiss must merge a pull request and re-generate GitHub pages afterwards. The advantage of this solution is, that Google & Co. are updating their indexes automatically and search results will point to the new GitHub page of the new GH repository. Legend:
|
Oh, I should not be writing anything when sick in my bed. Of course ICANN has nothing to do with subdomains nor with github.com . I remembered (wrongly) that there was some personal domain (not subdomain) from Eugen and reacted to that instead of carefully reading your text. I will rest a bit and once I feel a bit better I will try to reply with more cautiousness 😉. Thanks for all your work on this and your vigilance! |
No problem and get well soon! |
Since the whole content of this repository including github pages was moved we should do at least one of the following:
The reason for this is dublicate content and to not confuse visitors landing on this page.
And BTW: I would prefer option 4) since this would inform google & co correctly, that the page was moved.
The text was updated successfully, but these errors were encountered: