MacphersonWiki discusión:Twinkle

"WT:TW" redirects here. For other uses, see Wikipedia talk:Transwiki log, or the WikiProject Taiwan talk page.

Custom tags

When searching for tags, the user-defined ones are listed under the last regular section instead of under the "Custom tags" section, as they are without search. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:28, 24 January 2021 (UTC)

Yes. No headers are shown while searching. – SD0001 (talk) 17:35, 24 January 2021 (UTC)

I mean this. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 18:08, 24 January 2021 (UTC)

Oh, I see. That is a bug. – SD0001 (talk) 10:26, 26 January 2021 (UTC)

Pipes in RfD nominations

When I RfD'd a page via Twinkle, instances of pipes were replaced by {{subst:!}}, which breaks any templates with parameters in the nominator's rationale. I was able to confirm that this is specific to Twinkle; the preview function parses pipes correctly. It is possible that other queries in Twinkle are affected. Example diff. –LaundryPizza03 (dc̄) 01:05, 26 January 2021 (UTC)

The issue is specific to templates used inside ref tags as substitution doesn't work in them. – SD0001 (talk) 10:29, 26 January 2021 (UTC)

PROD: Prevent creation of discussion pages

Hi, I very often propose files for deletion and then it always creates {{Old prod}} on the talk page. Is there any way to add an option that prevents this/that you can turn this off? I have already created over 400 unnecessary talkpages, and for the few files that are not deleted, you can also read in the page history that the file was once suggested for deletion. --TheImaCow (talk) 06:20, 26 January 2021 (UTC)

Not to ask the impertinent question, but who cares? If the page is deleted, the talk is deleted along with it, and if the page isn't deleted, the {{old prod}} has successfully been added to the talk page to inform users of the existence of an old prod. I see no downside. Primefac (talk) 11:18, 26 January 2021 (UTC)

I care. When I want to move files to Commons, I go to Category:Unused Files and always middle-click a row of files to open them (i.e., in a new tab). The files, with which you can do nothing, or are not free, are proposed for deletion ... and if there is then in addition to the 3 other edits (notification, the actual tag, log entry) also the creation of a talk page, then it simply takes too long for me. But not only would it take too long for me, I find these "Old Prod" tags on files talks quite unnecessary in themselves. For articles with many revisions it might be helpful, but for files that only very rarely have more than 10 edits? You click once on the "History" tab and see that immediately. On the other hand, is there anyone who also looks at the file disscusion pages, if there are any? I think not. And also, I don't want to spam my edit count higher with such unnecessary edits.

Long story short: Takes too long, is unnecessary, and spams up the edits. --TheImaCow (talk) 05:21, 27 January 2021 (UTC)

But I thought the points was that Twinkle was doing it automatically - if you do nothing, it does it for you (from a "clicks" perspective, turning off a checkbox actually increases the number of clicks you make). If you're doing it manually, then I'm not sure why you're posting here. Primefac (talk) 11:56, 27 January 2021 (UTC)

Opting out of old prod tagging (if there had been such an option) won't actually reduce the total time taken. This is because Twinkle schedules things such that old prod tagging takes place at the same time as notifying the creator. Making the entry to your userspace log takes place after the creator is notified. Hence the latter two are the sort of like the rate-determining steps. – SD0001 (talk) 13:41, 27 January 2021 (UTC)

Annoying error message

Every time I load a new page on Wikipedia, I get a pink warning that says "Could not parse your twinkle preferences." Is there anything I can do to make this go away. It is getting annoying. Thanks. Scorpions13256 (talk) 20:10, 26 January 2021 (UTC)

Go to your preferences and disable Twinkle. Sorry. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:12, 26 January 2021 (UTC)

I don't want to do that because I use it for RCP. Do you have any idea what could be causing this? Scorpions13256 (talk) 20:21, 26 January 2021 (UTC)

Sorry, I was a bit sarcastic. Do you see any errors in the browser console? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:24, 26 January 2021 (UTC)

@Scorpions13256: It was likely caused by this diff. TheTVExpert (talk) 20:28, 26 January 2021 (UTC)

I just figured that out myself the second before you notified me. What a coincidence. Is there anything I can do? Scorpions13256 (talk) 20:29, 26 January 2021 (UTC)

Scorpions13256, it's likely because you're importing User:Scorpions13256/twinkleoptions.js directly in your personal script page, User:Scorpions13256/common.js. The twinkleoptions.js file is for Twinkle to use itself, you shouldn't ever import it directly. If you remove that line from your common.js, I think you can safely remove the edit Jon made. ~ Amory (u • t • c) 21:05, 26 January 2021 (UTC)

