Wikipedia talk:Bots/Requests for approval/Bender the Bot 2
Latest comment: 8 years ago by Xaosflux in topic Ramp up reset
Initial discussion
edit- This overlaps the work being done by User:Green Cardamom/WaybackMedic 2 (fix #2). It's about a week from final approval. -- GreenC 20:57, 20 August 2016 (UTC)
- Oh, I forgot. So I guess it doesn't need two bots fixing the same issue, right? --bender235 (talk) 21:20, 20 August 2016 (UTC)
- Well, I suppose over time it will need an occasional refresh. You could ask for an open-ended period. WM2 is a heavy resource consuming program due to its nature so I probably won't run it that often after it completes this run. -- GreenC 22:30, 20 August 2016 (UTC)
- That won't be necessary. Since 2013, if you access the Wayback Machine main page through HTTP it redirects you to HTTPS automatically. That means everyone adding an "archive-url" ever since 2013 should have added an HTTPS link anyways. All that's left are the "legacy links" added before 2013. Once these are fixed, the HTTPS transition is complete.
I think what I'll do instead is start fixing the Google Books links. Should I modify this RfA or close it and open a new one? --bender235 (talk) 22:47, 20 August 2016 (UTC)
- Yeah that's true. I don't know re: close versus mod .. maybe mod to retain the #2 project name. If you want to delete this thread I don't care. -- GreenC 00:34, 21 August 2016 (UTC)
- That won't be necessary. Since 2013, if you access the Wayback Machine main page through HTTP it redirects you to HTTPS automatically. That means everyone adding an "archive-url" ever since 2013 should have added an HTTPS link anyways. All that's left are the "legacy links" added before 2013. Once these are fixed, the HTTPS transition is complete.
- As this never went to trial, just move the discussion above to the talk page with a note, and rewrite your header. — xaosflux Talk 02:02, 21 August 2016 (UTC)
Ramp up reset
editDue to some initial issues, the step wise ramp up was reset, please see Special:Permalink/741448069#The_problem. — xaosflux Talk 15:30, 27 September 2016 (UTC)