Hey, I know I reverted your edits, but would like to extend an offer to work with you to get the statements correct. I've been working on Wikidata Every Politician which has similar succession and office holder boundaries.
@Wolfgang8741: I ran the edits from OpenRefine, and I still have the files on PAWS (here, if you can view them). I'm not entirely sure what format you want the data in, but from your example at BOTREQ, it appears it needs data other than the successor and judge. By the way, please just ask me to revert my edits, because now I have about 500 notifications. Thanks for taking the time to clean up my mess! ― Qwerfjkltalk18:25, 17 March 2022 (UTC)[reply]
@Qwerfjkl: Apologies for the excessive notices from the reverts, my first time catching something like this at scale. I do not have permission to view your openrefine, but an example schema config for a position would look more like the following screenshots from openrefine and based on creating this demo you may also need to create some of the positions and clean up some existing Qs for the judge positions. Yes, you probably need to create a few more columns to make a statement that fits both the established practice. I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. That is not a nuance I know the answer. It may be that confirmation date needs a new property to represent given the difference between appointed, confirmed, and starting in the role.
A quick look for Judge of the United States District Court for the Eastern District of Michigan (or similar) didn't exist - now Q111274584 and Q23933765 wasn't linked to the court - checked by viewing What links here.
You can create the position name in plain text in a new column from the table to try to mach what the position should be called and if they don't resolve, create new positions which would be another schema to configure. I'd look to Q20706330 to know what should be added when creating any new instances of judge positions related to a court listed in the table. Ideally the death date column wouldn't include the age as it makes matching less effective.
The new position schema would be a different statement you can export together or do this in two rounds. The first round to create all missing positions then second to add all the statements for persons holding those positions. For each position adding their respective qualifier of "start time" and "end time" as well as "replaces" and "replaced by" qualifiers for the position, the confirmation date (which I don't know a good property to use as a qualifier so you might ask on wikidata project chat) and "appointed by" property also would be a qualifier for the position.
Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement through the statement and the position that they will hold which is part of the "Court" that you currently have in the table as mentioned above. I hope this helps to clarify a little? Wolfgang8741 says: If not you, then who? (talk) 19:32, 17 March 2022 (UTC)[reply]
@Wolfgang8741: clean up some existing Qs for the judge positions - What exactly do you mean by this? I used {{Get QID}}, which follows redirects, so might be inaccurate. I could ignore redirects if that would help. I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. - I have additional data where I initially got the data from, mentioned in the BOTREQ. Ideally the death date column wouldn't include the age as it makes matching less effective. - I can easily use some regex to remove the template that gives the age (or just subst it and remove the age). Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement - harder to do automatically, though maybe possible in OpenRefine? ― Qwerfjkltalk20:42, 17 March 2022 (UTC)[reply]
clean up some existing Qs for the judge positions - not all existing positions link to their respective court Qid so to get the most out of the linked data, you may need to verify positions link to courts, have applies to jurisdiction values and other cleanup tasks to have consistent statements across the positions. I'm not aware of a model existing for judge positions, but basing off the example cited above it should be a good template of what statements should be on the judge's position.
I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. - One the postion held statements require a start time for context of period of time the person was in the role. Though start time is subjective possibly to different interpretation based on the job. Defining what is the start time for a judge and if it is the same or different from when they are confirmed. I'm talking more about how to represent the data. Without a start time the position statement is flagged as missing that qualifier unless the value is set to unknown or no value.
Ideally the death date column wouldn't include the age as it makes matching less effective. - This is more of a comment of table and data design than something hard to cleanup with regex or openrefine split column.
Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement The infoboxes (if accuracte) could be one source to extract the value or if you have another source at your disposal with this information. This was more of a comment comparing the table to what might be needed to make a more useful statement for the position. Really its not critical, but the more complete the statement the easier it is to query, walk through the links in either direction, visualize, etc. Wolfgang8741 says: If not you, then who? (talk) 20:57, 17 March 2022 (UTC)[reply]
@Wolfgang8741: I think I'm going to re-generate the table, using updated data, so all rows have a successor. Then, I can get the predecessor, which is typically just above it in the infobox. I think I've created most of the positions needed. Can you see any that are missing? (I wrote a QuickStatements batch to create a few.) ― Qwerfjkltalk21:12, 22 March 2022 (UTC)[reply]
It would help to provide to link(s) to resources you want me to review. I believe you wanted me to look at batch 79292? I don't have anything to compare to for a complete list off hand and courts are not my area of expertise. Format wise for the positions, it would be useful given the defined boundaries to add the position's the jurisdiction with P1001 as well as which court the position is affiliated via P361 of which court ie Q111295760 is part of Q7889771. A query for the list of courts to be part of: https://w.wiki/4yjB When you have the position statements ready, I'll check them out too. — Preceding unsigned comment added by Wolfgang8741 (talk • contribs) 21:43, 22 March 2022 (UTC)[reply]
No, the US is too broad for jurisdiction as these courts either have jurisdiction of an entire state's geographic area or sub region of a state's geographic area. An example would be the Q111295760 the first sentence states the jurisdiction to the entire state of Delaware https://en.wikipedia.org/wiki/United_States_District_Court_for_the_District_of_Delaware and appeals to the 3rd circuit as this map shows (not sure if this is most current, but it would be a guide on what Qids might be named or need to be created). While in this case I think the jurisdiction and state area are the same it probably requires a separate Qid to represent the jurisdiction that is equivalent in area to the state of Delaware as it is instance of a jurisdiction rather than instance of a state (so the concepts are similar, but different on type). An example of a jurisdiction only of a portion of a state is the Western District of Washington Q111295799 which would be a part of the state of Washington and a second Qid would represent the Eastern District of Washington. The development of the model for representing the jurisdictions may be better suited for the Wikidata Project Chat discussion.
There would be a relation between the jurisdiction and the state as part of the state of Delaware with different Qids, instance of, and description similar to how electoral districts are sub components of the state, but part of the state. This is where creating new positions have a lot of inter dependencies and deciding how to model can enable teasing out the differences between concepts with the same name, but in doing so allows for much richer queries once the Qids exist. New Qid for the district jurisdictions would probably be an instance of Q5982983 or a subclass of this to specify US district jurisdictional areas as a group or something like this. You might query the instances of this Qid to find what jurisdictions exist and for those that do not, create the Qid for each of the district areas as Q5982983 named the same as Q7889771 (United States District Court for the District of Delaware), but has an instance of Q5982983 or a subclass of Q5982983 being "United States District Court Jurisdiction" which would allow for alternative naming of the jurisdictions as "District of Delaware" with description "jurisdiction of the District Court. I was thinking of the jurisdictions to be modeled similarly to how electoral districts ie Q192611 and modeled, but it may be this concept needs more eyes and would benefit from a modeling discussion on the Wikidata project chat or related Wikidata project. This all said, if this is getting too complex, the jurisdiction can be left off for a later person to complete or put on hold to further discuss how to model them. — Preceding unsigned comment added by Wolfgang8741 (talk • contribs) 01:32, 24 March 2022 (UTC)[reply]
I've granted page mover per your request at WP:PERM; guidelines for usage of the right are found at Wikipedia:Page mover. If you have any questions, or in the future decide that you do not intend to use the tool, you can contact me or any other administrator. Hog FarmTalk20:15, 17 May 2022 (UTC)[reply]
You tagged this category for deletion but it still has 68,291 pages in it so I'm going to remove the tag. The category has to be emptied first and I think you need help from an admin who closes CFD cases for this one. LizRead!Talk!03:48, 19 May 2022 (UTC)[reply]
At the time of the last newsletter (No.26, September 2021), the backlog was 'only' just over 6,000 articles. In the past six months, the backlog has reached nearly 16,000, a staggering level not seen in several years. A very small number of users had been doing the vast majority of the reviews. Due to "burn-out", we have recently lost most of this effort. Furthermore, several reviewers have been stripped of the user right for abuse of privilege and the articles they patrolled were put back in the queue.
Several discussions on the state of the process have taken place on the talk page, but there has been no action to make any changes. The project also lacks coordination since the "position" is vacant.
In the last 30 days, only 100 reviewers have made more than 8 patrols and only 50 have averaged one review a day. There are currently 803 New Page Reviewers, but about a third have not had any activity in the past month. All 855 administrators have this permission, but only about a dozen significantly contribute to NPP.
This means we have an active pool of about 450 to address the backlog. We cannot rely on a few to do most of the work as that inevitably leads to burnout. A fairly experienced reviewer can usually do a review in a few minutes. If every active reviewer would patrol just one article per day, the backlog would very quickly disappear.
If you have noticed a user with a good understanding of Wikipedia notability and deletion, do suggest they help the effort by placing {{subst:NPR invite}} on their talk page.
If you are no longer very active on Wikipedia or you no longer wish to be part of the New Page Reviewer user group, please consider asking any admin to remove you from the list. This will enable NPP to have a better overview of its performance and what improvements need to be made to the process and its software.
To opt-out of future mailings, please remove yourself here. Sent 05:18, 23 May 2022 (UTC)
Wikidata weekly summary #521
Here's your quick overview of what has been happening around Wikidata over the last week.
6 and 8 June: Scholia hackathon with focus on software-related visualizations and curation workflows
29 July 2022: The submission deadline for the Wikidata Workshop 2022 that will be co-located with the 21st International Conference on Semantic Web (ISWC 2022).
Interrogating linked open data and Wikidata with SPARQL Lorenzo Losa - YouTube
Tool of the week
LOD4Culture is a web application for exploring world-wide cultural heritage.
Other Noteworthy Stuff
UNLOCK, a Wikimedia Deutschland program, is looking for your project ideas. These could be the development of tools building on top of Wikidata's data, of applications for social and public good or related to civic tech. Apply until May 29th, 2022!
Wikibase REST API: Initial implementation of a route providing all statements of an item (phab:T305988), an a route to retrieve a single statement (phab:T307087) completed.
First batch of WBstack.com accounts successfully migrated to Wikibase.cloud. You can keep track of our progress on this phabricator ticket phab:T303852.
Lexicographical data: We updated the input placeholders on the new version of the NewLexeme special page (T302877, T307443). We finished the feature to prefill the inputs from URL parameters if present (T298154) and to suggest common lexical category items (T298150). We are working on some accessibility improvements (T303806, T290733, T305359) and improving validation / error messages (T305854).
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Administrators using the mobile web interface can now access Special:Block directly from user pages. [1]
The Growth team maintains a mentorship program for newcomers. Previously, newcomers weren't able to opt out from the program. Starting May 19, 2022, newcomers are able to fully opt out from Growth mentorship, in case they do not wish to have any mentor at all. [3]
Some editors cannot access the content translation tool if they load it by clicking from the contributions menu. This problem is being worked on. It should still work properly if accessed directly via Special:ContentTranslation. [4]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 May. It will be on non-Wikipedia wikis and some Wikipedias from 25 May. It will be on all wikis from 26 May (calendar).
Future changes
Gadget and user scripts developers are invited to give feedback on a proposed technical policy aiming to improve support from MediaWiki developers. [5]
Would you mind reversing this closure? Per WP:BADNAC, A non-admin closure is not appropriate [... when] the outcome is a close call (especially where there are several valid outcomes) or likely to be controversial. Such closes are better left to an administrator. That argument seems to apply here. * Pppery *it has begun...15:44, 25 May 2022 (UTC)[reply]
Sorry, that was my mistake (I was only intending to challenge the no consensus closures, not the earlier relisting I conflated them with). For what it's worth I don't think the relisting there accomplished anything either, but that's water under the bridge now. * Pppery *it has begun...15:55, 25 May 2022 (UTC)[reply]
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator. scope_creepTalk15:46, 25 May 2022 (UTC)[reply]
I don't think you can find an admin who will delete a full category based on a CSD tag. All of the contents of this category need to be recategorized first to the new category, prior to this page being deleted. But you should be familiar with this process since you regularly close CFD discussions now so I'm a little bit confused by your request. LizRead!Talk!19:56, 25 May 2022 (UTC)[reply]
Hi Liz, the pages can't be recategorised because it is the category page; it needs to be deleted so that the other category can be moved in its place. On second thoughts, a round-robin move might have simplified this. ― Qwerfjkltalk20:20, 25 May 2022 (UTC)[reply]
IMHO it would also be appropriate for you to state your rationale for merging to only one parent, as suggested by User:Zxcvbnm, rather than to all parents, as suggested by me.
I have no objection to you processing CFDs manually, as you are leaving a clear edit summary, but feel free to list them instead at WT:CFDW, so that an admin can then feed the donkey work to a bot. – FayenaticLondon09:55, 30 May 2022 (UTC)[reply]
@Fayenatic london, Looking at it again, if there is consensus to keep Works set on fictional X, then the categories should probably have upmerged to both. I'll fix the closing statement and upmerge to the other categories based on my contributions, though it'll take a while - some of those categories had over 400 pages. It's mostly easier to manually process them, as with Cat-a-lot I can manage <90 pages in about 20 seconds, so it's easier, although any more than that and I have to wait another minute to avoid the rate limit. Once I remove d ~1300 pages from a category, and that took around half an hour. ― Qwerfjkltalk11:12, 30 May 2022 (UTC)[reply]
Thanks. Don't feel you have to do that just because I asked, though. There was some weight against my suggestion, and you may be able to find consensus for a single upmerge... but if so, the justification should be documented.– FayenaticLondon12:55, 30 May 2022 (UTC)[reply]
Next Linked Data for Libraries LD4 Wikidata Affinity Group call May 31, 2022: Felicia Smith, Nicole Coleman, and Akosua Kissi on the Know Systemic Racism Project Agenda
Want to know more about Abstract Wikipedia & Wikifunctions? You can now subscribe to the weekly newsletter and get a friendly reminder every time a new issue is published!
Radioactivity map: Mind map about radioactive radiation built by importing from Wikidata with InfoRapid KnowledgeBase Builder
Wikibase REST API: Expanding statement reading routes (a single statement specified by ID (phab:T307087), all statements of an item (phab:T305988), a single statement for a specific item (phab:T307088))
Fetch revision metadata and entity data separately in all use cases (phab:T307915, decision)
Update installation instructions in WikibaseLexeme.git readme file (phab:T306008)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
In the AbuseFilter extension, an ip_in_ranges() function has been introduced to check if an IP is in any of the ranges. Wikis are advised to combine multiple ip_in_range() expressions joined by | into a single expression for better performance. You can use the search function on Special:AbuseFilter to locate its usage. [7]
The IP Info feature which helps abuse fighters access information about IPs, has been deployed to all wikis as a beta feature. This comes after weeks of beta testing on test.wikipedia.org.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 May. It will be on non-Wikipedia wikis and some Wikipedias from 1 June. It will be on all wikis from 2 June (calendar).
Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 31 May at 07:00 UTC (targeted wikis).
The New Topic Tool will be deployed for all editors at most wikis soon. You will be able to opt out from within the tool and in Preferences. [8][9]
The list=usercontribs API will support fetching contributions from an IP range soon. API users can set the uciprange parameter to get contributions from any IP range within the limit. [10]
A new parser function will be introduced: {{=}}. It will replace existing templates named "=". It will insert an equal sign. This can be used to escape the equal sign in the parameter values of templates. [11]
Hey! Your bot's Task 10 (converting source to syntaxhighlight), understandably, missed a lot of .js and .css pages due to protection. However, I've noticed that quite a lot of the remaining pages have no visible reason for not being edited. They also all seem to be related to documentation of js pages or of source code (E.g. 12345). Is there any reason these pages seem to have been heavily excluded from Task 10? Aidan9382(talk)14:53, 31 May 2022 (UTC)[reply]
Rerun might be worth it. I didn't even think of {{#tag:source}}. If its fine according to the bot rules, then I think a rerun with #tag could help clear out the last of the fixable (I'm not gonna try clear the category further than that, I don't think an interface admin would be happy to wake up to 400 edit requests ). Aidan9382(talk)17:25, 31 May 2022 (UTC)[reply]
Yeah thats alright. If you are gonna use it on an interface admin's account, I'd make sure to be safe you dont overwrite anything thats simply picked up on accident (E.g. a script designed to remove source tags), cause the MW software detection for use of the source tag is fucking ass (At least it was with the enclose attributes on syntaxhighlight which I also cleared recently). The only way to fix that is to add //<nowiki> on the first line and //</nowiki> on the last line (Like here).
I'll also note that most of the errors seem to be by the user scripts, for whatever reason, have // <source lang="javascript"> in them, probably copied wrong. At that point, removing may be a better take. Idk. Other than that though, should be all ok. Aidan9382(talk)17:51, 31 May 2022 (UTC)[reply]
Thanks, I appreciate it. I did notice some 100 pages got removed from the category yesterday, and theres another 100 gone today. (Don't worry: I'll manually clear whatever's left). Thanks! Aidan9382(talk)05:12, 11 June 2022 (UTC)[reply]
Hi Qwerfjkl :) I'm not new exactly but I'm new to using Special:Homepage... how are you using it, how are you finding the mentorship process? --– SJ +18:43, 1 June 2022 (UTC)[reply]
Administrators using the mobile web interface can now access Special:Block directly from user pages. (T307341)
The IP Info feature has been deployed to all wikis as a Beta Feature. Any autoconfirmed user may enable the feature using the "IP info" checkbox under Preferences → Beta features. Autoconfirmed users will be able to access basic information about an IP address that includes the country and connection method. Those with advanced privileges (admin, bureaucrat, checkuser) will have access to extra information that includes the Internet Service Provider and more specific location.
Hello My name is Jules Lee. I need help funding my beautiful curtains that I have designed. People are going to love the curtains that I have designed. Thank you in Advance for your help. --ModernCurtains (talk) 17:23, 6 June 2022 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 June. It will be on non-Wikipedia wikis and some Wikipedias from 8 June. It will be on all wikis from 9 June (calendar).
Lexicographical data: We finished work on input validation and displaying errors for faulty input (phab:T305854) and are continuing work on accessibility improvements such as screen reader support and keyboard navigation (phab:T290733, phab:T30535).
REST API: We finished implementation of conditional statement requests (phab:T307031, phab:T307032) and published the OpenAPI specification document (still subject to change as the API develops). We started working on the write part of the API with adding statements to an Item (phab:T306667).
I'm uncertain about "moving" a category as the contents of the original category haven't been moved over yet. It's been sitting in a CSD category for a few hours now and I recommend contacting an admin who patrols CFD, like Fayenatic london, to handle this category. They do tricky category moves and sometimes it is faster to contact an experienced admin directly and request their help.
Also, Category:Cable game shows isn't empty yet so deleting this page would leave the pages it contains with red links which, according to WP:REDNO, has to be avoided. Once a category is emptied, I feel free to carry on with a CSD request. I've noticed that many admins who regularly patrol CSD categories avoid dealing with categories that have been tagged for deletion, even ones that are the result of a valid CFD close to "Delete". Just an observation. Thank you. LizRead!Talk!23:16, 8 June 2022 (UTC)[reply]
The article will be discussed at Wikipedia:Articles for deletion/Ashley Gjøvik until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
Next Linked Data for Libraries LD4 Wikidata Affinity Group call June 14, 2022: Will Kent (Wikidata Program Manager at Wiki Education) and Rosie Stephenson-Goodknight (Wikimedia Foundation Trustee; Visiting Scholar at Northeastern University; co-founder of Wiki Women in Red) will present on Leveraging Wikidata for Wikipedia – running a multi-language wiki project and the role of Wikidata in improving Wikipedia's content gender gap. Agenda
ExtraInterwiki. Some language links will never show up in your favorite Wikipedia, those who don’t have a corresponding article in this Wikipedia. This new tool aims to give them more visibility by searching topics closed to the one on an article with no article on your wiki.
Fixed a bug where Item IDs where shown instead of the label after selecting an Item in an Item selector (phab:T306214)
Lexicographical data: finished accessibility improvement for the new Special:New Lexeme page (phab:T290733), improving error messages for the new page (phab:T310134) and worked on a new search profile to make selecting languages easier (phab:T307869)
REST API: continued work on creating statements (phab:T306667)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 June. It will be on non-Wikipedia wikis and some Wikipedias from 15 June. It will be on all wikis from 16 June (calendar).
Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 14 June at 06:00 UTC (targeted wikis). [15]
Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Abkhazian Wikipedia, Achinese Wikipedia, Adyghe Wikipedia, Afrikaans Wikipedia, Akan Wikipedia, Alemannisch Wikipedia, Amharic Wikipedia, Aragonese Wikipedia, Old English Wikipedia, Syriac Wikipedia, Egyptian Arabic Wikipedia, Asturian Wikipedia, Atikamekw Wikipedia, Avaric Wikipedia, Aymara Wikipedia, Azerbaijani Wikipedia, South Azerbaijani Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [16]
The New Topic Tool will be deployed for all editors at Commons, Wikidata, and some other wikis soon. You will be able to opt out from within the tool and in Preferences. [17][18]
Future meetings
The next open meeting with the Web team about Vector (2022) will take place today (13 June). The following meetings will take place on: 28 June, 12 July, 26 July.
Future changes
By the end of July, the Vector 2022 skin should be ready to become the default across all wikis. Discussions on how to adjust it to the communities' needs will begin in the next weeks. It will always be possible to revert to the previous version on an individual basis. Learn more.
Hello and welcome to the June 2022 newsletter, a quarterly digest of Guild activities since April 2022. Don't forget you can unsubscribe at any time; see below.
Blitz: of the 16 editors who signed up for our April Copy Editing Blitz, 12 completed at least one copy-edit, and between them removed 21 articles from the copy-editing backlog. Barnstars awarded are here.
Drive: 27 editors signed up for our May Backlog Elimination Drive; of these, 20 copy-edited at least one article. 144 articles were copy-edited, and 88 articles from our target months August and September 2021 were removed from the backlog. Barnstars awarded are here.
Progress report: As of 07:12, 14 June 2022 (UTC), GOCE copyeditors have completed 209 requests since 1 January and the backlog stands at 1,404 articles.
Election news: Nominations for our half-yearly Election of Coordinators continues until 23:50 on 15 June (UTC), after which, voting will commence until 23:59, 30 June (UTC). All Wikipedians in good standing (active and not blocked, banned, or under ArbCom or community sanctions) are eligible and self-nominations are welcomed.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Reidgreg, Baffle gab1978, Dhtwiki, Miniapolis and Tenryuu
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
If I need help about someone that is being dishonest in a conversation about keeping a misleading article and they are being extremely bad faith --SiERRa662 (talk) 16:03, 14 June 2022 (UTC)[reply]
Feedback request: Wikipedia policies and guidelines request for comment
Hey! Do you think you could double check what you have it set to make the redirects have? They have a large amount of spacing before the templates for no seemingly good reason (E.g. here). Thanks. Aidan9382(talk)16:06, 16 June 2022 (UTC)[reply]
(I washed my hands before typing this, so you should be safe.) I saw this edit where you added a {{Bare URL PDF}} to a talk page. I don't think that's right because 1) why mess with talk pages and 2) it adds the page to a category that says it's an article. Does that make sense to you? SchreiberBike | ⌨ 15:56, 17 June 2022 (UTC)[reply]