Done. Everything is back to normal. Thank you all for your help. Scorpions13256 (talk) 21:25, 26 January 2021 (UTC)

refunds to "your user page"

I wrote about this issue here. I haven't surveyed other Twinkle templates, but the language in {{Welcomeauto}} has been there a very long time. I was proposing that we write that the restoration of a deleted page would be placed in "your user space" rather than "your user page". It's a pretty small thing, but used often enough that I wanted to get some consensus before making it all by myself. — jmcgnh^{(talk) (contribs)} 08:50, 27 January 2021 (UTC)

That makes sense from my perspective. Cyphoidbomb (talk) 17:34, 27 January 2021 (UTC)

I have created block templates.

You are welcome. ThePersistentAddition (talk) 17:12, 27 January 2021 (UTC)

And they have been TFD'd. I recommend consensus before you create a block template, suggest in the village pump. Aasim (talk) 09:32, 1 February 2021 (UTC)

Feature request

Hey you hard-working volunteers, thanks for Twinkle!

Had a feature request: Is it possible when using the Twinkle > Warn > search field, for the search feature to look through all templates by default and find the one you need? Currently, if you're looking for the COI template (random example), you have to either know to search through the single-issue notices page, or scroll all the way to All warning templates and run the search on that. Seems to me that a search tool should search everything. Thanks for your hard work! Cyphoidbomb (talk) 17:33, 27 January 2021 (UTC)

A workaround would be to configure "all templates" as the default group at Wikipedia:Twinkle/Preferences#warn. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 17:43, 27 January 2021 (UTC)

Just tried it. The downside there is that the layout of templates that I've become accustomed to over the years has changed, and the neat headings have disappeared as well. Cyphoidbomb (talk) 17:53, 27 January 2021 (UTC)

Cyphoidbomb, this should now be live, thanks to TheTVExpert! ~ Amory (u • t • c) 16:15, 31 January 2021 (UTC)

Cool, thanks TheTVExpert! Is this something I have to turn on? It doesn't seem to work for me just yet. Cyphoidbomb (talk) 17:05, 31 January 2021 (UTC)

Sorry, Cyphoidbomb, I meant that the group of "All templates" should now show the headers in the order expected. If you set that to your default, you can search for any template but still also see the headings you wanted. ~ Amory (u • t • c) 17:58, 31 January 2021 (UTC)

Amory I now see the change, although I was getting used to having L4 be my default warning. Curses! I appreciate the adjustment. That said, I still think the search field should encompass all standard warnings/notices, but perhaps an argument for another time. Regards to all, Cyphoidbomb (talk) 02:22, 2 February 2021 (UTC)

I hear ya, but counterpoint: someone who wants to give a level 3 warning and doesn't want their search results polluted with other options outside the level they've already selected. That's why the menu option with every template was created, for the broad search. ~ Amory (u • t • c) 12:22, 2 February 2021 (UTC)

Notifying deceased users

As per this, could it be implemented that users with {{deceased}} on their talk page don't get notified of a nomination? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 13:06, 28 January 2021 (UTC)

It would probably be better for Twinkle to obey some kind of Category:Wikipedians who opt out of message delivery or similar, and deceased editors to have that placed on their page (or {{deceased}} to include it), rather than Twinkle accounting for particular templates directly. ProcrastinatingReader (talk) 13:09, 28 January 2021 (UTC)

@ProcrastinatingReader: So, should we create a separate category like Category:Wikipedians who opt out of Twinkle notifications? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:45, 9 February 2021 (UTC)

Category:Wikipedians who opt out of message delivery has 3,954 pages built up over years. It might be better to just use that. ProcrastinatingReader (talk) 16:48, 9 February 2021 (UTC)

I thought about that, but Twinkle notifications are quite different, as they concern a specific user (the page creator) rather than all users at once. I am thinking about opting out of message delivery, but would rather not opt out of XfD notifications. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:51, 9 February 2021 (UTC)

I've got something in the works that will allow for this, and was planning on using categories rather than templates. Things like {{deceased}} and {{retired}} put/can put folks into Category:Wikipedians who opt out of message delivery, so that'd be a reasonable thing to piggy-back on/two-birds-one-stone kinda thing. I'd be inclined to say a separate category wouldn't be ideal. ~ Amory (u • t • c) 15:53, 10 February 2021 (UTC)

