We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@cxbrooks wrote:
I started fixing the links in https://ptolemy.berkeley.edu/accessors/ to the wiki, for example https://www.icyphy.org/accessors/wiki/ should be /accessors/wiki, which gets redirected to https://wiki.eecs.berkeley.edu/accessors/ There should probably be a redirect in the Apache configuration for this. However, https://ptolemy.berkeley.edu/accessors/ has a link to the overview paper at http://www.icyphy.org/pubs/75.html which is not found. That URL used to redirect to https://ptolemy.berkeley.edu/projects/icyphy/pubs/75.html I do see that https://www.icyphy.org/publications.html has a link to https://www.icyphy.org/publications/2018_BrooksEtAl/ Was there a general plan to prevent link rot? I thought that links like http://www.icyphy.org/pubs/75.html were going to be fairly permanent.
I started fixing the links in https://ptolemy.berkeley.edu/accessors/ to the wiki, for example https://www.icyphy.org/accessors/wiki/ should be /accessors/wiki, which gets redirected to https://wiki.eecs.berkeley.edu/accessors/
There should probably be a redirect in the Apache configuration for this.
However, https://ptolemy.berkeley.edu/accessors/ has a link to the overview paper at http://www.icyphy.org/pubs/75.html which is not found. That URL used to redirect to https://ptolemy.berkeley.edu/projects/icyphy/pubs/75.html
I do see that https://www.icyphy.org/publications.html has a link to https://www.icyphy.org/publications/2018_BrooksEtAl/
Was there a general plan to prevent link rot?
I thought that links like http://www.icyphy.org/pubs/75.html were going to be fairly permanent.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@cxbrooks wrote:
The text was updated successfully, but these errors were encountered: