User talk:0xDeadbeef

en:User:Meaghan/Sunshine

Hello, I'm 0xDeadbeef!

Feel free to ping me in reply to any comment made by me.

Administrators: if you disagree with any of my actions, please leave a talk page message and discuss with me here before reverting.

Discussion at User talk:Σ § total number of archived discussions

 You are invited to join the discussion at User talk:Σ § total number of archived discussions. —usernamekiran (talk) 05:17, 9 February 2025 (UTC)

I have updated the code, but it needs testing. —usernamekiran (talk) 05:17, 9 February 2025 (UTC)

@Usernamekiran: I will take a look later, but could you make it so that the original source code is there first and then your modifications can appear as a diff, so it is easier to apply? Thanks. 0xDeadbeef→∞ (talk to me) 15:36, 9 February 2025 (UTC)

I'm on mobile. Not to be rude, but cant you do such a simple thing by yourself? Just wondering. —usernamekiran (talk) 21:43, 10 February 2025 (UTC)

Hello. I saw my message again today, and now it looks very rude (it didnt seem that way while typing). I didnt mean to sound that way. Apologies for that. See you around —usernamekiran (talk) 12:26, 17 February 2025 (UTC)

Hey, no worries. I'll try to get to it when I notice it and have some time to process it. Let me know in a week if I don't get to it again. 0xDeadbeef→∞ (talk to me) 14:45, 17 February 2025 (UTC)

user:蒙古天骄

After your warning, this user still went on Special:Diff/1277698372, with an attitude of IDHT. Maybe a block is warrent? -Lemonaka 06:41, 26 February 2025 (UTC)

If I were you, I would just ignore that comment. I currently don't see anything that warrants a block right now. Let me know if they continue to harass you, though. 0xDeadbeef→∞ (talk to me) 11:56, 26 February 2025 (UTC)

You are right, this one is roped himself. -Lemonaka 10:47, 2 March 2025 (UTC)

CheckUser appointment, March 2025

The Arbitration Committee is pleased to appoint the following user to the CheckUser team following private and public consultation:

• 0xDeadbeef (talk · contribs · deleted contribs · logs · filter log · block user · block log)

The Committee thanks everyone who participated and helped bring this process to a successful conclusion.

On behalf of the Arbitration Committee, Sdrqaz (talk) 02:36, 7 March 2025 (UTC)

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § CheckUser appointment, March 2025

Hello, 0xDeadbeef,

Congratulations on your new appointment! Liz ^{Read! Talk!} 02:41, 7 March 2025 (UTC)

Hi Liz, a belated congrats on getting elected to ArbCom! I don't follow the enwiki ArbCom stuff closely.. I hope you're finding the ArbCom work enjoyable :) 0xDeadbeef→∞ (talk to me) 11:12, 13 March 2025 (UTC)

Abuse from sockpuppet

Thank you for blocking User:ZombieBruce. I have now been subjected to abuse from User:2402:4000:1257:FF56:9C88:3067:B18C:2BF [1]. Would you be able to block them too? The abuse is very similar to the abuse I received from another of the sockpuppets[2], which clears up any doubt about the sockpuppetry. Southdevonian (talk) 12:50, 7 March 2025 (UTC)

Has been dealt with. 0xDeadbeef→∞ (talk to me) 11:13, 13 March 2025 (UTC)

Requesting more info for CU

Hey! When you request more info for CU, you can update the status of the case to "Requested more info for CU". This is one of the options in the SPI script. See [3]. Best, MarioGom (talk) 16:55, 8 March 2025 (UTC)

Yes, I will do that next time. Thanks for the reminder! 0xDeadbeef→∞ (talk to me) 11:59, 11 March 2025 (UTC)

Ania

@0xDeadbeef we have another sock for the Ania case I opened earlier. Name is Editors6000 Insanityclown1 (talk) 02:27, 16 March 2025 (UTC)

Resolved. 0xDeadbeef→∞ (talk to me) 02:55, 16 March 2025 (UTC)

Error in Toolforge Code

Hi, I see that you may be consulted in place of User:Σ regarding the following error I just got when accessing the following URL: https://sigma.toolforge.org/usersearch.py?page=Things_as_They_Are;_or,_The_Adventures_of_Caleb_Williams&server=enwiki The response I got was the following: Traceback (most recent call last):

 File "/workspace/app.py", line 33, in inner
   return func(*a, **kw)
          ^^^^^^^^^^^^^^

TypeError: Index.usersearch_py() got an unexpected keyword argument '_or,_The_Adventures_of_Caleb_Williams'

This was on a page with the http response code of 500. Hopefully you can fix this. Thanks, Alan W (talk) 05:21, 16 March 2025 (UTC)

(not deadbeef) Does this link work for what you need? https://sigma.toolforge.org/usersearch.py?page=Things_as_They_Are%3b_or,_The_Adventures_of_Caleb_Williams&server=enwiki REAL_MOUSE_IRL talk 10:21, 16 March 2025 (UTC)

Thank you, REAL_MOUSE_IRL! Aha, URI encoding solves the problem (I understand something about these things, as it relates to my work). It most certainly does work with the "%3b" for the ";". Until this is fixed, now I can see a workaround for these things in the future. I appreciate your jumping in here. --Alan W (talk) 00:49, 17 March 2025 (UTC)