Twinkle messages are directed to a single user whereas that category is for mass messages (not targeted to a specific user). Quite different. Plus, we should support the ability to turn off messages from specific modules only. This is a better done via a template using hidden external links (similar to {{no talkback}}), so that they can be efficiently queried without needing to have multiple templates or categories. – SD0001 (talk) 16:45, 10 February 2021 (UTC)

Except of course for the examples I just gave. I'm fine with using a dedicated template (I've got both written atm) but it won't avoid having multiples. It would enable limiting specific modules, so that'd be a cool feature; hadn't thought of that. ~ Amory (u • t • c) 17:07, 10 February 2021 (UTC)

Not sure what you mean. The template could be included in those other templates. If we're fine with having multiples, then it deosn't matter if they're temlpates or categories. But the beauty of the external link trick is that we could aim for a single template: {{no twinkle}} (disable all) --> gives notwinkle.com?modules=csd|prod|xfd, {{no twinkle|csd}} (disable just csd) --> notwinkle.com?modules=csd. Then query prop=extlinks for notwinkle.com and parse the module list. – SD0001 (talk) 20:10, 10 February 2021 (UTC)

Yes, I'm agreeing with you on that. I was saying that to only use that would mean the presumptuous editing of retired or deceased users' talkpages. Both can exist, yes, but both have to exist. At any rate, more when PR. ~ Amory (u • t • c) 21:30, 10 February 2021 (UTC)

Worth noting {{deceased}} / {{retired}} are usually placed on user pages, rather than user talk pages which are usually what contain Category:Wikipedians who opt out of message delivery. So it'll have to check user pages too, probably. ProcrastinatingReader (talk) 00:05, 14 February 2021 (UTC)

Note to see steps for multiple/bundled XFD discussions

Twinkle doesn't seem support creating bundled XFD discussions, but doesn't indicate that on the XFD interface, would it be worth adding a notice like ("If nominating multiple Xs for the same discussion see WP:MULTIAFD/WP:TFDHOWTO/WP:RFDHOWTO/etc.") At User_talk:GenQuest#Lanka_Premier_League_AfDs the nominator evidently thought that this was possible, which led to duplication, busywork, and breaking the XFDCloser script. ---- Patar knight - ^chat/_{contributions} 17:43, 28 January 2021 (UTC)

I really appreciate many of Twinkle's wonderful features, but multi-XfD (and multi-RM) is the enhancement I'd most like to see. I know it wouldn't be easy. Certes (talk) 19:04, 28 January 2021 (UTC)

Uncontroversial RMs

Twinkle failed to create an RM/TR nomination on Foreign involvement in the Syrian Civil War with the error "Adding entry at WP:RM/TR: failed to find target spot for the entry". 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:09, 29 January 2021 (UTC)

@1234qwer1234qwer4: This edit may have fixed the problem. Can you try it again? -- John of Reading (talk) 19:21, 29 January 2021 (UTC)

Thanks, that was it. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:29, 29 January 2021 (UTC)

Don't display [rollback (AGF)] || [rollback] || [vandalism] buttons on the latest version of the diff page if there is only one contributor to the page

1. Go to special:diff/1001178118.
2. Click [Rollback] button.
3. When the Twinkle rollback, it will display the following text:

Grabbing data of earlier revisions: No previous revision found. Perhaps IN is the only contributor, or that the user has made more than 50 edits in a row.

I think that isn't necessary. That can be done by controlling the source - that is, do not show [rollback (AGF)] || [rollback] || [vandalism] button. By the way, did you know? Alcremie's 1000th edit was made very close to the 20th anniversary day of Wikipedia. 15:33, 30 January 2021 (UTC)

As above, this would be fairly unwieldy and slow things down. I suppose it'd be less apparent on diffs, but it would delay things loading. ~ Amory (u • t • c) 01:30, 1 February 2021 (UTC)

January 2021 Twinkle updates (2021-01-31)

A number of more minor improvements this time around. Most notably, most watchlist defaults have been changed to take advantage of expiring watchlist behavior. A number of bugs have been fixed; a brief summary of some of the more notable items are below. Changes not otherwise attributed were made by User:Amorymeltzer.

