Help talk:Using the Wayback Machine
![]() | Wikipedia Help NA‑class Low‑importance | |||||||||
|
Proof Of Concept
Check this sandbox history page to see. --TIB (talk) 20:16, Aug 22, 2004 (UTC)
"Improperly formatted links"?
The "improperly formatted links" given in the article seem to work just fine! Brianjd | Why restrict HTML? | 09:52, 2005 Mar 20 (UTC)
- They work fine in my system too. My browser is Opera 8.01 running on WinXP system. This wouldn't be browser dependant? --The Merciful 15:13, 24 July 2005 (UTC)
- They used to break, the wiki software has been fixed to cause them to work properly. The link would break at a semicolon and the rest of the text was cut off, so links broke. I suppose this article should be deleted, now that the software works. --TIB (talk) 00:03, August 8, 2005 (UTC)
- I take that back, for some reason the first one works (one version) but the all versions one doesn't, because of the asterisk. Why did you confuse me? --TIB (talk) 00:06, August 8, 2005 (UTC)
I agree with the previous comment. In my browser too the so-called "incorrect" code works fine! - anon.
Templates
The "broken" links work fine for me, but to make things hopefully easier I have made a few quick templates, {{wayback}} (which links to a site's archive), and {{waybackdate}}, which links to specific instances of a site. I hope they are helpful to someone! --Fastfission 22:46, 23 August 2005 (UTC)
Colons are no problem
As you can see, this link: [1] which doesn't use any silly replacement technique for its colon (:), works just fine. Maybe this was fixed with a later release of Mediawiki? --Michiel Sikma 14:20, 31 December 2005 (UTC)
[http://web.archive.org/web/19980112230112/http://www.planet.nl/]
I wonder
I wonder if anyone is reading this talk page, but should Wikipedia even allow Wayback people to archive our site? I realize Wikipedia is licensed in GFDL, etc. but there are many copyright violated pages that subsequently become archived in their site, and that's not something that we want to encourage. As for most search engines, they re-cache after a while (Supplemental Index of Google being the exception), but the Wayback Machine keeps a pernament copy. -- WB 07:59, 22 January 2006 (UTC)
- You said it yourself: Wikipedia is licensed under GFDL, so anybody can archive it. Period.--Eysen 02:21, 11 January 2007 (UTC)
automatic caption
i used the first template in Josiah Royce#References and encountered two bugs. first, it links to a specific version, not to the list. second,it creates an automatic anchor text which is both noninformative and not related to the page title. i could easily add text, but couldn't think of a way to delete the automatic part ("josiah royce", specifically). how and why does it happen? trespassers william 21:35, 7 January 2007 (UTC)
Other archiving systems
I wonder why Wikipedia is dwelling on using the Wayback machine to recover broken links, without even mentioning other archiving systems such as WebCite. As Archive.org is far from complete, there should be crosslinks to other articles describing how other services like WebCite can be used. Note that WebCite - in contrast to Wayback machine, which uses a shotgun-approach using a crawler - allows editor/author-initiated prospective archiving (taking a snapshot before the website disappears), which - if this would be done consistently by authors, a part of the Wikipedia "citing sources" policy, or handled by bots - would avoid the problem of link rot on wikipedia in the first place. Countless hours of editors are wasted just to eliminate broken links and trying to recover cited source. --Eysen 02:21, 11 January 2007 (UTC)
Output of Template:Wayback
I've proposed a minor change in wording at Template talk:Wayback. Comments appreciated. John Broughton | Talk 20:31, 12 January 2007 (UTC)
Use with {{cite web}}
Where the {{cite web}} template is already in use, we should just add archiveurl and archivedate arguments, right? 82.36.30.34 (talk) 06:07, 10 December 2007 (UTC)
Site Parameter note being transcoded
I could not get {{webarchive |url=https://web.archive.org/web/*/site= |date=* |title=Guinness Book of World Records 2005 - SCIENCE AND TECHNOLOGY << BUILDINGS }}
to work correctly. The site parameter was not picked up. I had to use {{waybackdate}} instead, with an additional date parameter, which worked fine. Was using the template in a sub-section of the CN Tower article. papageno (talk) 02:01, 10 April 2008 (UTC)
Outdated
- Out is the information the page out of date? Hyacinth (talk) 20:42, 6 July 2008 (UTC)
- I agree. The Wayback Machine website has changed. It now it shows the history directly when putting the URL or using the submit button. Please update this. Timofonic (talk) 12:40, 19 July 2017 (UTC)
Attempted killing of this useful site
Some editors are trying to kill off this template
- Wikipedia talk:Dead external links#No reason to link to an archive copy of a page
- Wikipedia talk:External links#Archived versions
DG and a few other exclusionists/deletionists have basically taken over WP:EL for months now (they just wear out anyone who tries to discuss things with them). We could really use some Wikipedians with more common-sense over there..... frustrated (talk) 21:34, 6 September 2008 (UTC)
- I have no idea what you're talking about - can you be more specific? --Ludwigs2 02:11, 7 September 2008 (UTC)
- See this diff, which is based on the 2nd thread I linked above. (DreamGuy has multiple rfcs and an arbcom, all about civility, but he treads the line enough to not get blocked - see his usual-rude reply to Jmabel at the 1st thread I linked above. (He's the cause, but I'm just trying to get people involved in fixing this particular symptom)) frustrated (talk) 00:09, 8 September 2008 (UTC)
archivedate/accessdate
I believe the example archivedate and accessdate values given in Wikipedia:Using_the_Wayback_Machine#Cite_templates are the wrong way round. Am I right? Open4D (talk) 13:59, 13 December 2011 (UTC)
- In general, people should be adding
|archiveurl=
and|archivedate=
parameters and not adding|accessdate=
as that is much less useful. When a date-stamped article also has a date-stamped archive copy, the accessdate is completely irrelevant. -- 86.144.190.83 (talk) 18:10, 9 October 2013 (UTC) - What about explaining this in the page? Timofonic (talk) 12:42, 19 July 2017 (UTC)
Use of Wikipedia as the example site
I believe the use of wikipedia.org as the example of a website that has been archived by Wayback Macine has the unnecessary possibility of confusing someone, and would propose that any other site be used - e.g. un.org, disney.com, guardian.co.uk. Thoughts? Open4D (talk) 14:00, 13 December 2011 (UTC)
- I agree. Any of the three websites you mentioned would be fine. Or you may choose http://www.example.com/, but it is a worse choice because it's not a commonly-known website. Feel free to make the change. —Unforgettableid (talk) 01:40, 10 October 2013 (UTC)
- Why not change it? Why this discussion ended and nothing has been done? Timofonic (talk) 12:44, 19 July 2017 (UTC)
The server web.archive.org doesn't work
The server http://web.archive.org/ hasn't been accessible for more than a month. Does anybody know what's the problem and when it will be accessible again? --Лъчезар 09:37, 21 September 2012 (UTC)
- It's working fine for me - both that direct link (which redirects to http://archive.org/web/web.php) as well as instances of Template:Wayback and Template:cite web's archiveurl. Can you give example(s) of the exact error and location that you're encountering? —Quiddity (talk) 19:47, 21 September 2012 (UTC)
- It's a DNS resolver problem. I'm in Bulgaria and my ISP is the Bulgarian Telecommunications Company. The DNS address "web.archive.org" just can't be resolved here. When I resolve it from abroad and try to access that IP address by HTTP, it gives "HTTP/1.1 302 Unknown Error" and somehow redirects back to "web.archive.org", which fails to resolve again. --Лъчезар☭共产主义万岁★ 17:50, 24 September 2012 (UTC)
- They just fixed the problem, after a complaint I did yesterday. --13:47, 27 September 2012 (UTC)
- It's a DNS resolver problem. I'm in Bulgaria and my ISP is the Bulgarian Telecommunications Company. The DNS address "web.archive.org" just can't be resolved here. When I resolve it from abroad and try to access that IP address by HTTP, it gives "HTTP/1.1 302 Unknown Error" and somehow redirects back to "web.archive.org", which fails to resolve again. --Лъчезар☭共产主义万岁★ 17:50, 24 September 2012 (UTC)
For subscription only material
Should the tool be used at all for subscription only material like billboard.biz charts (now moved to billboard.com/biz)? It seems like a copyright violation of some sorts. There should probably be a word of caution if so. ⊾maine12329⊿ talks✿wiki 02:16, 15 June 2013 (UTC)
- http://www.billboard.com/robots.txt does not disallow archiving. -- Gadget850 talk 11:29, 21 July 2013 (UTC)
Wayback API
I just learned of this: mw:Archived Pages: "The Internet Archive wants to help fix broken outlinks on Wikipedia and make citations more reliable. Are there members of the community who can help build tools to get archived pages in appropriate places? If you would like to help, please discuss, annotate this page, and/or email alexisarchive.org." - leaving the link here in case anyone else is interested or can help. –Quiddity (talk) 16:38, 31 October 2013 (UTC)
- What happened to this? Any news? Timofonic (talk) 12:53, 19 July 2017 (UTC)
HTTP Secure
Since October 24, 2013, the Internet Archive uses HTTP Secure by default. Should we reflect that by recommending the use of https://
links on this manual, or not? Please discuss at WP:VPM. --bender235 (talk) 13:14, 9 November 2013 (UTC)
- I hoped within half a year somebody would comment on this. --bender235 (talk) 09:31, 5 May 2014 (UTC)
- You did direct people to WP:VPM where it looks like it was discussed (before the time that I was active here). Personally, I have no preference. --Otus scops (talk) 10:02, 5 May 2014 (UTC)
Archive problem - redirect loop possibly?
I've no idea if this is a reasonable place to ask this, or if there even is a place to ask. I've been fixing links to PrimeraHora.com and adding updated urls to the internet archive. However, I've just realised that the archived copies aren't working properly - the page initially loads OK, but then loads a second copy in a box on the right of the page and, presumably, another to the right of that, etc, until the page goes blank after about 20 seconds. I'm not sure if this is a redirect and hitting the 5 redirect limit or something else. (Firefox gives the behaviour above - IE doesn't (for me) show the extra versions of the page loading but goes straight from showing the page briefly to a blank screen.)
Some examples - an original page with an archive created today:
"A punto de revivir a los Senadores de San Juan en el béisbol invernal" (in Spanish). Primera Hora. August 5, 2010. Archived from the original on 2014-04-21. {{cite web}}
: Italic or bold markup not allowed in: |publisher=
(help); Unknown parameter |deadurl=
ignored (|url-status=
suggested) (help)
It seems to have something to do with the box on the right of the page called "Las +".
I tried using the "id_", "js_", "cs_", and "im_" option mentioned on Help:Using_the_Wayback_Machine#Specific archive copy.
In Firefox, the "js_" option actually looks OK and seems to work (though it adds a bar at the top). In IE, it works but doesn't render very well. Is that my best option or can anyone suggest something else I can do to prevent the infinite loop / blank screen?
Alternatively, should I ask this somewhere else?
Thanks for any suggestions.--Otus scops (talk) 23:18, 21 April 2014 (UTC)
- I've commented out the links because I get the impression that someone at the IA is working on it. My example link had disappeared from the IA (until I accidentally added it again). I'll reinstate them in a few days if I don't hear anything. --Otus scops (talk) 21:42, 22 April 2014 (UTC)
- I guess it was a IA blip - links now point to the original archived version again. --Otus scops (talk) 20:40, 23 April 2014 (UTC)
I'm ignorant of javascrip and I can't seem to find an answer to this by searching. I wonder if anyone knows of a way to modify these scripts so that they open in a new browser window? I would like to go to the Wayback Machine in a new window and leave the page I'm viewing open. Is this possible?
javascript:void(location.href='http://web.archive.org/web/*/'+document.location.href)
(Search)javascript:void(location.href='http://web.archive.org/save/'+document.location.href)
(Save)
Thanks for any assistance anyone can provide.—D'Ranged 1 talk 16:56, 8 May 2014 (UTC)
- Have you tried it? It opens in a new tab (rather than window) for me in Firefox. I don't think I changed anything to get it to work like this.--Otus scops (talk) 17:34, 8 May 2014 (UTC)
- @D'Ranged 1:I've just double-checked (now that I'm on my computer) and my bookmarklet points to
javascript:void(window.open('http://web.archive.org/web/*/'+location.href))
- The window.open might make all the difference.--Otus scops (talk) 21:36, 8 May 2014 (UTC)
FWIW, I was having a hard time using the bookmarklet on network/http-related errors so I came up with a Chrome-specific solution. I'm not sure if it's worth adding to the main page so i'll let you decide. What it does is load the url from Chrome's error page if there, otherwise fallback to location.href:
javascript:void(location.href='http://web.archive.org/*/'+(location.href==="data:text/html,chromewebdata"&&loadTimeData.data_.summary.failedUrl||location.href))
216.162.78.214 (talk) 00:28, 18 August 2016 (UTC)
Sources
Does citing a webpage using the Wayback Machine always constitute a secondary source, even if the existing original or current version of the archived page would be considered a primary source? Technically, the Wayback Machine is secondary, as it is one party copying or quoting the material of another party. But does this create a loophole, where instead of citing the original material, one cites the Wayback Machine's version of this other party's material, in order to claim it's a secondary source? Sorry if this has been explained already, but I haven't seen it.--Wasp14 (talk) 21:37, 2 June 2014 (UTC+1)
- @Wasp14: The creator of a typical secondary source would be thinking about the material, assessing it and reworking it. Examples would be newspaper journalists or book editors. The Wayback Machine is just preserving the original, without any editorial steps. So when it copies a primary source I'd say that the copy counts as a primary source too. -- John of Reading (talk) 21:01, 2 June 2014 (UTC)
- (edit conflict)@Wasp14: No, if it was originally a primary source, it's still a primary source from the Wayback Machine. And it was was an unreliable source it's still unreliable. The Wayback Machine archives anything and everything that someone has requested (unless the site blocks archiving) - there's no mechanism by which it decides the VALUE of a site or comments on it. It's just a (very) useful source of no-longer available webpages.--Otus scops (talk) 21:23, 2 June 2014 (UTC)
Citing the Wayback Machine
Why cite the Wayback Machine as template {{Wayback}} does?
If it's important, why does this page cite Internet Archive instead (ref 2)?
--P64 (talk) 01:38, 22 July 2014 (UTC)
- That template got deleted and replaced by {{Webarchive}}. I just mention it to avoid confusion, as I had while trying put an archived version of a site that is no longer available. Timofonic (talk) 13:00, 19 July 2017 (UTC)
This article needs to talk about references which are bare URLs
This article should talk about converting a reference which is a bare url (Example: <ref>[http://www.deadlink.example.com/some_dead_link.html Some dead link]</ref>) in to a “proper” web archive link. I ended up making the bare URL a link to the wayback version of the URL in question: diff. Samboy (talk) 15:42, 7 March 2015 (UTC)
Suggestion: a bot that automatically retrieves a Wayback Machine's archived page for dead link
So I'm not sure if there still are bots checking for offline links - made a post that at the idea lab: A bot that checks for offline-links. And I'm also not sure if this is the right place to post this - and not say somewhere on Village Pump or Phabricator. But anyway here's my idea which is also relevant if there are no more bots checking for offline links:
What about a bot that scans through wiki-pages for references marked as dead links (the syntax for that is:{{dead link}}) and automatically retrieves the page archived by the Wayback Machine that is closest to the accessdate (in the case of it being specified) and then either automatically makes an edit right away or proposes this via a comment behind the deadlink, or an extension of the dead-link parameters or by the use of an external tool.
What do you think? --Fixuture (talk) 22:39, 18 March 2015 (UTC)
- One problem to think about: when a web page is taken down, it's often replaced with either an error message ("Sorry, this story is no longer available") or by generic advertising. The Wayback Machine's archiving bot faithfully copies these useless pages into its archive. I think this rules out any fully-automated use of these Wayback Machine links, as only a human can decide whether the archive page is a useful reference. -- John of Reading (talk) 07:42, 19 March 2015 (UTC)
- Yes, that's the reason why it would just make a comment or add another entry in a new dead-link-template parameter: it wouldn't show up on the page but causes the watchers of an article to check the link and if it's ok they'd just need to uncomment the part or otherwise (for example via an external tool) confirm that the archive-link is correct & fine. --Fixuture (talk) 18:24, 19 March 2015 (UTC)
- Checking for only archives taken as a close as possible to, but before the access date should pretty much eliminate this problem.--greenrd (talk) 08:37, 3 May 2015 (UTC)
- I even suggest the bot go through live links and create archive copy if Wayback machine doesn't have it, and add archive-url, archive-date and url-status=live to the reference, so we're ready when the live link rots. This seems to be InternetArchive Bot Numbersinstitute (talk) 19:37, 12 April 2020 (UTC)
- URLs added to Wikipedia (across all wiki languages) are saved at the WaybackMachine within 24hrs of being added to Wikipedia. -- GreenC 20:06, 12 April 2020 (UTC)
- I even suggest the bot go through live links and create archive copy if Wayback machine doesn't have it, and add archive-url, archive-date and url-status=live to the reference, so we're ready when the live link rots. This seems to be InternetArchive Bot Numbersinstitute (talk) 19:37, 12 April 2020 (UTC)
The 14th month
This isn't right. "YYYYMMDDhhmmss" - "20131404315600" —User 000 name 23:58, 2 May 2015 (UTC)
accessdate=</nowiki>{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY2}}<nowiki> did not work when I tried it
The sample code at the end of the intro section of this article didn't work for me.
Here was my attempt: [2] (see reference 38).
Can anyone confirm and/or fix this?
Thanks. --Mathieu ottawa (talk) 14:29, 15 August 2015 (UTC)
Why can't I save this page?
I'm trying to archive this page but when I go to https://web.archive.org/save/https://forum.quantifiedself.com/thread-my-phone-and-me I get an error that "This url is not available on the live web or can not be archived.". That's just bogus. I'm the admin of that site, and the robots.txt doesn't disallow that URL. Thousands of different URLs from the site have been archived successfully. What's up? -- Dandv 03:07, 3 October 2015 (UTC)
- I'm not sure what happened, but the site just got archive by what it seems a generic (spam) advertising site. Timofonic (talk) 13:06, 19 July 2017 (UTC)
Faulty markup in an example
The current page contains the following example:
<ref>{{<!-EXISTING REFERENCE->|archive-url=https://web.archive.org/web/20021128120000/http://www.originalurl.com|archive-date=2002-11-28|access-date={{subst:YYYYMMDD|d}}|dead-url=yes}}</ref>
That should surely be (with the proper XML comment markup):
<ref>{{<!--EXISTING REFERENCE-->|archive-url=https://web.archive.org/web/20021128120000/http://www.originalurl.com|archive-date=2002-11-28|access-date={{subst:YYYYMMDD|d}}|dead-url=yes}}</ref>
Can someone sort this out please? Best wishes. RobbieIanMorrison (talk) 17:54, 29 September 2016 (UTC)
Done @RobbieIanMorrison: Not sure why it took so long, or why you did not do it yourself. – Allen4names (contributions) 23:58, 26 February 2017 (UTC)
nytimes.com robots exclusion standard
Hi, I've noticed that the Wayback Machine archives pages from the domain nytimes.com regularly and that I can access those pages on the Wayback Machine without getting an error message about robots.txt. While some pages archived required a login, the site overall doesn't seem to be using its robots exclusion standard. In fact, nytimes.com/robots.txt has /archives/ listed but not /archive/ which would presumably disallow the Wayback Machine from viewing. Is this standard still applicable? Thanks, Icebob99 (talk) 14:16, 5 November 2016 (UTC)
Add a notice that archive.org is blocked in China
According to Websites blocked in mainland China , archive.org is blocked in China. ShadowYC (talk) 23:11, 15 February 2017 (UTC)
- I agree about this. I think Wikipedia is blocked in China too. Would be relevant to provide an alternative access method or just expect that people in China would use methods to avoid the blocking to access Wikipedia and other sites? Timofonic (talk) 13:07, 19 July 2017 (UTC)
Outdated Browser?
What's with the message: "It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all). We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera" (See Curse, Inc. reference 77 as of 09:17, 25 April 2017 edit)
I get the same error message from Firefox and Chrome, both are up to date.
Softtest123 (talk) 04:45, 2 May 2017 (UTC)
Need a newer example than Washington Post
www.washingtonpost.com no longer blocks ia_archiver. Searching for "user-agent%3A+ia_archiver"+ext%3Atxt "user-agent: ia_archiver" ext:txt on Google brought up www.qualcomm.com and xiph.org but these are lesser known websites than washingtonpost.com.
Which site(s) could be used instead? — Preceding unsigned comment added by Lol MD4 (talk • contribs) 05:39, 19 May 2017 (UTC)
- My suggestion: Historical reasons Timofonic (talk) 15:28, 19 July 2017 (UTC)
- Historical reasons (I got tired to putting exact references, but most of the original ones are on NCSA What's New (mirrored [3] Desy.de] or Unicom.com) and CUI W3Catalog zipped snapshot (from W3 Catalog History archive mirror on Software Composition Group). Feel free do add, modify, suggest or whatever. Maybe finding the most popular and ancient sites would be a good middle ground.
- home of the first website (1990) [1][2]
- Aliweb (1993) [3]
- World Wide Web (1993) [4]
- First International Conference on the World-Wide Web (1993, updated 1994) [5]
- Electronic Frontier Foundation (1993) [6]
- TinyTIM WWW Page (1993)[7]
- Welcome to Netscape (1994) [8]
- The San Francisco FogCam! (1994). The world's oldest webcam.[8]
- Strawberry Pop-Tart Blow-Torches (1994)[8]
- Fantasy Baseball Home Page (1996)[8]
- CNN’s O.J. Simpson Trial Page (1995 or 1996)[8]
- Klingon Language Institute (1996)[8]
- Washington Post’s “Year in Review” (1996) [8]
- Bob Dole/Jack Kemp Presidential Campaign (1996) [8]
- Three Rives Stadium (1998) [8]
- You’ve Got Mail (1998) [8]
- Internet Explorer is EVIL! (1998) [8]
- The Robert Deniro Page (1999). Currently dead, it's a link to the last archived page. [8]
References (incomplete, sorry)
- ^ World's oldest website revealed: First internet page is now 25 years old, Mirror Online.By Jasper Hamill, 21 DEC 2015
- ^ First website ever made
- ^ 23 Ancient Web Sites That Are Still Alive, Mental Floss. By Attila Nagy 11/15/12 3:05pm.
- ^ What's New, June 1993, desy.de
- ^ First International Conference on the World-Wide Web,404PageFound
- ^ [www.desy.de/web/mosaic/old-whats-new/whats-new-1293.html NCSA What's New, December 1993], mirrored by desy.de
- ^ TinyTIM WWW Page,404PageFound
- ^ a b c d e f g h i j k l 17 Ancient Abandoned Websites That Still Work, Mental Floss. By Lucas Reilly. November 22, 2013.
Timofonic (talk) 15:28, 19 July 2017 (UTC)
Suggestions for updates to example wikitext for "EXISTING REFERENCE" in the lede
background
When I was making this edit, -- just today -- I was guided partly by the "example wikitext" shown in the last sentence of the lede of this ("how-to guide") article -- displayed (right before the [Table of] "Contents") as:
In short, this is the code that needs to be added to a reference:
<ref>{{<!--EXISTING REFERENCE-->|archive-url=https://web.archive.org/web/20021128120000/http://www.originalurl.com|archive-date=2002-11-28|access-date={{subst:YYYYMMDD|d}}|dead-url=yes}}</ref>
suggestions for fixing two suspected TYPOs or other possible "mistakes", there
- I think that the advice about what to add, should recommend adding an "
archive-date
" field, but it should not mention (adding nor changing) the "access-date
" field. Note that in my recent edit, I added an "archive-date", but I did not modify the "access-date" ... partly because the "{{cite web}}" template [instance] (which was being updated) already had an "access-date" field [value]. That date (which was in 2008) was a date when the "original URL" link was not "yet" a dead link, [!] and ... due to circumstances ... I was (regretfully!) having to add "|dead-url = yes
" to the "{{cite web}}
" template [instance] which was being updated. So, I ignored the suggestion to add "{{subst:YYYYMMDD|d}}
" to the "access-date
" field. Doesn't that give a "today's date" value? (it gives the date of the "edit" or update ... right?) IMHO that would have been "false and misleading" for the original URL, and for the "archived" (Wayback machine) URL, I figured that the "archive-date" was more appropriate. - Also: When I did a "show preview" during editing, (by clicking on the button labeled "show preview"), I got an error message, with some words displayed in a RED font -- ("!") -- saying << "Check date values in: |archive-date= (help)" >>. (...and the word "help" was a hyperlink, to some "help" page). I am not sure what was wrong, but I figured that maybe dates like "2002-11-28" used to be allowed, but are no longer allowed. So, I used an ordinary "date" character string for that field, ("February 14, 2009") (you can view the "date" as part of the URL, by looking at the DIFF "[see above]") in order to get rid of that error message.
- Has this been fixed? I hope someone comments on this Timofonic (talk) 13:09, 19 July 2017 (UTC)
Any Comments?
If there are no comments here within a few weeks (OR, if there are only some comments that agree with my "suggestions", or otherwise fail to [or, do not try to] convince me to change my mind), then ... I intend to proceed with implementing these "suggestions", by editing this article (that is, "Help:Using_the_Wayback_Machine") as suggested above.
If you want to prevent that from happening, or suggest some different changes, or entertain readers by including some off topic jokes about the universe, here ... then feel free to chime in. --Mike Schwartz (talk) 20:34, 14 July 2017 (UTC)
- I don't understand what's happening. Also, the user didn't sign her/his comment. Any idea about this? I'm confused, I just wanted to change a dead link to an archived version on a Intel_MCS-48 article (Coprolite 8048 Projects). Now I'm completely confused about what to do. How to make it more clear? I can contribute in editing, but first I need to understand it. Timofonic (talk) 13:16, 19 July 2017 (UTC)
the EDIT (discussed here) has been done (but comments are still welcomed)
The EDIT (discussed above) [by Mike Schwartz (talk)] has been done now.
The changes made to the "Help:" page (that "goes with" this "Help_talk:" page) can be seen by looking at this DIFF.
If any of you are not happy with that edit, then you are still welcome to "chime in" here. I might not be as confused as Timofonic (talk), but sometimes I do have "some" episodes of misunderstanding.
In fact, it is possible that, if that edit did improve that snippet of "example" wikitext to be added (to an "EXISTING REFERENCE" such as a URL of the dead link[dead link ] "persuasion", inside [e.g.] a "{{cite web}}" template instance inside a "<ref>
" tag) ... then maybe it will even "Help:
" -- (no pun intended!) -- to clarify the confusion ("Now I'm completely confused [...]") allegedly reported by Timofonic (talk). OR ... maybe it will just help a little bit, ... but maybe not that much. --Mike Schwartz (talk) 17:42, 31 July 2017 (UTC)
Valid external link?
Is
[http://javascript:void(window.open('https://web.archive.org/save/'+location.href) Wayback Save]
a valid HTTP link? Yes I am sure it works, but I don't think the [ and ] around it will make it useful to be clicked on from this page in most browsers. Jidanni (talk) 15:25, 4 November 2017 (UTC)
- That does not look like a valid HTTP link. Incidentally, Mozilla Firefox 57 won't even let me bookmark it. (It tries to protect users from creating invalid bookmarks, which might even be a good feature if it didn't also block some valid URIs.) Since the link (and others like it) can neither be followed, nor used to produce a working bookmark (it doesn't actually work, even when the browser allows creation), it doesn't seem to serve any purpose. Takatiej (talk) 00:31, 16 January 2018 (UTC)
Announce: RfC: Nonbinding advisory RfC concerning financial support for The Internet Archive
Wikipedia:Village pump (miscellaneous)/Archive 57#RfC: Nonbinding advisory RfC concerning financial support for The Internet Archive --Guy Macon (talk) 12:13, 22 December 2017 (UTC)
Wayback Machine not returning search results today ....
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Currently, any URL I place in the Wayback search field [4] does not return any results. There's no list of years, nothing. There's just a blank page like this [5] at present. I've tried a half dozen random URLs to check, but nothing comes up (not even the message "Hmm, Wayback doesn't seem to have that page archived"). I don't know what's wrong or what to do about it. It was working fine less than 24 hours ago. Any help or advice of what to do or where/how to report it? (I'm going to post this message at WP:VPT as well.) Softlavender (talk) 06:54, 30 July 2018 (UTC)
- To keep the discussion in one place, I suggest continuing it here, not at VP:VPT. The following comment was posted at WP:VPT. --Pipetricker (talk) 09:56, 30 July 2018 (UTC)
Strange. I found the same results with Safari and Firefox. From a quick look at the page source, it seems it's not loading completely. It does, however, load pages when one has a link, e.g. this will work. You might try posting to their 'FAQ forum' listed at the bottom of this page; you could also email info@archive.org . BlackcurrantTea (talk) 08:32, 30 July 2018 (UTC)
- Yes, as I stated, it's not returning search results for any URL. There is no place to raise the issue at their forums (I checked). I emailed info
archive.org two hours ago (that's the only email they provide); it would help if more people emailed them as well so they take the issue seriously. Thanks! Softlavender (talk) 10:05, 30 July 2018 (UTC)
- @Softlavender: Initially it failed for me but now it seems to be working. I'm not sure why. Jc86035 (talk) 15:10, 30 July 2018 (UTC)
- Yes, as I stated, it's not returning search results for any URL. There is no place to raise the issue at their forums (I checked). I emailed info
- Thanks, yes, they seem to have altered the interface so that the year sections are very small. Possibly they were in the middle of making that change when the search wasn't working. Anyway, I'm going to close this discussion as resolved. Softlavender (talk) 04:21, 31 July 2018 (UTC)
Suggestion for an archive site run/hosted/initiated by Wikimedia
Since archival has become an integral service used by Wikipedia and other Wikimedia projects, has anyone yet considered the possibility that Wikimedia should have their own alternative/backup archival website (or integrate the feature directly into Wikipedia (seems less independent, but perhaps more convenient))? It could not only provide many/most/all of the same features as existing archival sites, but:
- would have content retention policies directly in line with the needs of Wikipedia, its community, and other Wikimedia projects,
- would be an independent back-up resource should any of the third-party archival sites go down or dramatically alter their services, and
- could help automate a lot of the existing difficulties with working with existing archival sites (e.g. it could automatically generate lists of needed dead links and provide a streamlined user-interface to help editors find and document fixed links; it could go through existing citations and automatically generate archives of currently un-archived citations; etc.).
- Probably many other benefits, especially in terms of integration with WP and other WM projects. These suggestions were just the first ones off the top of my head.
Note: I posted this suggestion to this How To's talk page because I am currently in the process of trying to figure out the correct way to mark a dead link I found, and I found the information about how to do it complex and rather scattered around, and thought "There must be a more streamlined way to do this very basic, crucial type of maintenance task." I read the notice above and decided to post this here because I believe it is relevant to the request to, "Please use this talk page to discuss issues specific to this information or how-to page". The 'How To' of Using the Wayback Machine for the purposes of updating dead links with an archive is too difficult and could use such a Wikimedia-run archival site as a long-term improvement to this process. Sorry that I'm not a frequent editor and don't have the time to find the exact right place to post this feature request. I'm really just trying to fix one dead link! 😊 Please redirect this request to the appropriate location if this is not it. Thanks! --24.57.106.253 (talk) 16:56, 11 August 2018 (UTC)
What happens when an archived page is blocked off from the Wayback?
Got an archived link or two done months ago, but it seems that the main site has exclusions done that the arcvhived links don't work anymore. Should someone revert the article URL and leave a note that the link requires a subscription to access it? Ominae (talk) 09:44, 15 February 2019 (UTC)
Wikipedia should have an Archive.today bot as well as a wayback machine bot
Archive.today *does not* use robots.txt[6] so it's more reliable for Wikipedia than wayback machine/internet archive, IA are still blocking or removing pages from archive regularly, example Windows 7 Update privacy policy: [7]
Also the Internet Archive bot also seems to be falsely labelling links as dead for some reason: [8] --109.144.209.121 (talk) 11:17, 19 February 2019 (UTC)
Removing the navigational toolbar section no longer applicable
With both @InternetArchiveBot: and @GreenC bot:'s WaybackMedic actively stripping out any flags placed after the timedate stamp, is there any point to advising editors to go to the effort of adding them in the first place? The information is good and I think the iframe flag definitely provides Wikipedia users with the best presentation for archived content, but the standard being enforced appears to offer zero flexibility for any deviation from the basic link as generated on the Wayback Machine site. Is that intentional/by consensus or should the bots be reconfigured to respect editors that follow this guideline? — ⚞ ℛogueScholar🐈 ₨🗩 ⚟ 18:28, 14 October 2019 (UTC)
JavaScript bookmarklet to save live page with outlinks?
I see there is a JavaScript bookmarklet to save a live page here, which is very useful to me; I use it often! Is there way to save a webpage with outlinks through a bookmark, or does that have to be done through web.archive.org/save itself? --MoofEMP (talk) 00:07, 8 March 2020 (UTC)