Skip to content
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

archive.* links appear to be inaccessible #1

Open
andrey-seryukov opened this issue Jul 31, 2019 · 3 comments
Open

archive.* links appear to be inaccessible #1

andrey-seryukov opened this issue Jul 31, 2019 · 3 comments

Comments

@andrey-seryukov
Copy link

2019/07/31 - both archive.is and archive.fo links are down. It may be useful to have a "backup" list of links to original pages even if their content is transient. Original URLs are useful for lookups in alternative archive services, etc. PS: Thank you for making this wiki! :)

@MaximilianKohler
Copy link
Owner

MaximilianKohler commented Jul 31, 2019

If they're not working it's probably because you customized your DNS. Probably Cloudflare’s 1.1.1.1? Solution would be to change it back to default or contact Cloudflare to see if they can fix it on their end.

That's a good point about having the original URLs available. I'm not entirely sure the best way to do that. Using archive.org instead would work since it keeps the original URL and just adds its own prefix. But I like archive.fo since it gives a short URL and you can use it to link to specific parts of long pages.

I do typically try to add the title of the study before/after any link so that the title can be searched to find the study. Typically an archive link would include additional discussion & info though, or specific quotes.

Another solution for firefox:

Add the archive sites as exceptions under about:preferences#privacy -> "DNS over HTTPS". https://support.mozilla.org/en-US/questions/1418874

@andrey-seryukov
Copy link
Author

Yes, Cloudflare it was. Changed it to ISP's default and all is working well.

@MaximilianKohler
Copy link
Owner

I'm going to leave this open so people see a "1" instead of "0" on the "issues" tab. Hopefully that will lead to more people clicking the issues tab to solve this when they run into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@andrey-seryukov @MaximilianKohler and others