User talk:GeneralNotability/Archives/2022/December
 | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Administrators' newsletter – December 2022
News and updates for administrators from the past month (November 2022).
Administrator changes
Interface administrator changes
Guideline and policy news
- Consensus has been found in an RfC to automatically place RfAs on hold after one week.
- The article creation at scale RfC has been closed.
- An RfC on the banners for the December 2022 fundraising campaign has been closed.
Technical news
- A new preference named "Enable limited width mode" has been added to the Vector 2022 skin. The preference is also shown as a toggle on every page if your monitor is 1600 pixels or wider. When disabled it removes the whitespace added by Vector 2022 on the left and right of the page content. Disabling this preference has the same effect as enabling the wide-vector-2022 gadget. (T319449)
Arbitration
- Eligible users are invited to vote on candidates for the Arbitration Committee until 23:59 December 12, 2022 (UTC). Candidate statements can be seen here.
- The proposed decision for the 2021-22 review of the discretionary sanctions system is open.
- The arbitration case Reversal and reinstatement of Athaenara's block has been closed.
- The arbitration case Stephen has been opened and the proposed decision is expected 1 December 2022.
- A motion has modified the procedures for contacting an admin facing Level 2 desysop.
Miscellaneous
- Tech tip: A single IPv6 connection usually has access to a "subnet" of 18 quintillion IPs. Add
/64to the end of an IP in Special:Contributions to see all of a subnet's edits, and consider blocking the whole subnet rather than an IP that may change within a minute.
T-banned IP range won't stop
Hello GeneralNotability,
In this SPI discussion almost a year ago, which involved IP range User:2600:1004:B100:0:0:0:0:0/40, you said that you would be keeping an eye on the /40 - their behavior does not currently justify the collateral damage in blocking the /40, but if I do have to block it I will.
They've just posted this which is both a clear topic ban violation and, I feel, directly aimed at harassing me. Just over a month ago, they also popped up here to push the same conspiracy theory from the SPI (where two other editors who should definitely know better decided to indulge them).
Per this discussion at ANI, the user in question is well aware that their "broadly construed" topic ban extends to both "race" and "intelligence" and not just the conjunction of the two topics. In that discussion you commented WHOIS says the range in question is the /44, not the /40, not that that changes the collateral damage all that much, and I don't see any good options to narrow it down while still being effective. If you all trust the person behind the keyboard to abide by a broader TBAN, by all means try that. Otherwise, if this is going to turn into a long-term case of nibbling around the edges of whatever TBAN is imposed, I say just block the range and live with the collateral.
However, despite the apparent agreement that the latter course was the way to go, at that time no other admin stepped in to take you up on it and the discussion was archived without action.
If you'd prefer I take this back to ANI, I will do so. But I figured since you stated that you would take a personal interest in the matter it may be best to bring it here first. Cheers, Generalrelative (talk) 06:08, 1 December 2022 (UTC)
- I'm very disappointed that Generalrelative is determined to escalate this matter, but if he is determined to do that, so be it. I consider my comments here to be covered by WP:BANEX, particularly "Engaging in legitimate and necessary dispute resolution, e.g. addressing a legitimate concern about the ban itself", since in this discussion Generalrelative is requesting additional sanctions against me.
- A great deal has changed in the past few months. In particular, the discussions here and here demonstrate that the "conspiracy theory" for which I was topic banned is now being taken much more seriously. I urge both of you to especially read the discussion on Twitter, along with the related discussion on RationalWiki, because this is the best demonstration of how outside of Wikipedia more people have begun to understand what's going on. The person referred to in those discussions as "Kirkegaard" is the banned user Deleet; he gave his real name on his user page, so it is not outing to mention this.
- Notice his mocking reference to it as a "conspiracy theory" that his RationalWiki account is a parody. Generalrelative, this is most likely a reference to your own comments calling it that.
- Three years ago, what Deleet threatened to do was push Wikipedia's coverage of human intelligence topics to such an extreme position that it could no longer be taken seriously by the general public. This project has more or less succeeded now, as AndewNguyen described here. Just two months ago there was another troll account on these articles, Tristan albatross, which was evidently another account made by Deleet to gloat about this project's success. It was completely obvious that Tristan albatross wasn't a new user, but for some reason nobody showed any interest in determining who the master was.
- It's been over two years since I originally raised this issue. If I were making all of it up, do you think after all this time I would still be trying to get something done about it? If I were making it up, do you really think multiple other people would have independently reached the same conclusion in discussions where I wasn't involved? Deleet is making fools of us all, and Generalrelative, you've been unwittingly helping him.
- One last comment: if both of you could acknowledge what's actually been happening here since early 2020, and take whatever action it's appropriate to take about a banned user who is trying to destroy Wikipedia's credibility, I'm prepared to promise in return to stop editing in topics that are marginally related to the area of my topic ban. The reason I've been doing this is because it drives me crazy to see Deleet succeeding at this project, and getting away with it, and I'd have no reason to continue paying attention to these articles if that issue could be addressed. 2600:1004:B102:3157:19F1:799:70D7:C775 (talk) 07:19, 1 December 2022 (UTC)
- IP editor, let me put this bluntly: you are topic-banned. While you are correct that your comments here are subject to BANEX, nothing else you've done qualifies. I do not care what Twitter or RationalWiki (both awful places) have to say about your topic of choice, I do not care what other people may or may not be doing in the topic area, and I am not going to play the "if only you'd do X I would follow the rules" game. As my elementary school music teacher liked to say, "worry about you". If the circumstances surrounding you TBAN have changed, the correct response would have been to appeal it, not to ignore it. Also...the "I can't let (perceived opponent) get away with (thing)" and "I need to tell people THE TRUTH" mindsets are unhealthy and unconstructive; I've seen it in contentious topic areas, I've seen it from overeager vandalism patrollers, I've seen it in real life, and it is not gaining any sympathy from me. Since it's clear that you are going to continue to nibble at the edges of the topic ban despite clarification (as predicted by several people the last time this came up, I see), you are now siteblocked. GeneralNotability (talk) 01:48, 2 December 2022 (UTC)
Feedback request: Engineering and technology Good Article nomination
Your feedback is requested at Talk:Level Crossing Removal Project on a "Engineering and technology" Good Article nomination. Thank you for helping out!
You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name.
Message delivered to you with love by Yapperbot :) | Is this wrong? Contact my bot operator. | Sent at 10:30, 4 December 2022 (UTC)
Tech News: 2022-49
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
The Wikisources use a tool called ProofreadPage. ProofreadPage uses OpenSeadragon which is an open source tool. The OpenSeadragon JavaScript API has been significantly re-written to support dynamically loading images. The functionality provided by the older version of the API should still work but it is no longer supported. User scripts and gadgets should migrate over to the newer version of the API. The functionality provided by the newer version of the API is documented on MediaWiki. [1][2]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 December. It will be on non-Wikipedia wikis and some Wikipedias from 7 December. It will be on all wikis from 8 December (calendar).
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 00:39, 6 December 2022 (UTC)
IP unblock request
Huh? Templates inside unblock requests? That’s a new one. Sarrail (talk) 01:30, 6 December 2022 (UTC)
- Sarrail, can't say I've seen that before either. Oh well, they're still not getting unblocked anytime soon, even with that creativity. GeneralNotability (talk) 01:38, 6 December 2022 (UTC)
Koli editor?
Check the Koli revolts and Koli pirates articles. They have been created by a brand new user with 29 edits. I assume good faith but I am aware that there was a Koli editor blocked several times and you were involved in the discussion there as well. I thought I let you know, maybe it is of help. Paradise Chronicle (talk) 00:39, 7 December 2022 (UTC)
- Paradise Chronicle, you hate me, don't you...kidding. Yup, that's them, found and blocked a sleeper too. GeneralNotability (talk) 00:58, 7 December 2022 (UTC)
Bruh
I'm glad to know I was right to suspect something's off. LilianaUwU (talk / contribs) 00:39, 8 December 2022 (UTC)
- I'd wager that User:XavDaPlug belongs in the same drawer. OhNoitsJamie Talk 05:09, 8 December 2022 (UTC)
- CU evidence isn't particularly conclusive, but behaviorally this is a slam dunk (Tommy Chong, the town of Albert Lea, general writing style). Blocked. GeneralNotability (talk) 14:16, 8 December 2022 (UTC)
The Bugle: Issue CC, December 2022
|
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here.
If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 12:56, 9 December 2022 (UTC)
Tech News: 2022-50
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
- An A/B test has begun at 15 Wikipedias for DiscussionTools on mobile. Half of the editors on the mobile web site will have access to the Reply tool and other features. [3]
- The character
=cannot be used in new usernames, to make usernames work better with templates. Existing usernames are not affected. [4]
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 December. It will be on non-Wikipedia wikis and some Wikipedias from 14 December. It will be on all wikis from 15 December (calendar).
- The HTML markup used by DiscussionTools to show discussion metadata below section headings will be inserted after these headings, not inside of them. This change improves the accessibility of discussion pages for screen reader software. [5]
Events
- The fourth edition of the Coolest Tool Award will happen online on Friday 16 December 2022 at 17:00 UTC! The event will be live-streamed on YouTube in the MediaWiki channel and added to Commons afterwards.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 23:32, 12 December 2022 (UTC)
Speedy deletion of freddy 420 ashlyn mike
I'm ok with the article I attempted to write Being deleted as it didn't come out the way I wanted it to . Was just trying to make An wikipedia article for this girl named Ashlyn mike from new Mexico who met A tragic end .
By all means delete it . Freddy 420 (talk) 17:54, 11 December 2022 (UTC)
- Freddy 420, the problem is that your article was entirely copied word-for-word from other sources. That is a violation of the copyrights of those articles' authors and is the sort of thing that must be deleted in order to comply with Wikipedia's license rules. You are welcome to write the article again, just make sure you do so in your own words. GeneralNotability (talk) 22:50, 12 December 2022 (UTC)
So where would I go to create the article ? Freddy 420 (talk) 01:16, 13 December 2022 (UTC)
- Freddy 420, you are welcome to work on it in the same place you were before. GeneralNotability (talk) 02:16, 13 December 2022 (UTC)
For your consideration
Just wanted to make you aware. I'm not familiar with the situation but wanted to give you a heads up in the event any follow-up was required. Tiderolls 18:51, 15 December 2022 (UTC)
- Thanks Tide rolls. Just another LTA (Wikipedia:Sockpuppet investigations/Gustin Kelly), they like to pick on Malnadach, block 'em on sight. GeneralNotability (talk) 22:11, 16 December 2022 (UTC)
You've got mail
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.Doug Weller talk 18:35, 16 December 2022 (UTC)
Tech News: 2022-51
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Tech News
- Because of the holidays the next issue of Tech News will be sent out on 9 January 2023.
Recent changes
- On a user's contributions page, you can filter it for edits with a tag like 'reverted'. Now, you can also filter for all edits that are not tagged like that. This was part of a Community Wishlist 2022 request. [6]
- A new function has been used for gadget developers to add content underneath the title on article pages. This is considered a stable API that should work across all skins. Documentation is available. [7]
- One of our test wikis is now being served from a new infrastructure powered by Kubernetes (read more). More Wikis will switch to this new infrastructure in early 2023. Please test and let us know of any issues. [8]
Problems
- Last week, all wikis had no edit access for 9 minutes. This was caused by a database problem. [9]
Changes later this week
- There is no new MediaWiki version this week or next week.
- The word "Reply" is very short in some languages, such as Arabic ("ردّ"). This makes the Discussion tools button on talk pages difficult to use. An arrow icon will be added to those languages. This will only be visible to editors who have the Beta Feature turned on. [10] [11]
Future changes
- Edits can be automatically "tagged" by the system software or the Edit filter configuration system. Those tags link to a help page about the tags. Soon they will also link to Recent Changes to let you see other edits tagged this way. This was a Community Wishlist 2022 request. [12]
- The Trust & Safety tools team have shared new plans for building the Private Incident Reporting System. The system will make it easier for editors to ask for help if they are harassed or abused.
- Realtime Preview for Wikitext is coming out of beta as an enabled feature for every user of the 2010 Wikitext editor in the week of January 9, 2023. It will be available to use via the toolbar in the 2010 Wikitext editor. The feature was the 4th most popular wish of the Community Wishlist Survey 2021.
Events
- You can now register for the Wikimedia Hackathon 2023, taking place on May 19–21 in Athens, Greece. You can also apply for a scholarship until January 14th.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 23:58, 19 December 2022 (UTC)
Contentious topics procedure adopted
You are receiving this message because you are subscribed to updates on the Arbitration Committee's discretionary sanctions review process.
The Arbitration Committee has concluded the 2021-22 review of the contentious topics system (formerly known as discretionary sanctions), and its final decision is viewable at the revision process page. As part of the review process, the Arbitration Committee has resolved by motion that:
The above proposals that are supported by an absolute majority of unrecused active arbitrators are hereby enacted. The drafting arbitrators (CaptainEek, L235, and Wugapodes) are directed to take the actions necessary to bring the proposals enacted by this motion into effect, including by amending the procedures at WP:AC/P and WP:AC/DS. The authority granted to the drafting arbitrators by this motion expires one month after enactment.
The Arbitration Committee thanks all those who have participated in the 2021-22 discretionary sanctions review process and all who have helped bring it to a successful conclusion. This motion concludes the 2021-22 discretionary sanctions review process.
This motion initiates a one-month implementation period for the updates to the contentious topics system. The Arbitration Committee will announce when the initial implementation of the Committee's decision has concluded and the amendments made by the drafting arbitrators in accordance with the Committee's decision take effect. Any editors interested in the implementation process are invited to assist at the implementation talk page, and editors interested in updates may subscribe to the update list.
For the Arbitration Committee, MediaWiki message delivery (talk) 21:47, 14 December 2022 (UTC)
Welcome to ArbCom
Congratulations on your success in the elections and welcome to the 2023 Arbitration Committee. This is the first part of your induction onto the Arbitration Committee.
Please use the EmailUser function to indicate:
- the email address you'd like to use for ArbCom and functionary business, and
- if you wish to assigned CheckUser and/or Oversight for your term.
Before you can be subscribed to any mailing lists or assigned CheckUser or Oversight permissions, you must sign the Wikimedia Foundation's confidentiality agreement for nonpublic information (L37) and the VRT users confidentiality agreement for nonpublic information (L45). Please confirm that your username is listed on the Access to nonpublic personal data policy/Noticeboard. If isn't, and you haven't signed the agreements, please do this promptly and let me know when you have signed them. Instructions for signing can be found here. Again, if you want CheckUser or Oversight permissions during your term, you must sign both agreements listed in the instructions. If you have signed but your username is not listed on the noticeboard, please let me know.
Over the coming days, you will receive a small number of emails as part of the induction process. Please carefully read them. If they are registration emails, please follow any instructions in them to finalise registration. You can contact me or any other arbitrator directly if you have difficulty with the induction process.
Thank you for volunteering to serve on the committee. We very much look forward to introducing ourselves to you on the mailing list and to working with you this term.
For the Arbitration Committee,17:26, 21 December 2022 (UTC)
Merry Christmas!
|
Merry Christmas, GeneralNotability/Archives/2022 |
|
Or Season's Greetings or Happy Winter Solstice! |
Happy holidays!
Happy Holidays and Happy New Year, GeneralNotability!
The other day, I was having a conversation with someone about holiday cards and social media. It occurred to me that, in the years since I left Facebook, the site I use most to communicate with people I like isn't actually a social media site at all. If you're receiving this, it's pretty likely I've talked with you more recently than I have my distant relatives and college friends on FB, at very least, and we may have even collaborated on something useful. So here's a holiday "card", Wikipedia friend. :) Hope the next couple weeks bring some fun and/or rest. — Rhododendrites talk \\ 18:42, 22 December 2022 (UTC)
Congrats on the cool tool award
Bullseye really is a cool tool. Your win is well deserved. Just don't forget us little people now that you've gone big time. Best, Barkeep49 (talk) 19:01, 16 December 2022 (UTC)
- Thanks Barkeep49 :) GeneralNotability (talk) 23:17, 16 December 2022 (UTC)
- Hi GeneralNotability, I'm from the Technical Engagement team, the organisers of Coolest Tool Award. Does Bullseye have a wiki homepage? We are placing award badges on tool homepages but couldn't find one for Bullseye. Kindly let me know. Thanks, and congrats! SSapaty (WMF) (talk) 13:41, 19 December 2022 (UTC)
- Hi SSapaty (WMF)! Bullseye does not currently have an on-wiki homepage, though I probably should get around to throwing one together one of these days. Thank you for your work organizing the award! GeneralNotability (talk) 20:57, 23 December 2022 (UTC)
- Hi GeneralNotability, I'm from the Technical Engagement team, the organisers of Coolest Tool Award. Does Bullseye have a wiki homepage? We are placing award badges on tool homepages but couldn't find one for Bullseye. Kindly let me know. Thanks, and congrats! SSapaty (WMF) (talk) 13:41, 19 December 2022 (UTC)
Seasons Greetings
|
Whatever you celebrate at this time of year, whether it's Christmas or some other festival, I hope you and those close to you have a happy, restful time! Have fun, Donner60 (talk) 00:16, 23 December 2022 (UTC)}} | 
|
Happy Holidays!
.jpg)
.jpg)
Hello GeneralNotability : Enjoy the holiday season and winter solstice if it's occurring in your area of the world, and thanks for your work to maintain, improve and expand Wikipedia. Cheers, RV (talk) 15:51, 25 December 2022 (UTC)
,_cropped.jpg)