This doesn't seem to be a workaround but an actual fix for your problem. As per StackOverflow it is probably intended to parse a ';' as a separator for params. So you will need to use URI encoding from now on. 0xDeadbeef→∞ (talk to me) 06:40, 17 March 2025 (UTC)

non dead or non beef members of the project are equally welcome to chime in on my talk page :) 0xDeadbeef→∞ (talk to me) 06:39, 17 March 2025 (UTC)

Ah, 0xDEADBEEF themself has come alive :-) Well, the way I look at this, it is not a fix. The unsuspecting user on the "View history" page of Things as They Are; or, The Adventures of Caleb Williams clicks Find edits by user, and Bam! that error. You have to know about this workaround and apply it in the URL to get the Toolforge script to work. So, as I see it, this is a workaround, not a full fix. Not that I am not grateful to REAL_MOUSE_IRL for having provided it. It will do if I find links like this don't work in the future. --Alan W (talk) 00:16, 18 March 2025 (UTC)

I'll note that the URL encoding is applied for you if you use the form at https://sigma.toolforge.org/usersearch.py, so this would be an issue with the "external tools" link bar, not the tool itself. Adding an unencoded semicolon in the middle of a URL param will break any website AFAIK.

(I'll also note DEADBEEF's pronouns are listed as they/them) REAL_MOUSE_IRL talk 00:58, 18 March 2025 (UTC)

OK, then the issue is with the "external tools" link bar. But there is an issue. I can certainly understand that unencoded semicolons would cause a problem. A true fix for that link bar would be to encode as necessary any URL that is passed to the tool. How that would work, exactly, I do not understand enough to suggest. --Alan W (talk) 03:11, 18 March 2025 (UTC)

The external tools bar doesn't encode semicolons. I'll look into ways to fix it on the usersearch.py tool side. Which will take a moment. 0xDeadbeef→∞ (talk to me) 09:15, 18 March 2025 (UTC)

I imagine "moment" is an understatement, but I wasn't trying to rush you. I just appreciate that you are going to look into this at all. A fix, however managed, will benefit all unsuspecting users who might bump up against the same obstacle. --Alan W (talk) 23:30, 18 March 2025 (UTC)

Tech News: 2025-12

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs a datacenter server switchover, redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. Thanks to the Listen to Wikipedia tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can read more about the background and details of this process on the Diff blog. If you want to keep an ear out for the next server switchover, listen to the wikis on March 19 at 14:00 UTC.

Updates for editors

• The improved Content Translation tool dashboard is now available in 10 Wikipedias and will be available for all Wikipedias soon. With the unified dashboard, desktop users can now: Translate new sections of an article; Discover and access topic-based article suggestion filters (initially available only for mobile device users); Discover and access the Community-defined lists filter, also known as "Collections", from wiki-projects and campaigns.
• On Wikimedia Commons, a new system to select the appropriate file categories has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard.
• The Community Tech team is seeking wikis to join a pilot for the Multiblocks feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the project talk page.
• Starting March 25, the Editing team will test a new feature for Edit Check at 12 Wikipedias: Multi-Check. Half of the newcomers on these wikis will see all Reference Checks during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented on Phabricator. [4]
• The Global reminder bot, which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the listing of existing translations and documentation to check if their language needs updating or creation.
• The GlobalPreferences gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [5]
• View all 26 community-submitted tasks that were resolved last week. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [6]

Updates for technical contributors

• Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues please report them. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:45, 17 March 2025 (UTC)

Logging articletitles with sections that can't be archived

I was talking with @Wizmut: and it would be helpful to us if Lowercase sigmabot III would log the titles of the articles that contain sections that cannot be archived (due to a missing/malformed timestamp). Would you be so kind to implement that? Thanks! Polygnotus (talk) 01:47, 18 March 2025 (UTC)

For reference these talk pages contain examples of topics that sigma is ignoring:

https://en.wikipedia.org/wiki/Talk:Wolf_Blitzer

https://en.wikipedia.org/wiki/Talk:Gandhara

https://en.wikipedia.org/wiki/Talk:Robin_(character)

https://en.wikipedia.org/wiki/Talk:Epinephrine_autoinjector

https://en.wikipedia.org/wiki/Talk:Peter_Singer - contains an intentionally unsigned notice

https://en.wikipedia.org/wiki/Talk:Prom

https://en.wikipedia.org/wiki/Talk:Ne-Yo

https://en.wikipedia.org/wiki/Talk:History_of_Scouting_America

I can provide more... Wizmut (talk) 02:10, 18 March 2025 (UTC)

I'm more of a passive maintainer for these tools, because I'm not the most experienced programmer in Python. However I do try to get fixes in. This looks like something that would be really helpful, but implementing that is on a lower priority than most of the things on my to-do list so.. I'll get it done some time before June this year maybe? 0xDeadbeef→∞ (talk to me) 09:16, 18 March 2025 (UTC)

Is there someone else we should ask? I can also make 64k api calls but I would prefer to not do that. And what do you think about adding a template/magicword like {{do not archive this section}}? Polygnotus (talk) 16:54, 18 March 2025 (UTC)