Wikisource

Wikisource:Administrators' noticeboard/Archives/2022

< Wikisource:Administrators' noticeboard‎ | Archives
Warning Please do not post any new comments on this page.
This is a discussion archive first created in , although the comments contained were likely posted before and after this date.
See current discussion or the archives index.

Interface Admin for Xover

The following discussion is closed:

now in line with annual confirmation Beeswaxcandle (talk) 01:27, 11 March 2022 (UTC)

@BD2412, @Beeswaxcandle: Ok, I finally got tired of pestering Inductiveload for every little JS/CSS bit that needs doing, so I bit the bullet and enabled 2FA for my account (which the `crats are somehow supposed to check, but have no technical facility to actually do). I'd like Interface Admin rights added to take care of random needed changes to .js and .css in MediaWiki:-space (most immediately, fixing MediaWiki:Gadget-addsection-plus.js which got borked in the latest MW release). --Xover (talk) 19:24, 20 October 2021 (UTC)

@Xover: Granted for 1 month. Seek Community support for ongoing access to the right in that time and we'll can make it a longer period to bring into line with your annual reconfirmation. Beeswaxcandle (talk) 22:21, 20 October 2021 (UTC)
Thanks, and will do. Xover (talk) 07:21, 21 October 2021 (UTC)
  Support knows where their towel is and will be nice to have some company in the CSS mines. Inductiveload—talk/contribs 22:23, 20 October 2021 (UTC)
  Support Great user and has my trust. Languageseeker (talk) 22:27, 20 October 2021 (UTC)
  Support PseudoSkull (talk) 23:32, 20 October 2021 (UTC)
This is all very well, but the AN is not appropriate place to seek community support as not all members of the community are regularly here. Open a conversation at WS:ADMINS. Beeswaxcandle (talk) 01:25, 21 October 2021 (UTC)
At this point, I don't know that it makes sense to observe the formality of a separate discussion. I would not expect the outcome to vary. BD2412 T 02:21, 22 October 2021 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 01:52, 11 March 2022 (UTC)

Spamming as a block reason

The following discussion is closed:

was taken to Wikisource:Scriptorium/Archives/2021-09#Blocking policy regarding spammers for wider discussion Beeswaxcandle (talk) 01:33, 11 March 2022 (UTC)

We don't actually mention spam/promoting external linking as a blocking reason at Wikisource:Blocking_policy. Should we? I am extremely unsympathetic to it (i.e. an indef block is completely reasonable in my mind, because they users are clearly not interested in productive contributions), but I also don't want to act against policy. Inductiveload—talk/contribs 07:51, 21 September 2021 (UTC)

  • Support, it should be mentioned there so that the policy was in accordance with the practice. --Jan Kameníček (talk) 08:58, 21 September 2021 (UTC)
  • It depends on the type of spam. If it's bot-spam, then instant indefinite block. If the spam and the user name are linked, then it's a spam-only account and also gets indef'd. If it's an apparently real human who has linked their user page to something spam-ish, then I tend to remove the spam and use the {{spam}} template on their talk page and not block, at least initially. If it continues to be added, then a short block. The majority of what I've seen in the last few months comes into the earlier categories. Beeswaxcandle (talk) 09:55, 21 September 2021 (UTC)
  • I classify spam as vandalism. HARD SPAM block, includes machine-generated / bot spam which has zero place here and those accounts should be totally infinitely blocked. Real person-generated spam has a broader range, and as BWC says there can be a range of responses, from HARD SPAM blocks, and SOFT SPAM deletion and warnings, etc. If you can capture that into some words, then go for it. I don't block talk pages typically so they can always appeal a block, knowing that spambot-generated won't appeal, and is usually main or user: ns, though very occasionally user talk: ns. So if we mention we need wriggle room for the admin in use of the tool, and definitely allow real users to appeal on their user page (maybe mention {{unblock}}). — billinghurst sDrewth 08:49, 26 September 2021 (UTC)
  • I support having this as a reason to block. Having the basis in policy does not always need to result in its implementation, if another solution is available. BD2412 T 07:05, 27 September 2021 (UTC)
  • I agree with what others have said. Spam that requires a block is already covered under things like Vandalism and Bots, and the rare spam that isn't covered this way should be handled more gently. That being said, WS:BP also supports this perspective ("polite communication with the user should be the first action, and blocking a last resort"), and it would not hurt to clearly identify Spam in our policy, whether as part of our definition of Vandalism or as its own heading. —Beleg Tâl (talk) 13:59, 27 September 2021 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 01:51, 11 March 2022 (UTC)

Abuse filter false positive

The following discussion is closed.

This is a private filter so I won't describe it in detail, but on my en.wp talk page I had a complaint from Andrzejbanas that the abuse filter had blocked them for reporting harassment of them. The log is here: Special:AbuseLog/145862.

Is this part of the filter still needed or could it be relaxed? BethNaught (talk) 10:18, 3 January 2022 (UTC)

@BethNaught (CC Andrzejbanas): This filter was triggering on a slightly too generic string that it is probable that innocent users would be caught by, as demonstrated by the current case. I've removed the relevant condition so this should now hopefully no longer happen, and my apologies that you got caught up in it. I have also applied indef semi-protection on your user and user talk page. Feel free to ask for its removal here if you should ever become active on enWS (or for whatever other reason). Xover (talk) 10:58, 3 January 2022 (UTC)
Haha. Totally fine, i was curious what I did that might have done that. Thanks for setting it up. Andrzejbanas (talk) 18:32, 3 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:01, 11 March 2022 (UTC)

Edit request for protected page

The following discussion is closed.

I'd like to request an edit on Shaving Made Easy/Chapter 14, to transition it to transclude using the <pages /> tag rather than the {{page}} template. Since it's protected, I'm making the request here. The content I'd like the page to have is 

{{header
 | title      = [[../]]
 | author     = 
 | translator = 
 | section    = Chapter XIV.
 | previous   = [[../Chapter 13|Chapter XIII.]]
 | next       = [[../Chapter 15|Chapter XV.]]
 | notes      = 
}}

<div class="pagetext" style="text-indent:1em;">
<pages index="Shaving Made Easy 1905.djvu" include=65 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=66 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=67 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=68 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=69 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=70 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=71 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=72 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=73 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=74 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=75 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=76 />
{{page break|label=}}
<pages index="Shaving Made Easy 1905.djvu" include=77 />
</div>

Thank you! —CalendulaAsteraceae (talk • contribs) 04:11, 17 January 2022 (UTC)

@CalendulaAsteraceae:   Done Xover (talk) 07:38, 17 January 2022 (UTC)
Thank you! —CalendulaAsteraceae (talk • contribs) 07:40, 17 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:01, 11 March 2022 (UTC)

Move request Wittgenstein

The following discussion is closed.

About 200 pages from Index:Wittengenstein - Tractatus Logico-Philosophicus, 1922.djvu need to be moved to Index:Wittgenstein - Tractatus Logico-Philosophicus, 1922.djvu. Greetings Bigbossfarin (talk) 14:16, 19 January 2022 (UTC)

  Done, and the transclusion at Tractatus Logico-Philosophicus also updated. Inductiveload—talk/contribs 15:02, 19 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:04, 11 March 2022 (UTC)

74.75.9.45

The following discussion is closed.

Please block this user—vandalism. TE(æ)A,ea. (talk) 21:02, 19 January 2022 (UTC)

  Done Inductiveload—talk/contribs 21:12, 19 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:05, 11 March 2022 (UTC)

Index:The Black Cat v06no11 (1901-08).pdf

The following discussion is closed.

Please, delete the not needed redirect. The index has been moved in order to use higher resolution djvu version. Ankry (talk) 22:40, 22 January 2022 (UTC)

@Ankry:   Done. The {{sdelete}} template can be used too. --Jan Kameníček (talk) 23:56, 22 January 2022 (UTC)
Unfortunately it can't. The redirect could not be edited due to a MediaWiki error :( Ankry (talk) 01:48, 23 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:14, 11 March 2022 (UTC)

autopatrolled for User:廣九直通車

The following discussion is closed.

I would like to nominate 廣九直通車 (talk • contribs) autopatrolled permission. I have validated a number of his texts and he seems to have a good grasp of formatting and policy. Serprinss (talk) 06:18, 27 January 2022 (UTC)

  Done. Agree, the user understands how to edit in various namespaces and demonstrated understanding of our policies. --Jan Kameníček (talk) 11:08, 27 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:07, 11 March 2022 (UTC)

Autopatroller and move

The following discussion is closed.

Hi, Can I get the Autopatroller and move rights? I am a former admin. My rights were removed because of inactivity. Thanks, Yann (talk) 10:12, 28 January 2022 (UTC)

Autopatroller done. Filemover is bundled with Admin rights here and can't be granted separately. Beeswaxcandle (talk) 17:11, 28 January 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:08, 11 March 2022 (UTC)

history merge

The following discussion is closed.

Please merge history of pages The Mysterious Card & The Black Cat (magazine)/Volume 1/Number 5/The Mysterious Card.

I did not notice while preparing the scan-based version that another version of this text (based on the same source) already exists. I think it is worth to preserve both version history in one place. Ankry (talk) 23:55, 1 February 2022 (UTC)

  Done --EncycloPetey (talk) 00:22, 2 February 2022 (UTC)
This section was archived on a request by: Beeswaxcandle (talk) 02:09, 11 March 2022 (UTC)

Move request: The Village Pulpit, Volume II to The Village Pulpit/Volume 2

This section was archived on a request by: --Xover (talk) 06:48, 7 April 2022 (UTC)

Copied from Wikisource:Scriptorium#Move request: The Village Pulpit, Volume II to The Village Pulpit/Volume 2. I found this on User:Inductiveload/false root pages, and I'd like to standardize the page structure. Specifically, the moves I'd like are:

Thanks! —CalendulaAsteraceae (talk • contribs) 07:29, 4 April 2022 (UTC)

@CalendulaAsteraceae:   Done Xover (talk) 06:56, 5 April 2022 (UTC)

Need some sort of template for constitutions and other iterative works

This section was archived on a request by: Xover (talk) 18:21, 23 April 2022 (UTC)

It is my opinion that we need to template tag those government works that have histories of versions as well-meaning editors keep updating existing versions rather than adding completely new versions. And it would be fair to say that we somewhat bury the fact that our documents are static versions rather than dynamic. I think that we should develop an elegant template that we can apply to these types of iterative works that clearly says that the presented work is a static version, and clearly states which static version. Any takers? — billinghurst sDrewth 04:01, 19 January 2021 (UTC)

Restore deleted items so I can finish transcriptions

This section was archived on a request by: Xover (talk) 18:19, 23 April 2022 (UTC)

Please look at Portal:Susannah_Lattin, the red links were entries that were deleted before I could finish transcription or before I could migrate the text from Commons. Could they be restored so I can finish the project? --RAN (talk) 03:00, 27 February 2021 (UTC)

@Richard Arthur Norton (1958- ): It is imo possible to restore it, but I had a look e. g. at The Long Island Mystery which is just a so short extract of the text that I am not really sure why it would be useful. Can just the page be simply founded again, only this time with the full text? --Jan Kameníček (talk) 09:35, 27 February 2021 (UTC)
The full text already exists for all these entries, they were deleted as I was creating them. I have the corrected text or the raw OCR at Wikimedia Commons and at Familypedia, where they were in 2015 when their counterpart here was deleted. I won't be be able to match them up to their image and text at Commons until I see the full article titles and what text was already there. The person deleting them, should have just asked me if I had the text to complete them. I think it was part of a larger dispute over whether ordinary people can get a portal or a category to tie them together as a subject of a group of articles. If you restore them, I can finish what I started. --RAN (talk) 20:20, 27 February 2021 (UTC)
I have restored Brooklyn Eagle/1868/The Long Island Mystery. It's the one with content. Most of the others are a header only with a file link. The one from the New York Herald was never created. Beeswaxcandle (talk) 20:37, 27 February 2021 (UTC)
@Richard Arthur Norton (1958- ): Please don't create these unfinished in main namespace. If you want to undertake a progressive transcription like that, then create it in your user space in a sandbox. [This is not the first time this has been mentioned and you have a string of unfinished transcriptions sitting in Special:PrefixIndex/user:Richard_Arthur_Norton_(1958-_).] Of course the best practice when you have a scan of the text is to utilise the Index:/Page: namespace like everyone else is encouraged to do. — billinghurst sDrewth 22:29, 27 February 2021 (UTC)
And to your sniping assertion, I would point you to your user talk page where there is still the very specific and clear text about why they were deleted. And yes, it was part of your history of problematic editing at that time. — billinghurst sDrewth 22:37, 27 February 2021 (UTC)
When you refer to my comments as "sniping" it is another indicator there is a personal problem, hence the request for an interaction ban. --RAN (talk) 21:11, 2 March 2021 (UTC)
  • And as I said then, and is still true today. I have the transcriptions waiting to be cut and pasted, except you delete faster than I can finish the work. We also have categories for entries called Category:25% for entries that are 25% transcribed or less. We even have a Category:0%. If you asked me if I had the text, rather than delete things I am working on, everyone would be happier. --RAN (talk) 21:09, 2 March 2021 (UTC)

  Comment To any admin restoring progressive transcriptions, I would ask that if you restore them to main namespace that they are then moved to user namespace for their completion. Easy for them to be moved back to main ns upon completion. — billinghurst sDrewth 22:42, 27 February 2021 (UTC)

move requests

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

I am posting at Wikisource:Scriptorium#Repairs_(and_moves), but no one seems to be monitoring it. CYGNIS INSIGNIS 04:09, 9 August 2021 (UTC)

Import request for {{Date}}

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

I'd appreciate it if {{Date}} could be re-imported from commons:Template:Date. That's where it came from initially, but the version at Commons has changed a lot (and works a lot better). Thanks! —CalendulaAsteraceae (talk • contribs) 06:51, 13 October 2021 (UTC)

@CalendulaAsteraceae: {{date}} and its underlying Module:Date are problematic due to naming conflicts between the Commons version and the enwp version. It's on my todo list to resolve this, but it's going to take quite a bit of research and migration of other templates/modules so I haven't found the time yet. Xover (talk) 08:13, 24 October 2021 (UTC)
@Xover: That makes sense; thank you! It's certainly not urgent. —CalendulaAsteraceae (talk • contribs) 08:30, 24 October 2021 (UTC)
@CalendulaAsteraceae: {{date}} has now been re-synced from Commons. Xover (talk) 18:08, 26 October 2021 (UTC)
@Xover: Thanks you so much! —CalendulaAsteraceae (talk • contribs) 02:54, 27 October 2021 (UTC)
Just to note, this mess was generating too many issues so I've started in on trying to resolve it. It's probably going to take some time to complete, and breakage is expected while it's going on. If you run into issues related to dates, possibly accompanied by big red Lua errors, please let me know. Xover (talk) 17:52, 26 October 2021 (UTC)
Ok, all the issues I've been able to identify have been fixed. Module:Date is now w:Module:Date, and Module:DateI18n is c:Module:DateI18n (these are both in line with what other projects do). The custom code that was in Module:Date has been split out to Module:Era and Module:Author has been migrated to use that instead.
I'm not aware of any linger breakage from this, but there's a lot of obscure interdependent code in this area so I can't guarantee there isn't something remaining. The most likely and visible place to keep an eye out is in automatically added date-based categories for authors, but anything date based could potentially have been affected. Please let me know if you run across something. Xover (talk) 18:44, 27 October 2021 (UTC)

Requesting import of commons:Template:Cc-by-sa-3.0-de

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

commons:Template:Cc-by-sa-3.0-de is used on File:Governance across borders.pdf and doesn't seem to be here. Thank you! —CalendulaAsteraceae (talk • contribs) 06:20, 24 October 2021 (UTC)

@CalendulaAsteraceae: We can't import Commons' license templates here directly for technical reasons (they have a whole jerry-rigged i18n/l10n setup for their templates). But do we really need a -de specific CC BY-SA? I thought the CC licenses were interchangeable? Xover (talk) 07:44, 24 October 2021 (UTC)
@Xover: That does seem to be the case; thanks for catching that. —CalendulaAsteraceae (talk • contribs) 08:33, 24 October 2021 (UTC)

Script error: The function "missing_params_error" does not exist.

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

Some pages such as 2018 Hong Kong Policy Act Report started displaying a red error notice Script error: The function "missing_params_error" does not exist. What has happened and can it be fixed? --Jan Kameníček (talk) 12:23, 21 January 2022 (UTC)

It seems to happen to any page after it is newly saved or purged. --Jan Kameníček (talk) 12:32, 21 January 2022 (UTC)
Seems to be OK now, probably after this edit. --Jan Kameníček (talk) 13:02, 21 January 2022 (UTC)
Indeed this change appears to have broken it. Another example of why revert first, think later usually ends in tears. Also a excellent example of what the "preview a page with this template" edit box is for.
As for why that revert was made (there's no comment, so I'm guessing as to motive; there appears to be no emergency requiring a snap revert), regardless of whether or not defaultsorts should generally be applied with the header template, with interposer header templates, or not (I'm going to say not universally, but maybe in some circumstances with sufficient care, quite probably), providing the option to do so isn't the same thing as mandating it (or even recommending it). Specifically, and quite intentionally at this point, the defaultsort parameter is optional and defaults to a no-op. How, if and when it should be used would depend on what approach is used. For a non-exhaustive list of options, see #Edit request for MediaWiki filter. I have no particular personal interest in defaultsorts, so other than providing options to those who are interested in avoiding the need to manually curate 130k instances of them, I have no horse in this race. Inductiveload—talk/contribs 14:05, 21 January 2022 (UTC)

File import

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

Please import File:Проект Закона «О специальной самоуправляемой административной территории Закарпатье».jpg from Wikimedia Commons. Thank you. TE(æ)A,ea. (talk) 17:26, 10 February 2022 (UTC)

@TE(æ)A,ea.:   Done Please clean up, translate, etc. the file information page. Also, please keep in mind that unless it is actually used for a Translation it is out of scope on enWS as containing no English text. Oh, and "PS.", a link to the undeletion discussion on Commons and an explanation of the circumstances and rationale would have been helpful (less research required). Xover (talk) 10:52, 12 February 2022 (UTC)

.space blocked by the spam filter?

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

At Page:SATCON2 Algorithms Report.pdf/36 the addition of a link to space-track (the first link on the page) was blocked by the spam filter, apparently '.space' is blocked and this also catches this URL. I've worked around it, but please could someone fix this? Thanks. Mike Peel (talk) 19:28, 12 February 2022 (UTC)

120.29.117.111

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

Please block this IP as soon as possible, and sorry for revert warring. Thanks in advance. NguoiDungKhongDinhDanh (talk) 06:03, 4 March 2022 (UTC)

@NguoiDungKhongDinhDanh: Done. But in future, don't get into a revert war in these cases; just drop a note here. Xover (talk) 06:33, 4 March 2022 (UTC)
I used a script and it was more effective than I thought. Thanks! NguoiDungKhongDinhDanh (talk) 06:35, 4 March 2022 (UTC)

Languageseeker's request to delete all their pages

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

Recording my actions taken. User:Languageseeker this morning marked all their User pages for Speedy Deletion under the G7 Author Request criterion. I have deleted all the sub-pages and sandboxes that were so marked as these were all task specific and the only editors were themself and PheBot for some Match & Split tasks. I have declined to delete their main User page and UserTalk page, as I don't believe that this is an appropriate action to take for these pages—particularly as much of the history of planning for and setting up the Monthly Challenge is contained therein. Additionally, deleting the UserTalk page of an established user results in deleting other user's contributions, which is not permitted under criterion G7. Beeswaxcandle (talk) 00:41, 10 March 2022 (UTC)

  • Personal User: and User talk: pages of formerly-established-but-now-permanently-absent editors have been deleted in the past, see here and User: page, which both had much content. TE(æ)A,ea. (talk) 00:54, 10 March 2022 (UTC)
    A vanished user is somewhat different. --Xover (talk) 08:42, 10 March 2022 (UTC)
  • For whatever it's worth, I agree with this handling, except in that we usually delete User: pages on any otherwise valid request (i.e. made by the owning user) without delving into their rationale. For example, they may want to use the global user page from meta for consistency cross projects. The talk page is, as you point out, a different matter, and not deletable under G7. --Xover (talk) 10:38, 10 March 2022 (UTC)
I'm going to note here that I did delete Languageseeker's user page per their request, as I think this is fairly standard practice. What they want to do with their user page is their choice. But user talk pages, I agree, are a different matter. Languageseeker started two discussions at Wikisource:Proposed deletions about both their user and user talk pages. PseudoSkull (talk) 15:21, 10 March 2022 (UTC)

24-hour IP range block

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

Hi, I've just blocked 41.115.0.0/16 for 24 hours. There is an ongoing cross-wiki battle of a set of socks c:User:Achim55/Sockpuppet_investigations/MZ_Mbili. The IP addresses in the range are repeatedly adding a particular set of templates with the intent of being annoying. If I've got the range wrong, please feel free to adjust it. Beeswaxcandle (talk) 23:15, 10 March 2022 (UTC)

Thanks. Extended to 3 days. Same range. I note that in the past the erk has used 41.113 range addresses. Will have to see if they revert back to those. Beeswaxcandle (talk) 03:57, 12 March 2022 (UTC)

Move request for A History of the Military Transactions of the British Nation in Indostan

This section was archived on a request by: Xover (talk) 18:03, 23 April 2022 (UTC)

I'd like for A History of the Military Transactions of the British Nation in Indostan, Volume 1 to be moved to A History of the Military Transactions of the British Nation in Indostan/Volume 1, likewise A History of the Military Transactions of the British Nation in Indostan, Volume 2 to A History of the Military Transactions of the British Nation in Indostan/Volume 2, and for the subpages of these pages to also be moved accordingly. Thank you! —CalendulaAsteraceae (talk • contribs) 02:26, 7 April 2022 (UTC)

@CalendulaAsteraceae:   Done Xover (talk) 06:57, 7 April 2022 (UTC)
Thanks! —CalendulaAsteraceae (talk • contribs) 17:15, 7 April 2022 (UTC)

blanking spree

Somebody at 113.211.142.27 appears to be blanking and vandalizing a number of pages. -Pete (talk) 16:15, 4 May 2022 (UTC)

Thanks for the alert. IP blocked short term and page content restored.
This section was archived on a request by: --EncycloPetey (talk) 16:20, 4 May 2022 (UTC)

Protected edit request for Module:ISO 639

I'd like it if there were an option in Module:ISO 639 to specify an error message if the language code isn't recognized. The way I'd do it is like this—unless there are uses of the module where it's important that it return nil if the language code isn't recognized, in which case I can adjust accordingly. Thanks! —CalendulaAsteraceae (talk • contribs) 21:56, 5 May 2022 (UTC)

@CalendulaAsteraceae: The convention is that functions return nil to signal an error, particularly this kind of error, and it's generally bad practice to hard code error messages down in library code (for all sorts of reasons). This kind of behaviour is better handled closer to the user layer, but possibly aided by a function in the library to check whether the code exists and returning a boolean on which the error message can be made conditional. What's the context / use case? Xover (talk) 11:32, 7 May 2022 (UTC)
@Xover The use case is that {{ISO 639 name}} has an option to provide a default value if the code isn't recognized, and now that the template is using Module:ISO 639, I want to make sure that functionality still works. Which, now that I'm typing this, I'm realizing could be done with just an option in the module to provide a default value, something like this.
(Another question: what's a good way to do error-categorization for {{ISO 639 name}}?) —CalendulaAsteraceae (talk • contribs) 22:49, 7 May 2022 (UTC)
@CalendulaAsteraceae: Error categorization is just outputting whatever category you want at some point where the wikimarkup could validly appear. I wish the MW devs would move categories out of page content and into metadata for a page, and allow an API from Lua to set cats in a structured way. But for now it's just a matter of spitting out a text string with the category markup and hoping it'll be in some valid context that doesn't mess up formatting.
But what is the use case for having a default language if an invalid language code is provided? In what situation would you want some random and possibly changeable language name returned? As an interface guarantee, "returning either a valid language name or nil" is a lot cleaner than "… or possibly some default value, picked either by a template or module developer, or provided by the end user, that may or may not understand what it means and what the template does, and may or may not be stable over time, and may or may not be a valid language name under some standard or local convention or colloquially or in the user's head."
nil is a "default value" of a sort, that has the precise semantics "something went wrong". When something goes wrong you generally want either calling code or the invoking user to be made aware of that fact immediately so that they can fix it. Returning some seemingly valid output is directly contrary to this goal: it obfuscates the fact that we are in an error situation and thus makes it harder to fix. Xover (talk) 10:47, 8 May 2022 (UTC)
Thank you for explaining! —CalendulaAsteraceae (talk • contribs) 22:34, 9 May 2022 (UTC)
This section was archived on a request by: —CalendulaAsteraceae (talk • contribs) 04:58, 7 August 2022 (UTC)

DIFFERENT protected edit request for Module:ISO 639

It's occurred to me that it would be nice if the list of recognized language codes were available outside the module, and the simplest way to do that would be like this: move the lookup table outside of the language_name function, and add this function: 

--[=[
Get the list of all recognized ISO 639 (-1, -2 or -3) codes.
]=]
function p.language_codes()
	return pairs(langs)
end

Would this be possible? —CalendulaAsteraceae (talk • contribs) 21:56, 15 May 2022 (UTC)

…possibly pairs doesn't do what I want it to there, but the substance of the request still stands. —CalendulaAsteraceae (talk • contribs) 00:11, 16 May 2022 (UTC)
Yeah, it definitely doesn't, and I'm no longer sure what I wanted a table of all valid ISO codes for, so never mind. —CalendulaAsteraceae (talk • contribs) 09:10, 30 May 2022 (UTC)
This section was archived on a request by: —CalendulaAsteraceae (talk • contribs) 04:58, 7 August 2022 (UTC)

Russia—Ukraine conflict on-wiki

Just a note that the ongoing Russia—Ukraine conflict (and I am deliberately not characterizing it beyond identifying it) is currently creating echoes on-wiki across Wikimedia projects, with Wikimedians sympathising with one or the other of the involved parties acting or reacting on-wiki to events happening IRL. It is very likely this kind of thing will spill over to English Wikisource too (for example, speeches by representatives of the parties or by third parties are in scope) and by its very nature it is an issue apt to engender very strong feelings and emotional responses. I urge all admins to be on the lookout for on-wiki behaviour or actions that appear motivated in some way by this conflict and step in to manage such situations before they spin out of control, but with diplomacy and sensitivity in a very difficult situation for many.

Also, if you are an admin with a personal stake in this conflict or very strong feelings about it, please leave admin actions that are at all related to it to other admins. We've seen otherwise intelligent and level-headed admins on other projects act on what they feel is a moral imperative but entirely outside policy. There may indeed be trolling or propaganda being perpetuated on-wiki that we need to manage, but if you have a personal stake or very strong feelings you are probably not going to be the best person to make the judgement call of where to draw the line.

Hopefully we can keep this place a fussy, dusty, and what most would consider pretty boring place rather than import IRL conflicts. Xover (talk) 07:05, 28 February 2022 (UTC)

In agreement. Ineuw (talk) 23:45, 1 March 2022 (UTC)
Agreed. Telling us any existing conflicts may catch our attention.--Jusjih (talk) 03:44, 26 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:59, 23 September 2022 (UTC)

Move request for Castelvines y Monteses

I'd like to request that Castelvines y Monteses and its subpages be moved to Castelvines y Monteses (Cosens) etc. without leaving redirects, to make room for a translations page. Thanks! —CalendulaAsteraceae (talk • contribs) 02:22, 10 April 2022 (UTC)

@CalendulaAsteraceae:   Done Xover (talk) 17:53, 23 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:59, 23 September 2022 (UTC)

Page realignment request:Index:History of Oregon Literature.djvu

The 'realignment' below should be done in the 'batch' order presented to avoid moving the 'wrong' pages. Thanks. ShakespeareFan00 (talk) 06:01, 12 April 2022 (UTC)

Batch 1
Old page pp New page
Page:History of Oregon Literature.djvu/301 (pp 289) Page:History_of_Oregon_Literature.djvu/323
Page:History of Oregon Literature.djvu/302 (pp 290) Page:History_of_Oregon_Literature.djvu/324
Page:History of Oregon Literature.djvu/303 (pp 291) Page:History_of_Oregon_Literature.djvu/325
Page:History of Oregon Literature.djvu/305 (pp 293) Page:History_of_Oregon_Literature.djvu/327
Page:History of Oregon Literature.djvu/306 (pp 294) Page:History_of_Oregon_Literature.djvu/328
Page:History of Oregon Literature.djvu/307 (pp 295) Page:History_of_Oregon_Literature.djvu/329
Page:History of Oregon Literature.djvu/308 (pp 296) Page:History_of_Oregon_Literature.djvu/329

ShakespeareFan00 (talk) 23:15, 11 April 2022 (UTC)

Batch 2
old page pp newpage
Page:History_of_Oregon_Literature.djvu/461 (pp 425) Page:History of Oregon Literature.djvu/467
Page:History_of_Oregon_Literature.djvu/462 (pp 426) Page:History of Oregon Literature.djvu/468
Page:History_of_Oregon_Literature.djvu/463 (pp 427) Page:History of Oregon Literature.djvu/469
Batch 3
old page pp newpage
Page:History_of_Oregon_Literature.djvu/433 (pp 415) Page:History_of_Oregon_Literature.djvu/455
Page:History of Oregon Literature.djvu/434 (pp 416) Page:History of Oregon Literature.djvu/456
Page:History of Oregon Literature.djvu/435 (pp 417) Page:History of Oregon Literature.djvu/457
Page:History of Oregon Literature.djvu/436 (pp 418) Page:History of Oregon Literature.djvu/458
Page:History of Oregon Literature.djvu/439 (pp 419) Page:History of Oregon Literature.djvu/461
Page:History of Oregon Literature.djvu/440 (pp 420) Page:History of Oregon Literature.djvu/462
Page:History of Oregon Literature.djvu/441 (pp 421) Page:History of Oregon Literature.djvu/463
Page:History of Oregon Literature.djvu/442 (pp 422) Page:History of Oregon Literature.djvu/464
Page:History of Oregon Literature.djvu/443 (pp 423) Page:History of Oregon Literature.djvu/465
Page:History of Oregon Literature.djvu/444 (pp 424) Page:History of Oregon Literature.djvu/466
Page:History of Oregon Literature.djvu/448 (pp 428) Page:History_of_Oregon_Literature.djvu/470
Page:History of Oregon Literature.djvu/449 (pp 429) Page:History_of_Oregon_Literature.djvu/471
Page:History of Oregon Literature.djvu/450 (pp 430) Page:History_of_Oregon_Literature.djvu/472
Page:History of Oregon Literature.djvu/451 (pp 431) Page:History_of_Oregon_Literature.djvu/473
Page:History of Oregon Literature.djvu/452 (pp 432) Page:History_of_Oregon_Literature.djvu/474
Page:History of Oregon Literature.djvu/453 (pp 433) Page:History_of_Oregon_Literature.djvu/475
Page:History_of_Oregon_Literature.djvu/454 (pp 434) Page:History_of_Oregon_Literature.djvu/476
Page:History_of_Oregon_Literature.djvu/455 (pp 435) Page:History_of_Oregon_Literature.djvu/477
Page:History_of_Oregon_Literature.djvu/456 (pp 436) Page:History_of_Oregon_Literature.djvu/478
Page:History_of_Oregon_Literature.djvu/457 (pp 437) Page:History_of_Oregon_Literature.djvu/479
Page:History_of_Oregon_Literature.djvu/458 (pp 438) Page:History_of_Oregon_Literature.djvu/480
Page:History_of_Oregon_Literature.djvu/459 (pp 439) Page:History_of_Oregon_Literature.djvu/481
Page:History_of_Oregon_Literature.djvu/460 (pp 440) Page:History_of_Oregon_Literature.djvu/482

ShakespeareFan00 (talk) 05:13, 12 April 2022 (UTC)

Batch 4
old page pp newpage
Page:History of Oregon Literature.djvu/571 (pp. 547) Page:History of Oregon Literature.djvu/595
Page:History of Oregon Literature.djvu/572 (pp. 548) Page:History of Oregon Literature.djvu/596
Page:History of Oregon Literature.djvu/573 (pp. 549) Page:History of Oregon Literature.djvu/597
Page:History of Oregon Literature.djvu/574 (pp. 550) Page:History of Oregon Literature.djvu/598
Page:History of Oregon Literature.djvu/575 (pp. 551) Page:History of Oregon Literature.djvu/599
Page:History of Oregon Literature.djvu/576 (pp. 552) Page:History of Oregon Literature.djvu/600
Page:History of Oregon Literature.djvu/577 (pp. 553) Page:History of Oregon Literature.djvu/601
Page:History of Oregon Literature.djvu/578 (pp. 554) Page:History of Oregon Literature.djvu/602
Page:History of Oregon Literature.djvu/579 (pp. 555) Page:History of Oregon Literature.djvu/603
Page:History of Oregon Literature.djvu/580 (pp. 556) Page:History of Oregon Literature.djvu/604
Page:History of Oregon Literature.djvu/581 (pp. 557) Page:History of Oregon Literature.djvu/605
Page:History of Oregon Literature.djvu/582 (pp. 558) Page:History of Oregon Literature.djvu/606
Page:History of Oregon Literature.djvu/583 (pp. 559) Page:History of Oregon Literature.djvu/607
Page:History of Oregon Literature.djvu/584 (pp. 560) Page:History of Oregon Literature.djvu/608
Page:History of Oregon Literature.djvu/585 (pp. 561) Page:History of Oregon Literature.djvu/609
Page:History of Oregon Literature.djvu/586 (pp. 562) Page:History of Oregon Literature.djvu/610
Page:History of Oregon Literature.djvu/587 (pp. 563) Page:History of Oregon Literature.djvu/611
Page:History of Oregon Literature.djvu/588 (pp. 564) Page:History of Oregon Literature.djvu/612
Page:History of Oregon Literature.djvu/589 (pp. 565) Page:History of Oregon Literature.djvu/613
Page:History of Oregon Literature.djvu/590 (pp. 566) Page:History of Oregon Literature.djvu/614
Page:History of Oregon Literature.djvu/591 (pp. 567) Page:History of Oregon Literature.djvu/615
Page:History of Oregon Literature.djvu/592 (pp. 568) Page:History of Oregon Literature.djvu/616
Page:History of Oregon Literature.djvu/593 (pp. 569) Page:History of Oregon Literature.djvu/617
Page:History of Oregon Literature.djvu/594 (pp. 570) Page:History of Oregon Literature.djvu/618
Page:History of Oregon Literature.djvu/595 (pp. 571) Page:History of Oregon Literature.djvu/619
Page:History of Oregon Literature.djvu/596 (pp. 572) Page:History of Oregon Literature.djvu/620
Page:History of Oregon Literature.djvu/597 (pp. 573) Page:History of Oregon Literature.djvu/621
Page:History of Oregon Literature.djvu/598 (pp. 574) Page:History of Oregon Literature.djvu/622
Page:History of Oregon Literature.djvu/599 (pp. 575) Page:History of Oregon Literature.djvu/623


Batch 5
old page pp newpage
Page:History of Oregon Literature.djvu/557 (pp. 535) Page:History of Oregon Literature.djvu/581
Page:History of Oregon Literature.djvu/558 (pp. 536) Page:History of Oregon Literature.djvu/582
Page:History of Oregon Literature.djvu/559 (pp. 537) Page:History of Oregon Literature.djvu/583
Page:History of Oregon Literature.djvu/560 (pp. 538) Page:History of Oregon Literature.djvu/584
Page:History of Oregon Literature.djvu/561 (pp. 539) Page:History of Oregon Literature.djvu/585
Page:History of Oregon Literature.djvu/562 (pp. 540) Page:History of Oregon Literature.djvu/586
Page:History of Oregon Literature.djvu/563 (pp 541) Page:History of Oregon Literature.djvu/587
Page:History of Oregon Literature.djvu/564 (pp. 542) Page:History of Oregon Literature.djvu/588
Page:History of Oregon Literature.djvu/565 (pp. 543) Page:History of Oregon Literature.djvu/589
Page:History of Oregon Literature.djvu/566 (pp. 544) Page:History of Oregon Literature.djvu/590
Page:History of Oregon Literature.djvu/567 (pp. 545) Page:History of Oregon Literature.djvu/591
Page:History of Oregon Literature.djvu/568 (pp. 546) Page:History of Oregon Literature.djvu/592

ShakespeareFan00 (talk) 05:56, 12 April 2022 (UTC)

@ShakespeareFan00, @Peteforsyth:   Done Please check that I didn't mess up anything. Xover (talk) 17:30, 23 April 2022 (UTC)
@Xover: Thank you! I'm traveling and won't be able to check closely for a week or so, but I appreciate the effort and the note! -Pete (talk) 21:01, 24 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:00, 23 September 2022 (UTC)

request move volume Zoologist

Could an administrator please move the index of a volume of The Zoologist?

It's about Index:The Zoologist - Volume 4.djvu. It should be moved to Index:The Zoologist, 1st series, vol 4 (1846).djvu, to have it conform to other volumes of The Zoologist, that are indexed, especially in the 3rd and 4th series. Thanks, --Dick Bos (talk) 10:44, 13 April 2022 (UTC)

@Dick Bos: The Index: page needs to be at the same name as the associated File:; which in this case is on Commons, so you'll first need to request a move there and then we can move the Index: and Page: pages here. Xover (talk) 17:33, 23 April 2022 (UTC)
@User:Xover, thank you. Done. --Dick Bos (talk) 17:41, 25 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:00, 23 September 2022 (UTC)

Renaming request for Author:Pierre Banet-Rivet

Hi! I'd like to rename Author:Pierre Banet-Rivet in Author:Paul Banet-Rivet. I don't know were the name Pierre comes from; I was able to locate his birth certificate (see on Wikidata) and it is definitely Paul. --Jahl de Vautban (talk) 19:00, 22 April 2022 (UTC)

@Jahl de Vautban:   Done Xover (talk) 19:19, 22 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:01, 23 September 2022 (UTC)

Move request for The paradise, or garden of the holy fathers

Could The paradise, or garden of the holy fathers and its subpages linked in the TOC be moved to The paradise, or garden of the holy fathers/Volume 1 etc.? (The paradise, or garden of the holy fathers/Volume 2 and its subpages should not be moved.) Once this is done I'd also like for The Paradise or Garden of the Holy Fathers to be moved to The paradise, or garden of the holy fathers. Thanks! —CalendulaAsteraceae (talk • contribs) 21:06, 5 May 2022 (UTC)

Question: Why is "..., or garden..." in the title? It does not appear on the work's title page. --EncycloPetey (talk) 22:04, 5 May 2022 (UTC)
@EncycloPetey: Wow, I didn't notice that! I have no idea, and would be happy for you to take it out. —CalendulaAsteraceae (talk • contribs) 05:12, 7 May 2022 (UTC)
It appears on the full title page: Page:Theparadiseoftheholyfathers.djvu/9. But I would agree that a better page name would be The Paradise, or possibly The Paradise of the Holy Fathers.
In any case, this does not look like a simple move: there are a gazillion subpages in a complicated work structure that currently does not use subpages in a sane way. See Special:PrefixIndex/The paradise, or garden of the holy fathers/. In other words, I think this needs a bigger cleanup and a well-tought-out subpage structure. The Paradise/Volume 1/Book 1/Chapter 1 for The History of Abba Isidore for example.
That kind of cleanup is possibly best handled manually by someone with +sysop (for which I do not have the spare cycles currently, sorry). Alternately, given a list of page moves I can have a bot do it. If so, the format would be:
[[From page 1]]
[[To page 1]]
[[From page 2]]
[[To page 2]]
Or any other variant with from a delimiter to that I can easily transform it. Xover (talk) 11:24, 7 May 2022 (UTC)
Thank you! —CalendulaAsteraceae (talk • contribs) 23:51, 9 May 2022 (UTC)
Just to note, I haven't forgotten about this but I am waiting for the fix to phab:T307826 to get deployed to PAWS. If it's really pressing I can work around it by running from a local checkout of HEAD, but that's a bit of a hassle so I'll just wait for the deployment unless I'm nagged on. :) Xover (talk) 13:11, 13 May 2022 (UTC)
@CalendulaAsteraceae:   Done The bugfix finally got deployed so I've run the move. Please check the results and update the internal links as needed (let me know if you need any batch regex replacements there). Xover (talk) 06:10, 23 May 2022 (UTC)
@Xover: Thank you! Could you update the links in the TOC for Volume 1? Page:Theparadiseoftheholyfathers.djvu/13, Page:Theparadiseoftheholyfathers.djvu/14, Page:Theparadiseoftheholyfathers.djvu/15, Page:Theparadiseoftheholyfathers.djvu/16, Page:Theparadiseoftheholyfathers.djvu/17. —CalendulaAsteraceae (talk • contribs) 07:40, 24 May 2022 (UTC)
@CalendulaAsteraceae:   Done Xover (talk) 14:15, 24 May 2022 (UTC)
Pages to move
This section was archived on a request by: — billinghurst sDrewth 14:01, 23 September 2022 (UTC)

Vandalism

Hello, I noticed an ip which was vandalising User:Mpaa and kept vandalising (page blanking and content removal) this administrators userpage. The ip: Special:Contributions/2601:183:CB81:6460:F078:25B3:3716:3BE6. They might need to be blocked or the page might require protection. Thanks, Terasail (talk) 15:37, 2 June 2022 (UTC)

@Terasail: Blocked. PseudoSkull (talk) 15:39, 2 June 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:02, 23 September 2022 (UTC)

Bulk move request for Index:Pastorals Epistles Odes (1748).djvu

See also: Index talk:Pastorals Epistles Odes (1748).djvu

Source pagenum in print Destination
Page:Pastorals_Epistles_Odes_(1748).djvu/34 (pp 112.) Page:Pastorals Epistles Odes (1748).djvu/126
Page:Pastorals_Epistles_Odes_(1748).djvu/35 (pp 113.) Page:Pastorals Epistles Odes (1748).djvu/127
Page:Pastorals_Epistles_Odes_(1748).djvu/36 (pp 114.) Page:Pastorals Epistles Odes (1748).djvu/128
Page:Pastorals_Epistles_Odes_(1748).djvu/37 (pp 115.) Page:Pastorals Epistles Odes (1748).djvu/129
Page:Pastorals_Epistles_Odes_(1748).djvu/38 (pp 116.) Page:Pastorals Epistles Odes (1748).djvu/130
Page:Pastorals_Epistles_Odes_(1748).djvu/39 (pp 117.) Page:Pastorals Epistles Odes (1748).djvu/131
Page:Pastorals_Epistles_Odes_(1748).djvu/40 (pp 118.) Page:Pastorals Epistles Odes (1748).djvu/132
Page:Pastorals_Epistles_Odes_(1748).djvu/41 (pp 119.) Page:Pastorals Epistles Odes (1748).djvu/133
Page:Pastorals_Epistles_Odes_(1748).djvu/42 (pp 120.) Page:Pastorals Epistles Odes (1748).djvu/134
Page:Pastorals_Epistles_Odes_(1748).djvu/43 (pp 121.) Page:Pastorals Epistles Odes (1748).djvu/135
Page:Pastorals_Epistles_Odes_(1748).djvu/44 (pp 122.) Page:Pastorals Epistles Odes (1748).djvu/136
Page:Pastorals_Epistles_Odes_(1748).djvu/45 (pp 123.) Page:Pastorals Epistles Odes (1748).djvu/137
Page:Pastorals_Epistles_Odes_(1748).djvu/46 (pp 124.) Page:Pastorals Epistles Odes (1748).djvu/138
Page:Pastorals_Epistles_Odes_(1748).djvu/47 (pp 125.) Page:Pastorals Epistles Odes (1748).djvu/139
Page:Pastorals_Epistles_Odes_(1748).djvu/48 (pp 126.) Page:Pastorals Epistles Odes (1748).djvu/140
Page:Pastorals_Epistles_Odes_(1748).djvu/49 (pp 127.) Page:Pastorals Epistles Odes (1748).djvu/141
Page:Pastorals_Epistles_Odes_(1748).djvu/50 (pp 128.) Page:Pastorals Epistles Odes (1748).djvu/142
Page:Pastorals_Epistles_Odes_(1748).djvu/51 (pp 129.) Page:Pastorals Epistles Odes (1748).djvu/143
Page:Pastorals_Epistles_Odes_(1748).djvu/52 (pp 130.) Page:Pastorals Epistles Odes (1748).djvu/144
Page:Pastorals_Epistles_Odes_(1748).djvu/53 (pp 131.) Page:Pastorals Epistles Odes (1748).djvu/145
Page:Pastorals_Epistles_Odes_(1748).djvu/54 (pp 132.) Page:Pastorals Epistles Odes (1748).djvu/146
Page:Pastorals_Epistles_Odes_(1748).djvu/55 (pp 133.) Page:Pastorals Epistles Odes (1748).djvu/147
Page:Pastorals_Epistles_Odes_(1748).djvu/56 (pp 134.) Page:Pastorals Epistles Odes (1748).djvu/148
Page:Pastorals_Epistles_Odes_(1748).djvu/57 (pp 135.) Page:Pastorals Epistles Odes (1748).djvu/149
Page:Pastorals_Epistles_Odes_(1748).djvu/58 (pp 136.) Page:Pastorals Epistles Odes (1748).djvu/150
Page:Pastorals_Epistles_Odes_(1748).djvu/59 (pp 137.) Page:Pastorals Epistles Odes (1748).djvu/151
Page:Pastorals_Epistles_Odes_(1748).djvu/60 (pp 138.) Page:Pastorals Epistles Odes (1748).djvu/152
Page:Pastorals_Epistles_Odes_(1748).djvu/61 (pp 139.) Page:Pastorals Epistles Odes (1748).djvu/153
Page:Pastorals_Epistles_Odes_(1748).djvu/62 (pp 140.) Page:Pastorals Epistles Odes (1748).djvu/154
Page:Pastorals_Epistles_Odes_(1748).djvu/63 (pp 141.) Page:Pastorals Epistles Odes (1748).djvu/155
Page:Pastorals_Epistles_Odes_(1748).djvu/64 (pp 142.) Page:Pastorals Epistles Odes (1748).djvu/156
Page:Pastorals_Epistles Odes_(1748).djvu/65 (pp 143.) Page:Pastorals Epistles Odes (1748).djvu/157
Page:Pastorals_Epistles_Odes_(1748).djvu/66 (pp 144.) Page:Pastorals Epistles Odes (1748).djvu/158
Page:Pastorals_Epistles_Odes_(1748).djvu/67 (pp 145.) Page:Pastorals Epistles Odes (1748).djvu/159
Page:Pastorals_Epistles_Odes_(1748).djvu/68 (pp 146.) Page:Pastorals Epistles Odes (1748).djvu/160
Page:Pastorals_Epistles_Odes_(1748).djvu/69 (pp 147.) Page:Pastorals Epistles Odes (1748).djvu/161

ShakespeareFan00 (talk) 07:52, 9 June 2022 (UTC)

The range Page:Pastorals_Epistles_Odes_(1748).djvu/70 to Page:Pastorals_Epistles_Odes_(1748).djvu/76 are blank and should be at the end of the work as indicated by the pagelist for the Index. ShakespeareFan00 (talk) 07:54, 9 June 2022 (UTC)

Done. Mpaa (talk) 20:54, 10 June 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:02, 23 September 2022 (UTC)

Index Migration:

Source: - Index:The complete works of Count Tolstoy (IA completeworksofc09tols).pdf
Destination:- Index:Complete Works of Count Tolstoy - 09.djvu
Page-ranges: 1-12,16,18-24, 179-182, 213, 239-242, 289-292, 324-326, 323-326, 363-366, 407-412
ShakespeareFan00 (talk) 14:10, 16 June 2022 (UTC)

Done. Mpaa (talk) 21:09, 17 June 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:02, 23 September 2022 (UTC)

Update MC Template

Can an administrator update the MC template from Template:Collaboration/MC/sandbox. It contains a little additional text to make it more welcoming to new users. Languageseeker (talk) 19:36, 14 July 2022 (UTC)

@Languageseeker:   Done Xover (talk) 22:26, 14 July 2022 (UTC)
@Xover Thank you! Languageseeker (talk) 00:36, 15 July 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:03, 23 September 2022 (UTC)

Move pages from Gift book to Gift book

Hi! Could you move the proofed pages from Index:Princess Mary's Gift Book (IA princessmarysgif00mary).pdf to Index:Princess Mary's Gift Book.djvu. The numbers match (until 81 or so which have not been proofed. And, accept my apology for trying to do this on my own with the one really stupid botchup.--RaboKarbakian (talk) 20:27, 26 July 2022 (UTC)

Done. Mpaa (talk) 07:38, 27 July 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:03, 23 September 2022 (UTC)

Block needed

180.249.164.176 (talk • contribs) is being disruptive in pages related to abortion. Some edit summaries may require revdel. FlyingAce (talk) 05:40, 3 August 2022 (UTC)

  Done --Jan Kameníček (talk) 05:54, 3 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:04, 23 September 2022 (UTC)

Is it possible to close my public account?

Years ago I asked for a secondary (public) account for security reasons, but IneuwPublic is no longer needed or used. Is it a problem to delete the account? There is nothing in the account's subfolders. — ineuw (talk) 00:59, 21 August 2022 (UTC)

@Ineuw: Accounts can't really be deleted (they're attached to old edits, for one thing), but you can request a global rename to something nonsensical (random hex string I think is what they're using). We also sometimes perform a technical block on alternate accounts like this (e.g. no-longer needed bot accounts). If you're certain you no longer want to use the account, the latter is probably the easiest way to make sure it's not at risk of hijacking. Xover (talk) 10:44, 21 August 2022 (UTC)
Much thanks for the explanation. — ineuw (talk) 14:58, 21 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:04, 23 September 2022 (UTC)

Protected edit request for Template:PD-US-no-notice

I'd like for {{PD-US-no-notice}} to use Module:PD-US-no-notice, like {{PD-US-no-renewal}} uses Module:PD-US-no-renewal. To that end, I would like for the contents of {{PD-US-no-notice}} to be replaced with the following code: 

{{#switch:{{#invoke:PD-US-no-notice|use_PD_US|{{{1|{{{deathyear|}}}}}}|{{{2|{{{pubyear|}}}}}}}}
|PD/US={{PD/US|{{{1|{{{deathyear|}}}}}}}}
|PD-US={{PD-US}}
|#default={{license
 |image=PD-icon.svg
 |text={{#invoke:PD-US-no-notice|text|{{{1|{{{deathyear|}}}}}}|{{{2|{{{pubyear|}}}}}}}}
}}
<includeonly>{{#invoke:PD-US-no-notice|category|category={{{category|}}}}}</includeonly>
}}<noinclude>{{documentation}}</noinclude>

Thank you! —CalendulaAsteraceae (talk • contribs) 05:40, 22 August 2022 (UTC)

@CalendulaAsteraceae: Why is all this logic left in the template when you already have a module? Xover (talk) 18:38, 22 August 2022 (UTC)
@Xover: Good question. I'll fix that. —CalendulaAsteraceae (talk • contribs) 02:29, 23 August 2022 (UTC)
@Xover done. New edit request for {{PD-US-no-notice}}: 
{{#invoke:PD-US-no-notice|PD_US_no_notice}}<noinclude>{{documentation}}</noinclude>
—CalendulaAsteraceae (talk • contribs) 04:38, 23 August 2022 (UTC)
@CalendulaAsteraceae:   Done Xover (talk) 05:13, 23 August 2022 (UTC)
I realized it would simplify a lot of code if I moved the PD_US_no_notice function over to Module:PD-US. Could I ask you to change the module over and then delete Module:PD-US-no-notice? —CalendulaAsteraceae (talk • contribs) 01:50, 26 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:05, 23 September 2022 (UTC)

'On Wheels'

While trying to create a page for the article 'A Regiment on Wheels' [[1]] I seem to have run into a global block on creating any page which contains the phrase 'on wheels'. Kind people on Discord found a reference to this here. Is it possible to have 'on wheels' whitelisted on this site, or should I change the page name to something else? Qq1122qq (talk) 20:53, 23 August 2022 (UTC)

An administrator can create the page, so I did and you can just use that. It's possible to whitelist it; I don't know the cost versus rewards of doing so; is that vandal still around?--Prosfilaes (talk) 23:33, 23 August 2022 (UTC)
Wow, there's a blast from the past. What was Willy On Wheeeeeels...like 2007?? I think it's not worth worrying about, just do what needs to be done and assume that one has died down...but...I kinda enjoyed the reminiscence. -Pete (talk) 04:38, 24 August 2022 (UTC)
Aw look, Willy even got some academic recognition. [2] (More like 2005.) -Pete (talk) 04:41, 24 August 2022 (UTC)
Thank you for the page creation. Qq1122qq (talk) 07:28, 24 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:06, 23 September 2022 (UTC)

Protected edit request for Template:PD-old-US

This one should be more straightforward, just replacing the content of the page with 

{{#invoke:PD-US|PD_old_US}}<noinclude>{{documentation}}</noinclude>

—CalendulaAsteraceae (talk • contribs) 18:41, 27 August 2022 (UTC)

@CalendulaAsteraceae:   Done
PS. Once you're done with this massive modernization effort (which is very much appreciated btw), please let us know so we can full-protect the modules too. No hurry while you're still working on them, but long-term we want all these core/highly used/juicy vandalism targets fully protected. Xover (talk) 18:53, 27 August 2022 (UTC)
Will do! —CalendulaAsteraceae (talk • contribs) 23:08, 27 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 14:06, 23 September 2022 (UTC)

Requesting protection of Template:Center/styles.css

An IP editor (Special:Contributions/2604:3D08:6286:7500:A41E:EAFA:4A1C:8500) recently made {{center}} disappear because the stylesheet was unprotected. @Xover only created it a few weeks ago, so this is understandable. The same IP has also made a few mysterious additions to some other templates as well (e.g., this), which might warrant a closer inspection by someone more knowledgeable than me. Shells-shells (talk) 01:47, 25 July 2022 (UTC)

@Shells-shells:   Done The rest of the edits consist mainly of manually copying over a suite of protection-related templates, and their dependencies, from enWP. Since that system is not in use here I have queried the IP regarding their intentions with this. Xover (talk) 07:55, 25 July 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 21:30, 24 December 2022 (UTC)

New IP vandal

60.120.162.139 is currently (and has been) vandalizing User talk:Inductiveload, which should also be protected (for a longer time, hopefully). TE(æ)A,ea. (talk) 04:39, 13 November 2022 (UTC)

  Done PseudoSkull (talk) 05:02, 13 November 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 21:28, 24 December 2022 (UTC)

Page:Novoa v. Diaz.pdf/120

Spam-list blocks the hyper-link at the head of the page. Please allow. TE(æ)A,ea. (talk) 20:57, 29 November 2022 (UTC)

  Done Just nowiki'd it. — billinghurst sDrewth 00:56, 30 November 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 21:28, 24 December 2022 (UTC)

Page move request

Please move Portal:Constitutions of the United States to Portal:Constitution of the United States, so that it be in line with the other projects. Thank you. -- Nectarous (talk) 13:36, 2 December 2022 (UTC)

That would be misleading. This portal does not gather only texts connected with the federal constitution, but also constitutions of the individual states of the United States, like Alabama Constitution or California Constitution. This makes it different from e. g. Portal:Constitution of Sweden. --Jan Kameníček (talk) 14:10, 2 December 2022 (UTC)
I thought the same when I created the portal (but I then changed my mind after seeing a project on Wikipedia). Anyway, I have now revoked the request. Thank you so much. --Nectarous (talk) 14:46, 2 December 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 21:28, 24 December 2022 (UTC)

Spambots checked

Hello. I am Teles and I am writing to report that I checked the following accounts due to cross-wiki spam. I noticed that they were created in a short span of time on this wiki with promotional content that was caught by abuse filter. As local checkuser policy requires, I am writing them down.

  • DeneenHairston0
  • GinaRankine
  • DeannaRobin5129
  • ImogeneBoyer
  • ShennaSiddons
  • SharynRosenbalm
  • RonnyFritzsche7
  • JonathonDennison
  • QWCNikole1415878
  • DallasHannon15

Please, tell me if there is any question. Regards, Teles (talk) 18:02, 18 September 2022 (UTC)

@Teles: Just to clarify… You're saying that in your capacity as a Steward on meta you performed a checkuser check on these accounts here at enWS? And was this at your own initiative (since you mention noticing their creation in a short span of time), or was it responsive to a request for such a check (if so, by whom and where)? Xover (talk) 18:49, 18 September 2022 (UTC)
@Xover, yes. At my own initiative. Since it wasn't requested, I placed this note here. Teles (talk) 18:56, 18 September 2022 (UTC)
@Teles: Thanks. I see Billinghurst has already blocked all these accounts, so there appears to be no further action needed here. I do need to note, though, that checkuser is not actually needed for these spambot accounts: they show up, post their crap in an obvious way, and disappear. We routinely catch and block these without checkuser. Xover (talk) 19:07, 18 September 2022 (UTC)
@Xover, oh no... there are some things that can be done. Autoblock only blocks the underlying IP for a week. So, you shouldn't rely on them to keep this wiki out of spam. We have to find them and block for a larger time. It's common to use open proxies.
I can give you some examples of what we can do with checkuser information. Those accounts are bots, which means that they may make actions that are not reasonable if done by a human being. For instance, all these accounts used at least 2 IP. One for log in and another for editing (or trying to). They might be doing this to avoid being caught by any sort of check that identifies only the IP used to login. So, one thing we can do is checking them to identify and block the second IP, since autoblock wouldn't block it. I once checked an account that used about 700 open proxies to keep logging in and out, which wouldn't be seen without checkuser. We can also identify a common IP range that can be blocked and better prevent their action.
I am not saying that we should check every spambot created here, but I strongly encourage being receptive to checking of suspicious spam activity like the one that occured today. Still, if local community believes that none of these checks should be done, I'll be totally fine with stepping back from doing it again. Regards. Teles (talk) 19:46, 18 September 2022 (UTC)
@Teles: I'm saying that we regularly get spambots creating a user or user talk page with some pretty dumb spam content here on enWS. And that we also regularly catch and block these by simply patrolling recent changes. Overall the volume we get here on enWS is very low. For this there is absolutely no need for checkuser.
I am not saying that there is never a need for checkuser, or that the enWS community (or even just myself personally) is opposed to using it when warranted. I am just saying that in this particular case, for these particular accounts, there does not seem to have been any need for checkuser here at enWS; and that in this sense they appear to be quite similar to the vast majority of such spambots we get here. Xover (talk) 20:01, 18 September 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 16:15, 28 December 2022 (UTC)

Semi-Protection for Portal:Constitutional documents

A lot of vandalism has been occuring on this page. Thank you, Matr1x-101 (talk) 20:07, 24 October 2022 (UTC)

@Matr1x-101: I've semi-protected the page for 3 months. So far it looks like more annoyance than real problem. Xover (talk) 21:17, 25 October 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 16:18, 28 December 2022 (UTC)

Protection request for Talk:NKVD Letter № 00794/B

The globally banned editor w:en:WP:LTA/GRP has decided to target the above page, with a host of open proxies as ever. JavaHurricane (talk) 16:25, 2 November 2022 (UTC)

@JavaHurricane: Thanks. The local stuff has been taken care of now. I threw slightly longer than usual blocks on the IPs that weren't already globally blocked on the assumption that they are open proxies. Xover (talk) 19:48, 2 November 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 16:19, 28 December 2022 (UTC)

Protection request for David Irving v Penguin Books and Deborah Lipstadt/V

LTA vandalism (see above). TE(æ)A,ea. (talk) 14:55, 3 November 2022 (UTC)

This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 16:19, 28 December 2022 (UTC)

WMF-banned user - spam and harassment

Possibly protect Convention on the Prevention and Punishment of the Crime of Genocide from IP editing. He IP-hops using a VPN, so blocking individual IPs is of limited value (I block them all on enwiki and Wikivoyage). I suggest watching for similar activity on other pages. Thanks - Antandrus (talk) 16:48, 17 August 2022 (UTC)
I protected the page. Mpaa (talk) 18:04, 17 August 2022 (UTC)
Unsurprisingly, he is now doing the same thing to other pages - A Letter from The International Association of Genocide Scholars currently. Thanks - Antandrus (talk) 04:38, 18 August 2022 (UTC)
The banned user has now moved to Winning the War in Iraq. JavaHurricane (talk) 03:58, 29 August 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 16:34, 29 December 2022 (UTC)

MediaWiki:Spam-whitelist addition request (29 December 2022)

Could an admin please add the following to MediaWiki:Spam-whitelist for Index:Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf 

youtu\.be/-AAyKAoPFQs # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/pa9sT4efsqY # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/vBjUWVKuDj0 # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/pbRVqWbHGuo # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/9EfgETUKfsI # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/xa43_z_82Og # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
www\.thetrumparchive\.com # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf

Thanks, —‍Mdaniels5757 (talk • contribs) 16:37, 29 December 2022 (UTC)

@Mdaniels5757   Done. Inductiveload—talk/contribs 16:47, 29 December 2022 (UTC)

2nd request

Could you please also add the following? 

t\.co/nslWcFwkCj # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/pbRVqWbHGuo # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/IQvuBoLBuC0 # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/U9GbkPhG1Lo # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/rsQTY9083r8 # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/HeQNVaQ_jU # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/3Fsf4aWudJk # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/-AAyKAoPFQs # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf
youtu\.be/rrUa0hfG6Lo # Introductory Material to the Final Report of the Select Committee to Investigate the January 6th Attack on the United States Capitol.pdf

—‍Mdaniels5757 (talk • contribs) 17:06, 29 December 2022 (UTC)

@Mdaniels5757:   Done Xover (talk) 11:33, 30 December 2022 (UTC)
This section was archived on a request by: —‍Mdaniels5757 (talk • contribs) 15:11, 30 December 2022 (UTC)

m:Requests for comment/Global de-adminship for Jusjih

A user is requesting to "global de-admin" (sorry I really don't know how likely if this could be happened) @Jusjih: which in requestor's claim, has many disruptive and abusive behaviors in several Chinese-language projects and Meta-Wiki, the requestor is also mentioned en.wikisource here where Jusjih is also an administrator, but didn't say anything else on their en.wikisource's behaviors. Do any of our adminships that may or may not familiar Jusjih's works know how to resolve it? --Liuxinyu970226 (talk) 05:18, 29 April 2022 (UTC)

  • I have commented on a similar section on the Wikipedia administrator's noticeboard to the effect that I have seen nothing from Jusjih on this project that would merit de-adminship. BD2412 T 06:22, 29 April 2022 (UTC)
I have done the same on the meta RFC. Beeswaxcandle (talk) 09:05, 29 April 2022 (UTC)
Hello all, en.wikisource will no longer be included in the scope. Your opinions will be still welcomed if you will. Thank you. Zhxy 519 (talk) 00:45, 30 April 2022 (UTC)
I have added my thoughts at meta as well. BD2412 T 06:23, 30 April 2022 (UTC)
We should still consider whether to directly adopt w:Wikipedia:No personal attacks and w:Wikipedia:Assume good faith while cited by w:Wikipedia:Don't remind others of past misdeeds.--Jusjih (talk) 18:06, 7 May 2022 (UTC)
This section was archived on a request by: BD2412 T 18:54, 14 January 2023 (UTC)

Edit request for MediaWiki filter

I've been going through pages with defaultsort conflicts, and it occurred to me that this would be easier if there were a category analogous to Category:Authors with DefaultSort error. So I'd like to request that Category:Works with DefaultSort error be created and added to MediaWiki:Duplicate-defaultsort. Thank you! —CalendulaAsteraceae (talk • contribs) 09:43, 17 January 2022 (UTC)

@CalendulaAsteraceae   Done. This is a good idea, because the current (anti-)pattern of explicit DEFAULTSORTs makes it impossible to do this automatically in the header template (i.e. strip of "A/The" if present). This cat gets us a small step closer to being able to strip most of them out as redundant. Inductiveload—talk/contribs 10:12, 17 January 2022 (UTC)
@CalendulaAsteraceae also I have added the defaultsort parameter to {{header}}.
The task now is to transition all the manual defaultsorts to either that parameter, or, for most(?) of them, do it by stripping A/An/The in the Lua function. I'm not sure the best way to move forward, but one way would be:
  • Temporarily hide the warning text in MediaWiki:Duplicate-defaultsort in mainspace (leave it enabled in other namespaces), but leave the category
  • Enable the auto-sorting (i.e. stripping of A/An/The) in Lua
  • All the mainspace pages with conflicting sort keys will then drop into the category, but won't spew big red errors
  • The category can be processed (probably with some kind of script, since most of the conflicts are likely "Foo, A" vs "Foo" and easy to handle
  • Once the category is empty, strip the rest of the DEFAULTSORTs, since if they're not throwing errors they must be redundant.
  • Now the pages are transitioned to the parameter, reinstate the warning text
This is not the only way to do it: you could also
  • Migrate all explicit DEFAULTSORTS in mainspace to the defaultsort parameter, then enable auto-sorting and then go back over all pages and remove redundant keys, or
  • Migrate all explicit DEFAULTSORTS in mainspace to the defaultsort parameter, but just delete any which will become redundant, then enable auto-sort. This will have short period when some pages will sort by their "A/An/The".
Anyway, let me know if you need any more edits to facilitate whichever method you prefer! Inductiveload—talk/contribs 10:53, 17 January 2022 (UTC)
@Simon Peter Hughes: You do a lot of work in this area. Do you have any input here?
@Inductiveload: Not sure whether it's relevant, but keep in mind that we have some bad habits involving not bothering with the full title in defaultsort so long as the string used will kinda sorta sort properly mostly. Also, the sortkey should include any article stripped at the end so that titles that differ only in the article will sort correctly among themselves. Also, we have a lot of garbage data in title fields that we probably don't want to throw unprocessed into the magic word. Hmm. And then there's the "Sort key" field in the Index: that could maybe be used for something here… Xover (talk) 12:49, 17 January 2022 (UTC)
@Xover putting the article at the end is indeed how Module:Auto sort does it, which is what I would suggest Module:header eventually could use. The current manual ones are done both with and without, e.g. A Dictionary of Music and Musicians, which is literally the first result for insource:DEFAULTSORT that begins with an article.
The least "exciting" way would be to continue to use the subpage name, rather than the title parameter, because that won't change too much. If we wanted to use the title parameter, or inhale from an index page (rather hard, since most header invocations do not know what the index is), that would be a next step.
The first steps will have to be removing the manual DEFAULTSORTs, since, because none of them have been set with noerror or noreplace, it's impossible to do anything at all until they are changed to template params (or bot through and add noerror/noreplace, which is yet another option for moving forward). There are 132k+ instances, so it's going to be pretty painful whatever happens (and that's why I have never bothered to address it myself). Inductiveload—talk/contribs 13:08, 17 January 2022 (UTC)
@Inductiveload: Now that Category:Works with DefaultSort error is clear and I've had a little time to think about it, I think your first proposed method for transitioning to auto-sorting sounds good! (Assuming you or someone can do the script part, because I sure can't.) And I'm happy to do stuff like manually resolving the trickier conflicts. —CalendulaAsteraceae (talk • contribs) 05:58, 12 February 2022 (UTC)
@Inductiveload: Thank you! I don't particularly have a preference among the different ways of transitioning pages to use the defaultsort parameter. I do have an edit request, though—could you add | defaultsort = {{{defaultsort|{{SUBPAGENAME}}}}} to the header in {{A catalogue of notable Middle Templars, with brief biographical notices}}? Pages in that work had been putting manual DEFAULTSORTs on each page, and I removed that from the preload. —CalendulaAsteraceae (talk • contribs) 02:32, 18 January 2022 (UTC)
No, please don't do that. There is nothing wrong with individual defaultsort, and it was purposeful to not have it in the template. Having a hidden defaultsort can be problematic. — billinghurst sDrewth 11:00, 18 January 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:26, 19 March 2023 (UTC)

Trying to transclude "The Queen Bee"

I am trying to transclude "The Queen Bee" to the page Grimm's Household Tales, Volume 1/The Queen Bee, but it says my action may be harmful. 192.107.137.242 17:27, 19 April 2022 (UTC)

Annoyingly, your edit was caught in a global filter because it appeared like vandalism (non-logged-in users removing large amounts of contiguous text are a common signature of vandalism at most wikis). The good news is that you only need 10 edits to become an "established enough" editor for the filter to no longer apply. This is a global filter, so we can't change it immediately here. However, if we see lots of these hits, we should probably get the filter changed to allow edits if the wiki is a Wikisource and the edit contains "<pages". Inductiveload—talk/contribs 22:46, 19 April 2022 (UTC)
@Inductiveload: IP editors never get autoconfirmed, so that won't help here. Xover (talk) 17:34, 23 April 2022 (UTC)
@192.107: if you give us the details (Index: link and relevant pages) we can transclude it for you. Alternately, it is really recommended to register a user account (entirely free, and you don't even need to provide an email address if you don't want to). With a user account it's much easier to communicate, and after something like 10 edits you get extended permissions that exempt you from some spam filters, let you move pages, etc. Xover (talk) 17:38, 23 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:27, 19 March 2023 (UTC)

New index page broken?

Just created Index:The Private Life Of Helen Of Troy(1926) (IA dli.ernet.524076).pdf and there’s a big error message and size of 0. What’s going on? feydey (talk) 17:42, 25 April 2022 (UTC)

feydey I told the form that the page was pdf, and now it works.--RaboKarbakian (talk) 23:58, 25 April 2022 (UTC)
Thanks. feydey (talk) 08:30, 26 April 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:28, 19 March 2023 (UTC)

Index:The complete works of Count Tolstoy (IA completeworksof02tols).pdf

A new DJVU scan was uploaded for Volume 2 (with some missing pages re-instated) as a Djvu (see: Wikisource:Proposed_deletions#The_complete_works_of_Count_Tolstoy), and so the pages here were migrated back from the PDF to the new scan, and any transclusions were updated.

Because I can't delete the generated redirects when migrating pages between scans, it will need an Admin to do this, and I am requesting this here.

Done, I have removed all pages in Vol.2 pdf.Mpaa (talk) 21:41, 17 June 2022 (UTC)

I had also migrated the relatively small number of pages for Index:Complete_Works_of_Count_Tolstoy_-_20.pdf as well.

This leaves Volume 9 to be migrated across and Volume 1 carefully compared between the DJVU and PDF versions.

ShakespeareFan00 (talk) 14:03, 16 June 2022 (UTC)

This section was archived on a request by: — billinghurst sDrewth 13:29, 19 March 2023 (UTC)

Request for moving an Index page

Dear admin,

Could you please move Index:An introduction to Indonesian linguistics, being four essays.djvu to Index:An introduction to Indonesian linguistics, being four essays; Renward Brandstetter; 1916; London, Royal Asiatic Society.djvu and also its Page namespace to match its current file name? Thank you. ··· 🌸 Rachmat04 · ☕ 08:56, 2 July 2022 (UTC)

@Rachmat04There is no point in moving the index or pages in Page ns. What matters is the title of the work in Main ns. Mpaa (talk) 21:17, 2 July 2022 (UTC)
I understood. But, there's a downside if the index page and file name doesn't match. If we are on Page:An introduction to Indonesian linguistics, being four essays.djvu/17, we cannot navigate to previous and next page, and also if we click the ^ arrow, it points us to "Index:An introduction to Indonesian linguistics, being four essays; Renward Brandstetter; 1916; London, Royal Asiatic Society.djvu", which is not exist. ··· 🌸 Rachmat04 · ☕ 14:01, 3 July 2022 (UTC)
@Rachmat04: I think it would be easier to move the file back to the name corresponding to the index page. --Jan Kameníček (talk) 18:12, 3 July 2022 (UTC)
  Done Mpaa (talk) 20:50, 16 March 2023 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:29, 19 March 2023 (UTC)

Page:The Indian Biographical Dictionary.djvu/189

Hello. In the history of the above page, please hide the two edits immediately before my edit. They contain a spam link being pushed across numerous wikis. Cheers. [24Cr][talk] 12:47, 15 July 2022 (UTC)

  Done --Jan Kameníček (talk) 13:07, 15 July 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:30, 19 March 2023 (UTC)

Sandbox protected

Recently, Sandbox has been under frequent attacks of a vandal and finally I decided to protect it and allow only autoconfirmed users for some time. I know that protecting Sandbox can be controversial, but I decided for this temporary step after looking at the page's history where there had been practically no non-vandal IP contributions. Today I have noticed that an IP contacted PseudoSkull on their talk page requesting unprotecting the page. Interestingly, this IP has been blocked in de.wiki for vandalism today too, so it seems quite clear that the vandal just tries to remove the obstacle. For this reason I would like to ask other admins not to reflect similar requests. -- Jan Kameníček (talk) 19:30, 26 July 2022 (UTC)

This section was archived on a request by: — billinghurst sDrewth 13:31, 19 March 2023 (UTC)

Autopatroller request Reboot01

I'm not exactly sure how to word this, but I'd like to be put in for autopatroller, I try my best to follow guidelines and community standards (And help with setting new ones) while I edit, and I even try to greet new users when I see them edit a work I watch or interact with them on the Discord. I also feel that'd it'd make my life a bit easier without seeing that little red exclamation point beside my edits whenever I look through my watched pages, heh. Reboot01 (talk) 20:06, 29 July 2022 (UTC)

@Reboot01: Done. (I think it might be useful to have something like Wiktionary's wikt:WT:Whitelist at Wikisource.) PseudoSkull (talk) 19:39, 30 July 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:31, 19 March 2023 (UTC)

Wikidata badges

Could the wikidata badge of the following pages be changed from not proofread to proofread or removed entirely.

GhostOrchid35 (talk) 02:05, 2 September 2022 (UTC)

@GhostOrchid35: Done (admin permissions not required). —CalendulaAsteraceae (talk • contribs) 08:10, 4 September 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:32, 19 March 2023 (UTC)

Edit warring

User:Jan.Kamenicek: opened a copyvio discussion on an obviously public domain work.

User:Xover: continuously hides my contributions using {{copyvio}}. Interaccoonale (talk) 00:46, 20 September 2022 (UTC)

@Interaccoonale: I'm not sure I would call anything first published outside the US after 1926 an "obviously public domain work" (bear in mind that Wikisource operates under United States copyright law). That said, the rationale provided by @Prosfilaes at WS:CV#On the death of Comrade Kobayashi seems solid, so the work probably shouldn't be deleted unless a refutation is provided. It's probably best to simply let the copyvio process run its course. There are other issues with the work (it should probably be scan-backed and put in the Translation namespace, for example), but those can be addressed in due time.
On an unrelated note, I notice the justification "ignore all rules" given in a revert of yours. Until a very few minutes ago, I was under the impression that policies were generally established independently by each wiki, and I was not aware that IAR had ever been implemented here; however, I now find m:ignore all rules, which is evidently a global policy "mandatory for all projects". I don't know exactly how this was decided as I can't immediately find any m:requests for comment relating to it on Metawiki. I would be grateful if someone could point me to an RfC or equivalent community process establishing that policy globally.
P.S. Given that you've decided to use WS:AN as a venue... I wonder when the penny will drop? Shells-shells (talk) 03:01, 20 September 2022 (UTC)
That IAR is mandatory policy is incoherent; it only works as a flexibility outside the policies. I'm going to ignore all rules by ignoring the policy IAR.--Prosfilaes (talk) 03:17, 20 September 2022 (UTC)
Tangent:
@Shells-shells, the English Wikipedia's RFC process began in 2004, and IAR is from 2001, so you won't find any RFCs about it. They used a different process, mostly involving discussions on IRC and the main mailing list, back then. The w:en:WP:PROPOSAL process wasn't formalized until many years later.
The other thing to know is that Jimmy Wales uses "policy" in a way that's closer to the "unwritten British constitution" than to a recognized canon of official documents. In that model, the specific page and the bureaucratic process is unimportant; what matters is the idea being communicated. Consequently, if you make six copies of IAR, re-word them all in different ways (but to still accurately represent that community's actual views and practice), then all six versions are also and equally "policy". WhatamIdoing (talk) 14:52, 20 September 2022 (UTC)
I should have known better: the tag at the top of the page was only added three months ago without any sort of consensus procedure, as far as I can tell. I can't find any lasting previous attempts to make it a global policy in the page history. The page was highly contentious until around 2009, after which very few edits occurred; I wonder why editing dropped off so sharply? Shells-shells (talk) 16:20, 20 September 2022 (UTC)
You said that wikisource operates under United States copyright law. Yes, and so does the Chinese Wikisource where exist a lot of works by Lu Xun published after 1927 (China's laws are not applied there, yeah?). Interaccoonale (talk) 04:08, 20 September 2022 (UTC)
I'm glad you brought this up, as s:zh:聞小林同志之死 is indeed marked as PD for the same reason Prosfilaes gave. I have mentioned this at WS:CV. I think it's a good idea, if English Wikisource is to accept user translations of texts, to cross-reference their copyright statuses with other langauge Wikisources. Shells-shells (talk) 04:40, 20 September 2022 (UTC)
I have no idea what rules the Chinese Wikisource works under, nor how careful they follow those rules.
Works under copyvio discussions are hidden under {{copyvio}}. As Shells-shells said, it's hard to say that works published after 1926 are "obviously public domain".--Prosfilaes (talk) 03:17, 20 September 2022 (UTC)
Works are hidden under {{copyvio}}, and discussions should last at least 2 weeks. Does it means that anyone can make any article invisible for at least 2 weeks without any threshold requirement? Interaccoonale (talk) 04:03, 20 September 2022 (UTC)
Two weeks for a work that should be available for decades is not that long of a time. And we wouldn't tolerate abuse via this rule; in practice this hasn't been an issue, but vandalism and harassment would be immediately reverted.--Prosfilaes (talk) 16:38, 20 September 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:36, 19 March 2023 (UTC)

IP Address Unblock

I was wondering if it would be possible to grant me an IP block exempt. I will be moving to a country that frequently blocks Wikipedia and I would like to continue contributing to this project. Languageseeker (talk) 01:32, 19 October 2022 (UTC)

  • So far as I know we don't have any specific process for granting the "IP block exempt" flag, but I have elsewhere linked Languageseeker to the relevant policies on other projects (they are pretty much the same: c:COM:IPBE, meta:WM:IPBE, etc.), and this request seems to be an obvious case for granting it. So if there are no objections forthcoming, I intend to tick the box on their account soon-ish. --Xover (talk) 04:10, 19 October 2022 (UTC)
Happy to support this at the appropriate time. Do we need a formal policy/process for this should there be similar needs in the future? Or, are we okay to simply log requests here on an ad hoc basis? Beeswaxcandle (talk) 04:33, 19 October 2022 (UTC)
Personally, I would prefer to have explicit policy for all such things—so that I don't have to do everything based on my own judgement as an admin—but the process prescribed by such a policy could beneficially be no more than "Ask an admin, they'll give it to you if x, y, and z.". At other projects the main concern of the policies seems to be 1) making clear to those asking that there will be no leeway for funny business or abuse of this privilege, and 2) that it is a privilege, not a right, and it can be removed on admin discretion (unlike, say, a ban or even a block, which requires various levels of consensus). There's some other stuff might be worthwhile in a policy about it (effectively guidance for admin and applicant), but I don't think the process as such needs to be much more involved. enWP (IIRC) doesn't even process or log these at AN, it's in each admin's personal discretion and can be requested anywhere it's convenient. Xover (talk) 04:48, 19 October 2022 (UTC)
  •   Done We don't need to have a formal local policy, m:IPBE explains this suitably and we default to global guidance in lieu of local policy. The granted right (special:listgrouprights) gives no special additional rights, it just returns an account to normal WHEN it is impacted by an IP block. — billinghurst sDrewth 23:56, 28 October 2022 (UTC)
      Comment we have managed without a formal policy for 14 years and we have had next to zero issues. We point to proxy guidance at Wikisource:IP block exemption; and typically the place where it is requested is in a user talk page {{unblock}} request. — billinghurst sDrewth 00:02, 29 October 2022 (UTC)
    Yeah, I'll concede there's no pressing need for a (local) written policy on this particular issue. It's a general opinion that we should cover more things by explicit policy to manage user expectations, and to reduce the number of things an individual admin has to reason out de facto policy for on their own in the middle of a (possibly heated) situation. Xover (talk) 09:03, 29 October 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:38, 19 March 2023 (UTC)

License template migration edit requests

I've finished setting up the Lua modules to support license templates. The edits that need an admin are the following:

See also User:CalendulaAsteraceae/Staging for a categorization demo. Thanks! —CalendulaAsteraceae (talk • contribs) 04:11, 20 October 2022 (UTC)

@CalendulaAsteraceae: {{PD-US-no-notice}} and {{PD-old-US}} is done. But before we redirect {{PD/US}} we need to do some work on the documentation for {{PD-US}} to cover both cases. Xover (talk) 09:10, 29 October 2022 (UTC)
Thanks, @Xover! I've added the info from the documentation for {{PD/US}} to the documentation for {{PD-US}}. —CalendulaAsteraceae (talk • contribs) 17:41, 29 October 2022 (UTC)
@CalendulaAsteraceae:   Done Xover (talk) 18:51, 29 October 2022 (UTC)

  Comment @CalendulaAsteraceae, @Xover: Can we please get some documentation on the talk page for PD-US about the migration from PD/US as this change is significant from the long term instruction that we have provided. I would also encourage communication to all logged in users through the mediawiki:watchlist-details dialogue capability set up,--pointing to the anchored notes on talk page should be sufficient--and to leave that in place for several months at least. We should always have communication to the community about such changes rather than have them guessing.

Thinking that it may have impacts on some of our maintenance, though will consider that at a later time. It definitely changes the outputs of numbers of petscan queries that relied on that simple differentiation. — billinghurst sDrewth 04:21, 1 November 2022 (UTC)

@Billinghurst, I've added a note at Template talk:PD-US#PD-US and PD/US merger. I'm happy for @Xover (or anyone else) to add anything I've missed!
How does the MediaWiki:Watchlist-details dialogue capability work? —CalendulaAsteraceae (talk • contribs) 03:51, 2 November 2022 (UTC)
It's presumably MediaWiki:Watchlist-announcements, and it's a way to put a notice (arbitrary wikicode) on everyone's watchlist (some info on its talk page).
But that being said, I'm not sure I understand what the need for a watchlist notice is? So far as I know {{PD/US}} still works exactly like it always has, and can be used now just like before. That it is now a redirect to {{PD-US}} should be completely transparent for most users unless they go digging for some reason.
We may have (probably do have) a need for better guidance on which templates to use when, and to use one set of guidance consistently across the site, but I'm not actually sure that guidance changed meaningfully as a result of this mostly technical change. But perhaps having more instructions on a single template's /doc page makes it more pressing that those instructions are clear and concise to avoid confusing users? Xover (talk) 09:16, 2 November 2022 (UTC)
Ugh, wrong quick copy of message names, apologies. When we are changing a long term behaviour and instruction, we should always communicate, whether we have an override/fix/whatever in place. The reason being that the redirect is not effective in all cases, and we cannot predict all uses. Especially when it is a cheap and easy thing to do. — billinghurst sDrewth 12:09, 2 November 2022 (UTC)
I'm not aware of any use cases where that might plausibly cause problems, but I've added a general watchlist notice about the changes and linked to the talk page as a venue to report issues. Xover (talk) 19:29, 2 November 2022 (UTC)

Is it necessary?

  Comment Just a short off-topic comment. I am not able to judge how necessary these changes are and if they are necessary at all, but generally speaking, the more complex and complicated things are, the less people are able to maintain them. I remember nostalgically wiki times without lua modules, when all the templates were written in wiki code and easily accessible and simple. Now we are dependent on a very few techies (who I otherwise respect very much) who understand them. Licence templates seem a very simple thing to me, is it necessary to make the access to their editing so complicated? --Jan Kameníček (talk) 12:52, 2 November 2022 (UTC)

It's an apt question to ask, and sometimes the answer is "no". But in general the answer is "yes", although the reasons can vary a bit from case to case. One big reason is that your nostalgia is fooling you: a lot of templates are not so simple, and contain increasing amounts of outright programming logic, which raw templates are profoundly unsuited for (vs. a real programming language like Lua). And even the seemingly simple templates are not so simple because they exist in an increasingly complex technological context, and the lack of fine control inherent in templates (vs. Lua) causes more and more irresolvable problems. And the more complex this whole is the less safe and sustainable it will be for non-technical contributors to wade in and make changes regardless of whether it is implemented in raw templates or in a Lua module. Xover (talk) 17:57, 2 November 2022 (UTC)
Indeed. I do want to note that I have left a number of simpler license templates, like {{PD-Pakistan}}, as-is. —CalendulaAsteraceae (talk • contribs) 03:47, 3 November 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:39, 19 March 2023 (UTC)

Forum with limited access

What I do lack is a forum with limited access where e.g. antivandal strategies could be discussed without the vandals being able to read them. It may be used to make e.g. abuse filter requests too. The access does not have to be limited to admins only, any trusted users might have it. --Jan Kameníček (talk) 13:47, 2 November 2022 (UTC)

This section was archived on a request by: — billinghurst sDrewth 13:39, 19 March 2023 (UTC)

Talk:NKVD Letter № 00794/B

Please protect this page and block 102.67.243.35, 102.69.220.86, 161.18.183.13, and 41.79.219.203 permanently (LTA). TE(æ)A,ea. (talk) 16:36, 2 November 2022 (UTC)

As for protecting, I have been recently discouraged by another admin from protecting pages against LTAs, which is why I have called for some space to make abuse filter requests above. These links to some external encyclopedias or sometimes pseudoencyclopedias repeat almost on a daily basis. Often the LTA(s?) escapes the filter by breaking the link (e.g. writing ency clopediaXY.com instead of encyclopediaXY.com) --Jan Kameníček (talk) 00:48, 3 November 2022 (UTC)
Protection is a decent enough approach for stopping an ongoing and immediate situation, combined with liberal (but not permanent) blocks of the accounts and IPs involved. But for these LTAs it's a temporary and localised solution because they'll just reappear using new IPs and on a different page, so we need other strategies in addition to local blocks and page protection. And typically that's going to be something more or less automatic based on the content and other common characteristics of their editing. I agree it would be nice to have a specific forum designed for that, but absent that you can just use the existing less-public channels. You may also want to talk to the folks over on meta who do a lot of global patrolling and filtering since they have a lot of experience with this sort of thing. Xover (talk) 11:57, 3 November 2022 (UTC)
The IPs belong to open proxies and the LTA in question is hopping between them, so long-terms blocks are pointless; they'll just skip on to a new one. But I've blocked the used ones for a while just stop the ongoing annoyance. Xover (talk) 11:47, 3 November 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:40, 19 March 2023 (UTC)

Author:Rodolfo Gustavo da Paixão

Not sure about this speedy request. The author does not seem to have anything published in English. -- Jan Kameníček (talk) 00:00, 5 December 2022 (UTC)

FWIW it doesn't look like anyone's working on a WS translation of the author's works either. —CalendulaAsteraceae (talk • contribs) 00:31, 5 December 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 13:42, 19 March 2023 (UTC)

LTA and Stalin

This is just a heads-up to explain the large number of page protections I've been doing recently. A cross-wiki LTA has been persistently adding a phrase about Stalin in various languages (Chinese, Russian, English, and Latvian so far) to headers and talk pages of various mainspace pages related to Russia in some way. So far all have been from IP addresses. Each one has been different, IIRC. I haven't had time to check the ranges, so haven't done any blocks. Between Jan and myself we've been dealing with them, with Antandrus doing some reversions. There have been two hacking attempts on my account in close succession to reversions and page protections. Beeswaxcandle (talk) 06:30, 30 December 2022 (UTC)

This section was archived on a request by: — billinghurst sDrewth 13:43, 19 March 2023 (UTC)

A letter on "Uncle Tom's cabin"

I'm trying to transclude this document, but it's saying that there is no such index. I think it's because the DJVU file has quotation marks in its name. Could someone please help me with this?

For reference, the index file is Index:A letter on "Uncle Tom's cabin" (1852).djvu.

Thanks, Lizardcreator (talk) 03:55, 15 September 2022 (UTC)

@Lizardcreator The quotation marks can be escaped like so by replacing them with the HTML entity &quot;, but I'm not sure if this is the ideal solution. This index is especially tricky because it includes both " and ' in the title; if an index title only contains double quotes, it can be wrapped with single quotes: see the transclusion of "A Modern Hercules," The Tale of a Sculptress (1899). Shells-shells (talk) 04:50, 15 September 2022 (UTC)
@Shells-shells: As a FYI, the even easier way to do this is using #tag, like {{#tag:pages||index=A letter on "Uncle Tom's cabin" (1852).djvu|from=...|to=...}} — billinghurst sDrewth 13:35, 19 March 2023 (UTC)
This section was archived on a request by: — billinghurst sDrewth 02:47, 28 June 2023 (UTC)

Request at MediaWiki talk:Protectedpagetext

There is a request at MediaWiki talk:Protectedpagetext#Protected edit request on 25 July 2022. Can somebody more competent have a look at it? -- Jan Kameníček (talk) 08:50, 26 July 2022 (UTC)

I'll follow up. Xover (talk) 09:51, 26 July 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 23:55, 10 September 2023 (UTC)

Edit request: merge Template:PD-US and Template:PD/US

I've created Module:PD-US, which allows {{PD-US}} and {{PD/US}} to be implemented in a much more streamlined way, and as the same template. Assuming the module really does work as well as I think it does, could {{PD/US}} be redirected to {{PD-US}}? —CalendulaAsteraceae (talk • contribs) 04:58, 25 August 2022 (UTC)

Ehm. Can someone remind me of the difference between {{PD-US}} and {{PD/US}}? And why we need {{PD-old-99-US}}, {{PD-old-80-US}}, {{PD-old-75-US}}, {{PD-old-70-US}}, {{PD-old-60-US}}, {{PD-old-50-US}}, {{PD-old-30-US}}, {{PD-old-25-US}} (and probably more that I didn't find in a quick search)? And why we're reporting this in strict ten year increments (that looks like an artefact of the limitations of templates rather than anything else).
What I'm saying is, presuming Module:PD-US works as intended, doesn't this just drop-in replace that whole cluster of twisty little templates? Xover (talk) 14:26, 25 August 2022 (UTC)
I believe that set of templates is meant to replicate various copyright durations worldwide; there's no point in mentioning e.g. life+55 because there's no nation that uses that. We could probably simplify it; there's not many nations below life+50, and that virtually guarantees they won't care about foreign copyrights and we host few works from them.--Prosfilaes (talk) 17:26, 25 August 2022 (UTC)
But we're not really describing jurisdictions, we're describing pma. terms as a concept and relating it to the time passed since this specific author's death. Why not just say "any country with a term longer than specific number of years since deathyear" (or however we phrase it)? Xover (talk) 17:37, 25 August 2022 (UTC)
@Xover: Historically, {{PD-US}} didn't have a death-year parameter, and {{PD/US}} required one. (I've migrated {{PD-US}} to use the module, so it has a death-year parameter now.) I'm pretty sure {{PD-old-99-US}} and so forth are just an artefact of the setup for {{PD/US}}, since they're not supposed to be used directly.
The other purpose of the pma buckets is to put works into PD-old-[years]-US categories like Category:PD-old-70-US. Do these categories serve a useful purpose? Because if not, it would be straightforward to remove the bucketing and simplify the license text like you suggested. —CalendulaAsteraceae (talk • contribs) 00:41, 26 August 2022 (UTC)
I suppose the buckets might have some use if we discover an issue that affects only a particular bracket, but I don't really see that as a likely scenario and tracking cats for such issues can be easily added when needed. So absent any other factors I'd be inclined to say we should just drop the bracketing and get rid of the helper templates. --Xover (talk) 05:49, 27 August 2022 (UTC)
PD-US is for works where the author’s death date is not known or for e.g. collective works where that would be difficult to determine. PD/US is for works where date-of-death is known, and sorts them into useful categories. CalendulaAsteraceae: Does your new module replicate the above? That’s the difference in the templates, so far as I know. TE(æ)A,ea. (talk) 01:49, 26 August 2022 (UTC)
@TE(æ)A,ea., yes, if you don't put a death-year parameter in, the module will just produce {{PD-US}}. —CalendulaAsteraceae (talk • contribs) 01:52, 26 August 2022 (UTC)
CalendulaAsteraceae: Also, it’s broken. TE(æ)A,ea. (talk) 02:25, 26 August 2022 (UTC)
@TE(æ)A,ea. I am very sorry about that. I didn't realize that {{license}} automatically adds an Author- prefix to the beginning of categories in the author namespace. —CalendulaAsteraceae (talk • contribs) 02:32, 26 August 2022 (UTC)
A demonstration:
{{PD-US}}

 

This work is in the public domain in the United States because it was published before January 1, 1929.

This work may be in the public domain in countries and areas with longer native copyright terms that apply the rule of the shorter term to foreign works.

 

Public domainPublic domainfalsefalse 

{{PD-US|1982}}

 

This work is in the public domain in the United States because it was published before January 1, 1929.

The longest-living author of this work died in 1982, so this work is in the public domain in countries and areas where the copyright term is the author's life plus 41 years or less. This work may be in the public domain in countries and areas with longer native copyright terms that apply the rule of the shorter term to foreign works.

 

Public domainPublic domainfalsefalse

—CalendulaAsteraceae (talk • contribs) 23:08, 26 August 2022 (UTC)
This section was archived on a request by: — billinghurst sDrewth 23:54, 10 September 2023 (UTC)
Retrieved from "https://en.wikisource.org/w/index.php?title=Wikisource:Administrators%27_noticeboard/Archives/2022&oldid=13442828"