• Watchlist behavior:
  • Set most watchlist defaults to 1 month expiry (#1249)
• All windows: add link to Twinkle talk page (#1212, by TheTVExpert)
• tag:
  • Hide subheadings on quick filter (#1288, by TheTVExpert)
  • Fix rcat matching when 1= is explicitly used (#1246)
• warn:
  • Add headers for "All Warning" template group (#1290, by TheTVExpert)
  • move {{uw-agf-sock}} from singlewarn to singlenotice (#1265)
• arv: Add a blank newline after UAA entries (#1263)
• revert and rollback: Change 'Reverted to revision' edit summary to 'Restored revision' (#1271)
• speedy: Remove T3 (#1217)
• shared: Add preview (#1275, by TheTVExpert)
• block:
  • Adjust default expiry for copyright blocks to be indefinite for registered users (#1278, by ToBeFree)
  • AP2 amended to post-1992 (#1284)
• unlink:
  • Link the listed pages (#1254)
  • Properly show what will happen to all links (#1248)
• unlink/batch: Sort lists of pages by namespace then title (#1251)
• batch:
  • Show arrow links for batchprotect and batchundelete (#1254)
  • Show image uploader/editor info, like batch delete (#1253)
• welcome: Fix welcome-short parameter syntax (#1269, by TheTVExpert)
• prefs: fix typo: proteting -> protecting (#1285, by The Earwig)
• morebits:
  • Fix handling of circular redirect page load (#1274)
  • lookupCreation: fix bug from JSON conversion (by SD0001)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. There were a lot of changes behind the scenes, so feel free to ping me. As always, input is welcome at the GitHub repo as well. Finally, if you're interested in helping out with Twinkle development, there's a helpful guideline for new contributors — check it out! ~ Amory (u • t • c) 16:12, 31 January 2021 (UTC)

@Amorymeltzer would you mind adding the most important bits to the next issue of Scripts++ if you have time? I missed this for the January issue unfortunately DannyS712 (talk) 01:57, 3 February 2021 (UTC)

​It's actually on my todo list whenever I make this post, but I didn't think anything here was really worth mentioning this time around. In hindsight, maybe the watchlist behavior would have been good to include? ~ Amory (u • t • c) 12:15, 3 February 2021 (UTC)

Yeah, thats what I was thinking, as well as possibly the copyright block default expiry, the preview in shared, and the revert and rollback summary change DannyS712 (talk) 13:55, 3 February 2021 (UTC)

 Done ~ Amory (u • t • c) 12:44, 13 February 2021 (UTC)

Nomination for deletion of Template:Uw-ttraidblock

Template:Uw-ttraidblock has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Aasim (talk) 02:05, 1 February 2021 (UTC)

Nomination for deletion of Template:Uw-ewpovblock

Template:Uw-ewpovblock has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Aasim (talk) 02:08, 1 February 2021 (UTC)

TfD problem

This has been on my mind for some time, but can Twinkle stop inserting an extra line when nominating a template for TfD? See e.g. this, this, or this for what I'm talking about.

That is, rather than

{{Tfm/dated|...}}
ORIGINAL TEMPLATE CONTENT

can it be

{{Tfm/dated|...}}ORIGINAL TEMPLATE CONTENT

or perhaps

{{Tfm/dated|...}}<!--
-->ORIGINAL TEMPLATE CONTENT

(provided the bot or script used to remove the banner could correctly remove <!-- --> as well)?

The line break could be particularly disruptive e.g. when the template is used inside <ol>...</ol> made by #. I assume the same applies to other types of banners such as SD, in which case </noinclude> should be immediately followed by the first character of the template content without a line break. Nardog (talk) 12:35, 2 February 2021 (UTC)

Many templates start with {| which must be at the start of a line. Otherwise the whole table code is displayed instead of rendering the table. There is also other code which must be at the start of a line. In some cases it is produced by transcluding another template so it may be hard to detect for Twinkle. Always omitting a newline would do more damage than always including it. Wikipedia:Templates for discussion#Listing a template says: "If the template nominated is inline, do not add a newline between the Tfd notice and the code of the template." The newline is the default recommendation. PrimeHunter (talk) 12:57, 2 February 2021 (UTC)

Twinkle tries to be smart: if it detects p .Inline-Template it defaults to inline (and likewise .infobox' for infobox). Perhaps some additional clarification on the meaning of the menu options would be helpful? ~ Amory (u • t • c) 13:10, 2 February 2021 (UTC)

Ah, that's true. Clarification sure could help, but I think a separate checkbox would be even better (e.g. "Suppress line break after tag (recommended for inline)"). I also wonder why |type=disabled isn't available in the dropdown; I submit that it should be. Nardog (talk) 13:31, 2 February 2021 (UTC)

@Nardog and PrimeHunter: For TfDs twinkle offers a "deletion tag display style" option. If set to "standard" or "sidebar/infobox", a newline is added. If set to "inline template" or "tiny inline", no newline is added. This option usually has to be selected by nominator, but is auto-set in cases mentioned by Amorymeltzer. – SD0001 (talk) 13:30, 2 February 2021 (UTC)

FFD notices

Are there plans in the works for Twinkle to add optional FFD notices to either the talk pages where files are used or to captions (where applicable). This is the optional part of the WP:FFD Instructions, Step 3. Give due notice. The documentation suggests that there are no extra FFD options to handle this. -2pou (talk) 22:12, 8 February 2021 (UTC)

Nomination for merging of Template:R from template shortcut

Template:R from template shortcut has been nominated for merging with Template:R from shortcut. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Aasim (talk) 10:12, 9 February 2021 (UTC)

IP user notification

When I realised I created an XfD notification at User talk:203.143.10.132 for a user whose last contributions were in 2005, I was quite amused; however, a regular Wikipedia reader might now be confused rather than amused. I think Twinkle should notify IPs whose last contributions were more than half a year ago. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:53, 9 February 2021 (UTC)

Update to Twinkle menu — Devs read here

This is for folks from other projects who maintain their local forks of Twinkle who may be bullets on their Vector menus today. Similar to last June, things were changed a bit. The fix (see PR and diff) is to simply add the mw-portlet class to the constructed menu's outer class. ~ Amory (u • t • c) 18:50, 9 February 2021 (UTC)

Nomination for deletion of Template:Expert needed

Template:Expert needed has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Ten Pound Hammer • ^{(What did I screw up now?)} 22:27, 9 February 2021 (UTC)

• As noted in the TfD, "Template:Example" seems to be a bug in Twinkle. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 22:32, 9 February 2021 (UTC)
  • @TenPoundHammer: Unrelated to the TfD, but what happened to get the "Template:Example" do you know? Do you remember what the steps were when you nominated the page? ~ Amory (u • t • c) 11:01, 10 February 2021 (UTC)
    • @Amorymeltzer: I don't know. I just did it like any other Twinkle nomination, and it did this. I think it's because the template is fully protected that Twinkle spazzed out. Ten Pound Hammer • ^{(What did I screw up now?)} 23:00, 10 February 2021 (UTC)
      • Twinkle should be able to handle that, though, so I'm curious how it ended up happening. ~ Amory (u • t • c) 18:56, 11 February 2021 (UTC)

BLPPROD tagging should not add Old prod template to talk pages

Twinkle currently appears to add the {{Old prod}} template to talk pages when an article is tagged as BLPPROD. However, this is incorrect behaviour, per WP:BLPPROD: "a prior declined BLPPROD nomination does not block an article from being nominated for standard PROD and vice versa." --Paul_012 (talk) 12:57, 10 February 2021 (UTC)

I still think the template is valuable to have, for showing talkpage readers the history of the page. I don't think Twinkle should be changed. UnitedStatesian (talk) 13:13, 10 February 2021 (UTC)

@UnitedStatesian: The solution would be a different template. I'm with Paul 012, it's confusing to have a template whose primary purpose is to remind users that a page is now PROD-ineligible when that is not the case. davidwr/(talk)/(contribs) 13:50, 10 February 2021 (UTC)

Change to wording of Template:Undisclosed_paid with language saying that the payer may not be the subject of the article

Per the instructions at Template:Twinkle_standard_installation:

If you plan to make breaking changes to this template, move it, or nominate it for deletion, please notify Twinkle's users and maintainers at Wikipedia talk:Twinkle as a courtesy, as this template is used in the standard installation of Twinkle. Thank you!

The change to Template:Undisclosed_paid is the addition of the sentence:

The payer may have been the subject of the article, or a competitor, rival, associate, independent entity, etc.

So that it looks like:

Further discussion could be at Template_talk:Undisclosed_paid#Proposal_to_add_language_to_the_template....

Jjjjjjjjjj (talk) 04:08, 12 February 2021 (UTC)

Twinkle XFD redirect template bug

When nominating a redirect page for deletion, twinkle adds the Template:afd1 to the page the redirect page links to.Manabimasu (talk) 04:55, 14 February 2021 (UTC)

@Manabimasu: I believe you're referring to Wikipedia:Articles for deletion/Regressive conservatism? From what I can tell, you selected the AfD option on the Regressive conservatism redirect, when you wanted to select Redirects for discussion. Is that right? I can clean up the AfD if you like, but I think that's what happened. ~ Amory (u • t • c) 16:05, 14 February 2021 (UTC)

​ thanks for the info. You can clean it up.Manabimasu (talk) 22:09, 14 February 2021 (UTC)

 Done See Wikipedia:Redirects for discussion/Log/2021 February 14#Regressive conservatism ~ Amory (u • t • c) 22:31, 14 February 2021 (UTC)