710:
391:
687:
740:
352:
48:
590:
All "good" 'copy-pasted URL will be HTTPS from now on', but that wasn't my example. An editor who copied from "://www.foo.com" by accident, might just type in http at the beginning of that URL, vs. going back and re-copy/pasting. And that still doesn't address stuff pulled from history and the like.
488:
I support this proposal. In addition to the 50 edit trial I'll throw out another possibility but ignore if other bot experts think this is overkill. Given the large number of affected references (approximately 100,000), I think it would be wise to run it for 1000 or so and then pause for couple days
374:
I don't have an accurate number, but I would guess as of today about 70-80% of the links would be re-routed to HTTP on the NYT server. This number will gradually go to zero over the next couple of months. (By the way, the example link above already works with HTTPS on mobile; desktop will follow
557:
Clear-cut and helpful. My only feedback would be to change this from a one-time run to a large initial run, and then periodically after, as there will certainly be non-https links re-introduced by editors, either due to bad copy/pastes or restoring stuff from page history, etc.
336:
We have a lot of NYT links (my conservative guess is 100k pages), and while the NYT announcement says so far only "articles published in 2014 and later" are HTTPS accessible, I want to convert them all right now for two reasons: (1) it does not break older links
341:), only redirect to HTTP again; but if NYT does that on their site, at least they keep the HTTP Referrer information. And (2) as they announced they "intend to bring the rest of our site under the HTTPS umbrella", so it's only a matter of time.
512:
Generally when approving massive jobs like this I do it with a ramp-up throttle (e.g. 1000 edits, 24 hr wait, 2000 edits, 24 hour wait) with increasing large steps depending on the max size (last step is "open"). —
771:
Should there be any minor issues brought up during the ramp up that are easily correctable, make corrections and restart the ramp up schedule. You may certainly use a slower ramp up schedule at your discretion. —
358:
Here is a trial approval to test your code, do you have any statistics as to how many of the links you will change will end up being currently useless due to the remote server changing them back to http? —
434:
I have no problem with this and it's a great idea and thanks for BB for doing this important work. My question is why not run the bot for multiple sites? It would reduce the number of edits if : -->
811:
316:
255:
248:
21:
88:
717:
398:
83:
691:
Approved for extended trial (1000 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
576:
I don't think that will be necessary, since nytimes.com is now HTTPS-by-default, so all copy-pasted URL will be HTTPS from now on. --
338:
153:
118:
418:
312:
141:
103:
356:
Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
641:
778:
729:
699:
678:
646:
614:
600:
585:
567:
543:
519:
500:
476:
450:
427:
410:
384:
365:
165:
98:
93:
443:
78:
793:
40:
594:
561:
159:
330:
147:
538:
495:
467:
and others in the same bot run? I figured it would be more organized if I do one domain at a time. --
208:
725:
610:
581:
472:
436:
406:
380:
135:
59:
304:
673:
325:
636:
17:
592:
559:
533:
507:
490:
721:
661:
606:
577:
468:
464:
402:
376:
315:, conveniently listing all major news outlets that enable HTTPS access. Having already
238:
130:
686:
660:
is important for the privacy and security of our readers. Thank you for the good work
805:
773:
694:
665:
514:
422:
360:
276:
631:
217:
605:
I don't think there will be more than a few cases. I'll keep an eye on it. --
460:
417:
Due to the massive size of this request, I have posted a link in from
259:
Should we convert existing Google and
Internet Archive links to HTTPS?
657:
630:
I can't find any issues with this proposal, overall net positive.
786:
The above discussion is preserved as an archive of the debate.
308:
252:
Why we should convert external links to HTTPS wherever possible
792:
To request review of this BRFA, please start a new section at
591:
But, that's your call to make. I still support it either way.
195:
39:
To request review of this BRFA, please start a new section at
323:, I want to work through that list one by one, starting with
421:. Placing on hold for any initial community comments. —
183:
177:
171:
113:
108:
73:
812:Approved Knowledge (XXG) bot requests for approval
246:Links to relevant discussions (where appropriate):
33:The following discussion is an archived debate.
8:
489:just to see if something odd has happened.--
459:So you're saying I should also convert, say
435:1 site could be processed at once. --
333:their activation of HTTPS a week ago.
746:Task approved with ramp up schedule:
7:
270:Estimated number of pages affected:
28:
202:Automatic, Supervised, or Manual:
194:01:06, Friday, January 20, 2017 (
45:The result of the discussion was
738:
708:
685:
389:
350:
46:
313:Freedom of the Press Foundation
693:Please update with results. —
1:
779:16:32, 3 February 2017 (UTC)
730:06:44, 31 January 2017 (UTC)
700:20:11, 30 January 2017 (UTC)
679:05:31, 29 January 2017 (UTC)
647:04:19, 27 January 2017 (UTC)
615:19:48, 28 January 2017 (UTC)
601:02:57, 27 January 2017 (UTC)
586:23:37, 26 January 2017 (UTC)
568:22:26, 26 January 2017 (UTC)
544:01:05, 27 January 2017 (UTC)
520:00:00, 27 January 2017 (UTC)
501:20:58, 26 January 2017 (UTC)
477:22:14, 26 January 2017 (UTC)
451:17:57, 26 January 2017 (UTC)
428:17:20, 26 January 2017 (UTC)
411:16:21, 21 January 2017 (UTC)
385:12:07, 21 January 2017 (UTC)
366:05:09, 21 January 2017 (UTC)
828:
656:I don't see any problems.
751:(already completed above)
599:@ 02:57, 29 Tevet 5777 /
566:@ 22:26, 28 Tevet 5777 /
789:Please do not modify it.
36:Please do not modify it.
397:Edit history obviously
307:recently pointed me at
532:Sounds good. Thanks.--
290:Already has a bot flag
761:5000 edits, 24hr hold
758:3000 edits, 24hr hold
755:2000 edits, 24hr hold
749:1000 edit, 24hr hold
22:Requests for approval
209:Programming language
18:Knowledge (XXG):Bots
716:Edit history again
311:, a project of the
277:Exclusion compliant
326:The New York Times
226:Function overview:
331:proudly announced
302:Function details:
819:
791:
776:
742:
741:
712:
711:
697:
689:
676:
644:
639:
634:
541:
536:
517:
511:
498:
493:
448:
441:
425:
393:
392:
363:
354:
353:
235:
231:
188:
187:
60:Bender the Bot 7
50:
49:
38:
827:
826:
822:
821:
820:
818:
817:
816:
802:
801:
800:
787:
774:
739:
714:Trial complete.
709:
695:
674:
642:
637:
632:
597:
564:
539:
534:
515:
505:
496:
491:
444:
437:
423:
395:Trial complete.
390:
361:
351:
347:
309:Secure The News
264:Edit period(s):
233:
229:
133:
129:
124:
63:
47:
34:
26:
25:
24:
12:
11:
5:
825:
823:
815:
814:
804:
803:
799:
798:
782:
781:
768:
767:
766:
765:
762:
759:
756:
753:
735:
734:
733:
732:
703:
702:
682:
681:
650:
649:
624:
623:
622:
621:
620:
619:
618:
617:
595:
571:
570:
562:
551:
550:
549:
548:
547:
546:
525:
524:
523:
522:
482:
481:
480:
479:
454:
453:
431:
430:
415:
414:
413:
387:
369:
368:
346:
343:
272:about 100,000
239:New York Times
123:
122:
116:
111:
106:
101:
96:
91:
86:
81:
76:
74:Approved BRFAs
71:
64:
62:
57:
56:
55:
29:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
824:
813:
810:
809:
807:
797:
795:
790:
784:
783:
780:
777:
770:
769:
764:Open editing.
763:
760:
757:
754:
752:
748:
747:
745:
737:
736:
731:
727:
723:
719:
715:
707:
706:
705:
704:
701:
698:
692:
688:
684:
683:
680:
677:
672:
669:
668:
663:
659:
655:
652:
651:
648:
645:
640:
635:
629:
626:
625:
616:
612:
608:
604:
603:
602:
598:
593:
589:
588:
587:
583:
579:
575:
574:
573:
572:
569:
565:
560:
556:
553:
552:
545:
542:
537:
531:
530:
529:
528:
527:
526:
521:
518:
509:
504:
503:
502:
499:
494:
487:
484:
483:
478:
474:
470:
466:
462:
458:
457:
456:
455:
452:
449:
447:
442:
440:
433:
432:
429:
426:
420:
416:
412:
408:
404:
400:
396:
388:
386:
382:
378:
373:
372:
371:
370:
367:
364:
357:
349:
348:
344:
342:
340:
334:
332:
328:
327:
322:
321:links earlier
320:
314:
310:
306:
303:
299:
297:
294:
291:
287:
285:
282:
279:
278:
273:
271:
267:
266:one-time run
265:
261:
260:
258:
253:
251:
247:
243:
241:
240:
227:
223:
222:upon request
221:
219:
214:
212:
210:
205:
203:
199:
197:
193:
189:
185:
182:
179:
176:
173:
170:
167:
164:
161:
158:
155:
152:
149:
146:
143:
140:
137:
132:
128:
120:
117:
115:
112:
110:
107:
105:
102:
100:
97:
95:
92:
90:
87:
85:
82:
80:
77:
75:
72:
70:
66:
65:
61:
58:
53:
44:
42:
37:
31:
30:
23:
19:
788:
785:
750:
743:
713:
690:
670:
666:
653:
627:
554:
485:
445:
438:
394:
355:
335:
324:
319:The Guardian
318:
301:
300:
295:
292:
289:
288:
283:
280:
275:
274:
269:
268:
263:
262:
256:
249:
245:
244:
237:
225:
224:
216:
215:
207:
206:
201:
200:
191:
190:
180:
174:
168:
162:
156:
150:
144:
138:
126:
125:
68:
51:
35:
32:
638:Consermonor
535:S Philbrick
492:S Philbrick
339:for example
218:Source code
192:Time filed:
508:Sphilbrick
345:Discussion
317:converted
220:available:
204:Automatic
184:ANI search
178:rights log
166:page moves
154:edit count
114:rights log
104:page moves
744:Approved.
722:bender235
662:bender235
643:Opus meum
607:bender235
578:bender235
469:bender235
465:Bloomberg
403:bender235
377:bender235
375:soon.) --
172:block log
131:Bender235
127:Operator:
109:block log
806:Category
775:xaosflux
696:xaosflux
667:Tony Tan
516:xaosflux
461:Techdirt
424:xaosflux
362:xaosflux
293:(Yes/No)
281:(Yes/No)
242:domain.
236:for the
234:https://
228:replace
142:contribs
84:contribs
52:Approved
20: |
794:WT:BRFA
654:Support
633:Iazyges
628:Support
596:ennasis
563:ennasis
555:Support
486:Support
305:Bgwhite
230:http://
41:WT:BRFA
540:(Talk)
497:(Talk)
419:WP:VPR
658:HTTPS
439:Green
232:with
89:count
16:<
726:talk
720:. --
718:here
675:talk
611:talk
582:talk
473:talk
463:and
407:talk
401:. --
399:here
381:talk
329:who
298:Yes
286:Yes
257:WPR:
254:and
250:WPR:
213:AWB
211:(s):
160:logs
136:talk
119:flag
99:logs
79:talk
69:BRFA
196:UTC
148:SUL
94:SUL
808::
728:)
664:!
613:)
584:)
475:)
409:)
383:)
198:)
796:.
724:(
671:·
609:(
580:(
510::
506:@
471:(
446:C
405:(
379:(
337:(
296::
284::
186:)
181:·
175:·
169:·
163:·
157:·
151:·
145:·
139:·
134:(
121:)
67:(
54:.
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.