Jump to content

User talk:Xaosflux: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Tag: Reverted
Line 27: Line 27:


:You block there stands, as you are being disruptive. If you want to appeal in 6 months, you may ask once on another project (such as here), do not otherwise follow admins around to other projects about it. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 14:07, 18 November 2022 (UTC)
:You block there stands, as you are being disruptive. If you want to appeal in 6 months, you may ask once on another project (such as here), do not otherwise follow admins around to other projects about it. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 14:07, 18 November 2022 (UTC)

Xjvxigckgchoc [[User:Калмыки патриоты России|Калмыки патриоты России]] ([[User talk:Калмыки патриоты России|talk]]) 04:59, 4 February 2023 (UTC)


== Mail ==
== Mail ==

Revision as of 04:59, 4 February 2023


My PGP public key ID is 0x2F0E92637366A6A9, expand for key:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: Valid from:	2023-04-03 12:44
Comment: Type:	4,096-bit RSA (secret key available)
Comment: Usage:	Signing, Encryption, Certifying User-IDs
Comment: Fingerprint:	34D49230690769512E0054832F0E92637366A6A9


mQINBGQrAnQBEADxNwdru6BpewwiEZngz+fEeCfnv/HesnjV1CNNZi5IHQ4ExPJJ
9AIwNS30FvOdXIM2/R2NeHAAnksV/mxX4zdQM9S/jD1eF/bYnMUss3Kdx5KotZmU
3zwK/fhXtBwB3GNdy6qtDf3vUHeNV0LGN5XiE4GpjQ9wFUp1OdnPf6pNmIgJpm6y
/YmOixOs9CbY1o6dyHjjNb+RQHJrO5Arbe0lvyS5pm6SGVGWErk2gTu3XZ4fwdF7
3WarqcS9qzS94rr3kjV/SqQC9BaVit36HlQJU3qUmsY6eCr2LdyCj+FfpVr9T5fv
eUR3LnEz4kHBOEbOjfvNvxBQzurNf2EnuKWNADU/CyBrgqQH6sX0O/rNFo7oHdTJ
B6mvMGxqdVoYnXJ7jK7fPWaF3oWea6aFu2YpPZIndnAuWZXfoJY5/pJvcaNhTsi6
xnK7OKjDq21KdwX0/NGGSYaFjezdf6cXSrrpQE15f76LT5qSk1RbYH8W8ZVLKc59
4GAjnEZZDXOGYEBdJIoGHCdRwvvtH8MJqGeyAOB2xH0D+EhdrWkQIrfUMzAlzA6f
7UWsgchCTn7vl8uosd0LmH0u8wpy6MNVZc7nbqYJHT029BXclrlVtxtn73xhmzdj
n/N+TZy6xFCxd5maDgxikbN6GkPP8p7sJP6Ig0sr0DLt6Fm0If5HtAWpqQARAQAB
tB5YYW9zIEZsdXggPHhhb3NmbHV4QGdtYWlsLmNvbT6JAlEEEwEIADsCGwMFCwkI
BwICIgIGFQoJCAsCBBYCAwECHgcCF4AWIQQ01JIwaQdpUS4AVIMvDpJjc2amqQUC
ZCsDEQAKCRAvDpJjc2amqbPLEADqribQF33rfPJ8zhwGzAunZ9j76gS8UHQcbG//
ozQEfvC1GdZ2hazZxltQzbRh2s/4xbPjjL6TeO5s9IHAteZOl8CjahHLoTiSIDVK
JxlhadPQC8/He7EM42NV/zQUI3rWkwWc5ct+WaLkGthqB+vpKikZldxt/8Iyog2y
rS1Y2OqEnCw9SmDYQcrPgb+fqXWurRYddeyjdTAX+er/OoeOAb6CWiUw/FW58vie
uLU7TNTkz8NCPP7I+rIPWcckJOQ7pqcVOWZf3mgYhjbws+esjHpq6kHGW/VcjnLP
dqxtGIuGH0KCY1NSSsDyDXP5lHN+m2kY57CKvIpcMSemHVoq9ir2N+N6p7+EkplF
eMSL+V4WsR/zok2nliT74HOfUfzveNfJ23FHNY0uXCfJTPFL5CVqFPQJ3a2rnx8Q
//ciyltjrLQIEcApkyxkbwdxRj7VP2G0MYRmvq2gZdE1tk0mUOFAdvGLOwdWWk5Q
24gkQY2qpoTHYeD0jAXW4OJPtRcGMPrKTYmOOvQk4oLFkWCnf6tQjtxMg+4IIl8I
IhBD00n67e+r9S46h4ib+fAyVSBFtkV9O1KBlx4f7J6tGXVr5/gHhlwSJjMUxToj
Hg6MiCoJvdSGI8AK6PY23se0mY5AHS5+vcqCXfDXPsKYE3y1zbo4zczK1aPRRs4s
fru8wYkBIgQQAQgADAUCZCsE2gUDABJ1AAAKCRCXELibyletfB7zB/940yi/w244
UShVHtXOgJrI8l1yZacqZpU/ivFAKg+ThKzz6Tc8BKNjz5lnff66MzzxyHJ8DYlV
M3xL+3Q3x91bRnkK2ph/cFPeGT1UEi4DHtvwVKVghNF1SY28Gc9C4IG6p26eCeKD
Hl/c9jtVNb9+0vds9wTfuHkqp5AXPRjle6GXoT5x6r8A3SbtH1AmtbhQ2cxaRvHo
BasRiptKGflLzXv5Iq5VvSQuJ0WL3GCGjZx7VSgTxRhK/nbZbhNxs1dQTnXzXGMd
zClS7K0kEcg2BWa6LSfKauBTboc6T/xPIcuYOiGnjlHElQiPYiswCS/3JUcWxHgP
L7aiVEEFsoJUuQINBGQrAnQBEADuIsq4xCuXrwDy7aKJmPqcaK0i1R6sKyQu3DBd
UUXgHSr7qkU+M4+cjI4etdLR+MIp5hO2SVdJKUVku+MIdtI2KJn7ntvTdjqiVRKV
KHmybuWavH/Onx/6o9owqeT98RxmkbzFFPrVNqw0OnOUmkvMxGeyyHH2/rUULFyk
jhMtRuvFLSEvrtnEy4mpKXNNRVYWGDbM5K+4jsGyDVWyCXzOh7fo0ObN/e6Pf27M
Nvq+D/Q80qF9YL9kN3PSTpiYRspxJ2m5NT8A5sGW2mYbGwQxCCDGpeOZOnZUDQvz
sB8x+XcLk243pgXfJ/KXPVTCv7bVP49lLWxyYDqscAizhLzjWbrmtMP2t7yfeVVz
X80/eGCTNZTKQY7mquzVe4Z+9crSgjKjipgq/DFYeWUDHV5my8o91DnSiVVp9FW7
6vWP+osH25hXFLfpnfODuezykUBinKwkSjy6/q8fzvMAnYfuClkHC1sjz2PbM4ZT
YGVRzepebh217kensuuyDVV3suROgyNisUdulbZTIb5P0L4E2hsr1zilt+KGApni
HuwtVuoOOEGqkT8yd/94w76SCkkfGBeTs47vp7ebAZvYR30M7WF0wliteGGYGNIW
gu3XOqUXu5iAxACzHtuSR0kDfzRIYK8P2SvV6fi/D1uR9PxQST3OfgttrMhEwhsj
2ol12wARAQABiQI2BBgBCAAgAhsMFiEENNSSMGkHaVEuAFSDLw6SY3NmpqkFAmQr
AxgACgkQLw6SY3NmpqmCexAAmXGXSEbEBjy+MPU//bMMoPco4wkgvkgbfEwfGP0i
LNM+fhZ6gDy6FYzbv9MFiocCAKcAuLwMmgneqrcWlEk2S+KurYqSuyCV8xPlladB
itU81t0s/x3QhMcnRjj2Rp/fe8Zlnb0erybUlmbVwXcY7SrV7p3qdCYtnmTvPz8m
J/FOUcGGAdVkzVFnW11YbBhTgw5wvqRO8ukJKLMnngk6c2LWD+3c0KBmQGbio1Y5
NcDYDNCT8YYdji66BKPlFGsLHDnoYfD73okkqeKquYG67DIV0/OLTa/9kzaGX6Y5
BjJCMYTT1NaISIrjyiwmL64xgHVl5zDrMWArk/XNaDZskhTkHFZwgdUBnn3Bo7UU
afcqZuoExVkPVCSDdN+hm9ekjPLzsEtv7MtePH2o1asbJXp2GU7LpZnfApoEdMt5
JYnODUNNwDOR1/QB/Hv7FttS7RuJD+xpDvPj5i2OHJta6C4AUAy+BGak6YByTKo5
UsCVAOQ8WjYl1ntmXpqtVV6HlqqvvJf9OjtL767m4h97Q5Y48ccYlRpXqVS4XM0O
aWyRevm8HFd0s/Ags9fCpmFMyuVsUmla6ot7f4EVdUklo2d7+jPsBscMsm7OrlXU
fBe0Fv/SGRoB6z9jj4QgAsYdDCeOqPVNVvRHtEyl54VakLSyXD4LzjXuceh/XUXq
enU=
=Ike+
-----END PGP PUBLIC KEY BLOCK-----



My Talk Archives:
Archive-01 ~ Archive-02 ~ Archive-03
Archive-04 ~ Archive-05 ~ Archive-06
Archive-07 ~ Archive-08 ~ Archive-09
Archive-10 ~ Archive-11 ~ Archive-12
Archive-13 ~ Archive-14 ~ Archive-15
Archive-16 ~ Archive-17 ~ Archive-18
Archive-19 ~ Archive-20 ~ Archive-21
Archive-22 ~ Archive-23 ~ Archive-24
Archive-25 ~ Archive-26 ~ Archive-27
Archive-28 ~ Archive-29 ~ Archive-30
Archive-31 ~ Archive-32 ~ Archive-33
Archive-34 ~ Archive-35 ~ Archive-36
Archive-37 ~ Archive-38 ~ Archive-39
Archive-40 ~ Archive-41 ~ Archive-42
Archive-43 ~ Archive-44 ~ Archive-45
Archive-46 ~ Archive-47 ~ Archive-48


DB1729 watchlist

Hi Xaosflux. First I owe you a HUGE Thank You! for all your help with my watchlist. I was starting to get a little frustrated and I hope that did not come across as me being frustrated with you. I was trying to explain my rationale and evidence for why I believed it was categorization edits that was flooding my WL and causing all the problems. Turns out, that is precisely what it was. "Categorization changes" is a filter setting that was set to show categorization changes either by default or it was something I selected myself when I first setup my watchlist three years ago. Just now, by X'ing out that filter option, it ignored any categorization changes and instantly my watchlist returned to normal function!

I suppose the only problem that might remain is what if actually do want to see categorization changes without breaking my watchlist? But never mind that. I am happy I got my watchlist working normally and that I know now what was causing the problem this whole time. Mystery solved!

Thanks so much once again:) --DB1729talk 01:21, 18 November 2022 (UTC)[reply]

@DB1729 glad to hear it is working better for you now, didn't have a chance to get back to you there yet! It can be hard to help people in this area, because there are many many ways to change the watchlist display. I use the very-old style one on my usual account (Use non-JavaScript interface), I know it misses out on some of the fancier features, but it "just works" for my daily use. If you haven't lately, you may want to make a backup of your watchlist, go to Special:EditWatchlist/raw , copy all the text of the pages, and save it on your computer as a file. That way, if things get really messed up you can reset all your preferences, reset your watchlist and reload it from your saved list. Best regards, — xaosflux Talk 01:37, 18 November 2022 (UTC)[reply]
Good idea. I saved it as suggested. Thanks:) DB1729talk 04:28, 18 November 2022 (UTC)[reply]

Don't worry

Please unblock me in Meta-Wiki,I got your change to cannot edit own talk page ,In block log i soon this 13:58, 18 November 2022 Xaosflux talk contribs changed block settings for Mhab Zdan1 talk contribs with an expiration time of infinite (account creation disabled, email disabled, cannot edit own talk page) (repeated unconstructive unblock requests) Mhab Zdan1 (talk) 14:04, 18 November 2022 (UTC)[reply]

You block there stands, as you are being disruptive. If you want to appeal in 6 months, you may ask once on another project (such as here), do not otherwise follow admins around to other projects about it. — xaosflux Talk 14:07, 18 November 2022 (UTC)[reply]

Xjvxigckgchoc Калмыки патриоты России (talk) 04:59, 4 February 2023 (UTC)[reply]

Mail

Hello, Xaosflux. Please check your email; 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 remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

-- Colin°Talk 15:15, 21 November 2022 (UTC)[reply]

Replied via wikimail. — xaosflux Talk 21:50, 21 November 2022 (UTC)[reply]

Tech News: 2022-47

MediaWiki message delivery 23:20, 21 November 2022 (UTC)[reply]

Move to Draft:Sari Katha Article in Mainspace.

Sir, I request to you that I informed you that move to draft article on mainspace.it is ready for mainspace.Thanks you. Golmala (talk) 14:36, 22 November 2022 (UTC)[reply]

OK, I haven't worked on that article. — xaosflux Talk 16:04, 22 November 2022 (UTC)[reply]

You are amazing

I just looked at the history of Candidates/Guide, and it struck me just how much work you do behind the scenes to make Wikipedia happen. So, take this:

All Around Amazing Barnstar
For being quietly amazing. SilkTork (talk) 18:53, 23 November 2022 (UTC))[reply]

The Signpost: 28 November 2022

Tech News: 2022-48

MediaWiki message delivery 20:01, 28 November 2022 (UTC)[reply]

ArbCom 2022 Elections voter message

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:18, 29 November 2022 (UTC)[reply]

ArbCom 2022 Elections voter message

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:22, 29 November 2022 (UTC)[reply]

question regarding revdel

Hello. If you perform revdel, is that page added to your watchlist automatically by default? —usernamekiran (talk) 22:47, 29 November 2022 (UTC)[reply]

@Usernamekiran it shouldn't be. This is a little bit of a hard thing to test, because (a) it can only be done by admins, and (b) by the time an admin becomes an admin, they generally are far from using "default" settings. I did a quick test of make a page, revdel a version - it did not WL it for me, and it did not even have an option to WL it if I wanted to. — xaosflux Talk 23:50, 29 November 2022 (UTC)[reply]
yes, I tried it again on an non-watchlisted page, it wasn't added to the watchlist. A few days ago, I had rev-del'ed from two pages, which later showed up as temporarily watchlisted. I might have added them already. Sorry for the inconvenience —usernamekiran (talk) 00:17, 30 November 2022 (UTC)[reply]

You've got mail

Hello, Xaosflux. Please check your email; 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 remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template. Main focus talk (talk) 07:05, 30 November 2022 (UTC)[reply]
@Main focus talk that seems fine. It will be up to them now. — xaosflux Talk 10:24, 30 November 2022 (UTC)[reply]
@Xaosflux thank you so much for directing me.
The request was successful, and I am back into it.
It's the same acc I am replying right now.
Thank you once again!
Tumbuka Arch 19:17, 30 November 2022 (UTC)[reply]
@Tumbuka Arch good news! Be sure to keep your scratch codes safe, if you are ever in a situation where you may have to use them:
  • STOP EVERYTHING
  • DONT PROCEED UNTIL YOU ARE READY TO RECOVER
  • USE 1 TO LOGON
  • USE 1 TO DISABLE 2FA
You could also consider adding additional information that could be used to help identify you to developers/staff such as publishing a committed identity or a cryptographic public key, such as a OpenPGP one. Best regards, — xaosflux Talk 19:24, 30 November 2022 (UTC)[reply]
@Xaosflux Thanks for the advice.
Actually, I have kept the codes safe.
I am looking forward to add that commited Identity right now.
Thanking you for the good advice in the first place.
Thank you once again.
Thank you so much.
Tumbuka Arch 19:34, 30 November 2022 (UTC)[reply]

Administrators' newsletter – December 2022

News and updates for administrators from the past month (November 2022).

Administrator changes

readded
removed

Interface administrator changes

readded TheresNoTime
removed TheresNoTime

CheckUser changes

removed TheresNoTime

Oversight changes

removed TheresNoTime

Guideline and policy news

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

Miscellaneous


Meta Mass Message

Hello, I am currently trying to help Windblown29 with sending a mass message, but just so I don't get things wrong I was wondering if Special:MassMessage has the same interface on meta as it does here? Thanks, Terasail[✉️] 12:33, 3 December 2022 (UTC)[reply]

@Terasail yes, but there are special considerations on how a message and list must be formated if you are going to send it as a global MMS. See meta:MassMessage#Global_message_delivery. — xaosflux Talk 16:32, 3 December 2022 (UTC)[reply]
Ah I see, thanks for this. I was trying to explain the basics of mms from my experience and how they should appy for it, (they applied here when they wanted it on meta) I gave some links but missed that one so I just added it. Thanks, Terasail[✉️] 20:40, 3 December 2022 (UTC)[reply]

Zero!

Regarding this comment: zero, or zero factorial (that is, one)? ;-) isaacl (talk) 21:15, 3 December 2022 (UTC)[reply]

@Isaacl well, I didn't use "" ;) — xaosflux Talk 22:05, 3 December 2022 (UTC)[reply]

Just wondering…

…what upstream changes could replace the Synchbot process? –xenotalk 00:18, 4 December 2022 (UTC)[reply]

@Xeno from a technical perspective, this could be an extension. Operationally, such an extension could be used by stewards. Process-wise, some global policy to support it could be put in place (it has a fairly weak original historical support, but that has been strengthened in process by no one complaining about it). Currently, this is a house of cards built on pathoschild wanting to keep doing it for the most part. — xaosflux Talk 01:14, 4 December 2022 (UTC)[reply]
Ah, okay. Gotcha. Do you know if there's already a phab? –xenotalk 02:28, 4 December 2022 (UTC)[reply]
@Xeno, no it was brought up a couple of times (such as here and here) but never went anywhere. I think one reason is that there really isn't policy to support it (e.g. stewards are not suppose to act when local sysops are present) and it exists in a murky global IAR realm. — xaosflux Talk 04:09, 4 December 2022 (UTC)[reply]

Minor ce

Just a heads up, I edited your message at WP:VPT (Special:Diff/1125575324). I assume this is what you meant but since you wrote it and I didn't I thought you should know I changed it. Terasail[✉️] 19:12, 4 December 2022 (UTC)[reply]

@Terasail thank you, was just going back to fix that and EC'd you! — xaosflux Talk 19:13, 4 December 2022 (UTC)[reply]
@Terasail wait, no. I am specifically trying to say that we, the editors here on enwiki, can NOT change that ourselves.. — xaosflux Talk 19:15, 4 December 2022 (UTC)[reply]
Oh, yeah. My mistake, I saw the "can do anything about" and thought: "no we can't". Will make sure to double read next time. Terasail[✉️] 19:19, 4 December 2022 (UTC)[reply]

Tech News: 2022-49

MediaWiki message delivery 00:39, 6 December 2022 (UTC)[reply]

stupid question

Hi. I know this is a stupid question, but given complexities of policy, and odd circumstances: what would have happened if Fribbler had first made 100ish edits till 15 Dec, and made the re-sysop request after 100 edits? Or what if they make 100 edits in next two weeks, and make the request again? I didn't want to clutter BN with hypotheticals hence asking here. —usernamekiran (talk) 15:59, 6 December 2022 (UTC)[reply]

@Usernamekiran right now the only hold up I see is the "return to activity as an editor" convincing part. If they actually did return to editing, that should overcome that hurdle. The new 2023 policy doesn't prevent someone who was removed under criteria 2 from getting restored at BN. (If those edits were gamed, I wouldn't be convinced though). Also, there isn't a looming deadline, they could do that up until they hit the 5 year rule. — xaosflux Talk 16:08, 6 December 2022 (UTC)[reply]
yes. —usernamekiran (talk) 17:43, 6 December 2022 (UTC)[reply]

Unable to remove ArbCom Elections automated message despite having a template

Hello there. For the past two years, I kept getting an automated message to vote in the yearly ArbCom election despite having the "NoACEMM" template on my talk page. I noticed that the message sent was listed under your name using the list called Wikipedia:Arbitration Committee Elections December 2022/Coordination/MM/05. I'll like to know if there's something wrong with the placement of the template on my page or if there's some weird oversight on why I kept getting the automated message. If you can help, that'll be greatly appreciated. The Gamer 91 (talk) 22:04, 11 December 2022 (UTC)[reply]

Replied on your talk. — xaosflux Talk 22:37, 11 December 2022 (UTC)[reply]

Pronunciation

Hi xaosflux - I was communicating with another editor, and your name came up in reference to something we wouldn't need to do because you'd done it. However, this was overshadowed by a far more crucial issue: that we had each been confidently sure we knew how to pronounce your name since we'd been editing Wikipedia, and our two ways were different. So, tl;dr: how do you pronounce your username? Nosebagbear (talk) 23:39, 11 December 2022 (UTC)[reply]

@Nosebagbear I think this is the right markup: /ˈzeɪ.as.flʌks/. I'm not super picky since I rarely hear it aloud! — xaosflux Talk 23:55, 11 December 2022 (UTC)[reply]
(c.f. testwiki:User talk:Xaosflux/phonos). — xaosflux Talk 23:57, 11 December 2022 (UTC)[reply]
I didn't suspect three syllables. It was always just two in my head. SmokeyJoe (talk) 01:04, 12 December 2022 (UTC)[reply]
@SmokeyJoe think back in the day I derived it from the words "chaos" and "flux", and may have been inspired by the animated series Æon Flux. I've been called "Zous" by some. — xaosflux Talk 01:08, 12 December 2022 (UTC)[reply]
Don't worry about it, Joe. As a WP:Talk page stalker here, I thought it was just using the "X" for a Greek Chi and have always pronounced it as "Chaos Flux" in my head. TIL. VanIsaac, GHTV contWpWS 01:49, 12 December 2022 (UTC)[reply]
(That was my method, too, @Vanisaac!) :) Nosebagbear (talk) 10:09, 12 December 2022 (UTC)[reply]
Once we get the phonos extension installed, maybe we can make a new "hear my username" userbox! — xaosflux Talk 11:15, 12 December 2022 (UTC)[reply]

8TV (Malaysian TV network) needs to be protected from unregistered users

Hello there. I wanted to tell and concern about this. 8TV (Malaysian TV network) is suffering from vandalism and needs to be protected from the unregistered users because of the false information/gibberish into pages. There's no news about ceasing it's operation and it is proven to be false or just fake news. GlorysiaMelodyYT (talk) 10:16, 12 December 2022 (UTC)[reply]

Oh yeah, don't forget about 8FM, it is also suffered from vandalism before I undo it. GlorysiaMelodyYT (talk) 10:19, 12 December 2022 (UTC)[reply]
Third one: List of programmes broadcast by 8TV (Malaysian TV network) were also got hit, I trying to stop the vandalism but the unregistered users won't stop spreading fake news. GlorysiaMelodyYT (talk) 10:30, 12 December 2022 (UTC)[reply]
@GlorysiaMelodyYT Hello, to request a page be protected please post at Wikipedia:Requests for page protection. Best regards, — xaosflux Talk 11:14, 12 December 2022 (UTC)[reply]

Tech News: 2022-50

MediaWiki message delivery 23:33, 12 December 2022 (UTC)[reply]

What do you mean by that? As far as I can tell only interface admins have the right to implement my request because it requires editing CSS in someone else ("User:UBX")'s userspace, which uses the editusercss right, which per Special:ListGroupRights only iadmins have. * Pppery * it has begun... 16:44, 16 December 2022 (UTC)[reply]

@Pppery yes, the target of that probably should have been the userpage, not the template - it was showing up on the wrong report, looks like the entire thing has been speedily deleted now though so nothing to do. — xaosflux Talk 17:46, 16 December 2022 (UTC)[reply]

Tech News: 2022-51

MediaWiki message delivery 23:58, 19 December 2022 (UTC)[reply]

2FA security key

Hi - do you think this would be useful for my Google authenticator? Just in case? Don't want to loose access![19] Thanks. Doug Weller talk 15:55, 21 December 2022 (UTC)[reply]

I have two Yubikey 5's I use. -- Avi (talk) 16:11, 21 December 2022 (UTC)[reply]
@Avraham any idea what the difference is between the cheaper one that I linked and the one that you have? Thanks Doug Weller talk 16:30, 21 December 2022 (UTC)[reply]
See https://www.reddit.com/r/yubikey/comments/adzfqb/yubco_security_key_nfc_vs_yubikey_5_nfc/. The 5 has more methods. You could put GPG keys on it, for example. Or you could use the YubiAuth App with the key for TOTP (like Authy or Google Authenticator). -- Avi (talk) 11:38, 22 December 2022 (UTC)[reply]
@Doug Weller I don't recommend it here. From what I see that would mean you'd convert your 2FA from TOTP to WebAuthn; WMF has even less support for WebAuthn than for it's almost non-existent TOTP support system. There is currently no self-service recovery for WebAuthn failures. I use TOTP, and set it up on 2 devices, that way if one device fails I still have it on the other. The easiest way to do this is to register them both at the same time (turn off TOTP and set it up again). Additionally, ensuring that you safely store your scratch codes for TOTP is important. If your authentication device fails it can take up to 2 scratch codes to turn off 2FA until you can re-enroll. I have used some of the hardware keys with other systems, but they are ones where I register my real-world identity to them and have various built-in recovery mechanisms. — xaosflux Talk 17:07, 21 December 2022 (UTC)[reply]
I have two keys that I use for my FIDO2, including Wikipedia, and they work fine. But I have two in case I lose one. That's the downside of the increased security of a physical device: no virtual back door. I consider that a feature, not a bug. -- Avi (talk) 11:40, 22 December 2022 (UTC)[reply]
Thanks. I have my codes. It’s on my android phone so unless that dies before I replace it I can transfer it to a new phone. Doug Weller talk 17:10, 21 December 2022 (UTC)[reply]
@Doug Weller if you have a secure computer, you could also install a software TOTP client. It won't help in the "your computer was taken over" type of attack, but still provides multifactor security from external cracking. — xaosflux Talk 17:13, 21 December 2022 (UTC)[reply]
good idea I can add Google Authenticatior to Chrome.. Thanks. Doug Weller talk 17:19, 21 December 2022 (UTC)[reply]

2FA - 2 devices, 2 different OSs

Hello, Xaosflux! I wanted to write a question here but I got a notice saying it didn't get many watchers so I thought about asking you personally given that you had answered quite some questions there. (The question above me is also about 2FA. Strange coincidence...)
I use a PC and a laptop to edit Wikipedia. The PC uses Windows and the laptop is on Linux. I want to activate the 2 factor authorization but I'm not sure as to what would be the best way to act on this case. Do I really have to get 2 different groups of scratch codes by 2 different programs? Is there "a better way"? Sorry if I'm not clear. I'm a bit confused by the whole 2FA thing. — Klein Muçi (talk) 12:43, 22 December 2022 (UTC)[reply]

@Klein Muçi 2FA isn't related to the devices that you use to log on. 2FA (sticking to the TOTP model here) requires an authenticator, which is software that can take an initial secret seed, the time of day, and output a short-lived code. Most people that use our TOTP use a smartphone app as their authenticator. When you activate 2FA it will give you your initial registration seed, at that point you can use that seed to register multiple authentication devices (I use a software application on a trusted computer, and a software application on a smartphone). You shouldn't store that seed as it could be used to impersonate you. During registration you will get a set of scratch codes. These are attached to your account, not to your authenticator or any computer you log on to. They should be used only in the even of a broken authenticator, and only to unenroll from 2FA until you can set it up again. Does that answer your questions? — xaosflux Talk 14:06, 22 December 2022 (UTC)[reply]
To be 100% clear, you can never have "2 different groups of scratch codes"; the only way to get scratch codes is to activate 2FA, and the only way to get another set is to deactivate it (invalidating the old scratch codes) and reactivate it. There is not currently support to register multiple TOTP instances with different seeds and scratches. — xaosflux Talk 14:10, 22 December 2022 (UTC)[reply]
During registration you will get a set of scratch codes. These are attached to your account, not to your authenticator or any computer you log on to.
Aha! Okay then. That was my dilemma. Thank you! :)) — Klein Muçi (talk) 16:01, 22 December 2022 (UTC)[reply]

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)}} [reply]

Donner60 (talk) 01:41, 24 December 2022 (UTC)[reply]

Merry Christmas!

Hello, Xaosflux! Thank you for your work to maintain and improve Wikipedia! Wishing you a Merry Christmas and a Happy New Year!
CAPTAIN RAJU(T) 19:15, 25 December 2022 (UTC)[reply]

Spread the WikiLove and leave other users this message by adding {{subst:Multi-language Season's Greetings}}

Happy New Year, Xaosflux!

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Abishe (talk) 21:50, 31 December 2022 (UTC)[reply]

Happy New Year!

Send New Year cheer by adding {{subst:Happy New Year}} to user talk pages.
CAPTAIN RAJU(T) 22:14, 31 December 2022 (UTC)[reply]

Inactivity criterion 2 desysop notifications

Hi xaosflux. It would be best to use {{inactive admin 2}} instead of {{inactive admin}}. — JJMC89(T·C) 02:13, 1 January 2023 (UTC)[reply]

@JJMC89 thanks, good thing I'm doing these in batches! — xaosflux Talk 02:17, 1 January 2023 (UTC)[reply]

A barnstar for you!

The Admin's Barnstar
You deserve this barnstar because of your hard work at Wikipedia:Inactive administrators/2023. Great work! Sarrail (talk) 03:31, 1 January 2023 (UTC)[reply]
aand...

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Sarrail (talk) 03:34, 1 January 2023 (UTC)[reply]

The Signpost: 1 January 2023

Happy New Year

Wishing you a year filled with prosperity, happiness, and good health. Dr.Pinsky (talk) 12:23, 1 January 2023 (UTC)[reply]

Happy New Year, Xaosflux!

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Moops T 17:07, 2 January 2023 (UTC)[reply]

Suspension of my administrative permissions

Thank you for notifying me on my user talk page that my admin permissions have been suspended due to inactivity. Sadly, I have been too busy with other projects to do much Wikipedia editing in recent years. I still think Wikipedia is a great resource and a shining example of volunteer collaboration. Best wishes and Happy New Year.

--Sheldon Rampton Sheldon Rampton (talk) 19:42, 3 January 2023 (UTC)[reply]

Administrators' newsletter – January 2023

News and updates for administrators from the past month (December 2022).

Guideline and policy news

Arbitration

Miscellaneous

  • Voting for the Sound Logo has closed and the winner is expected to be announced February to April 2023.
  • Tech tip: You can view information about IP addresses in a centralised location using bullseye which won the Newcomer award in the recent Coolest Tool Awards.

Bureaucrat chat - invitation to participate

The RfA for MB has gone to a bureaucrat chat. Please join in the discussion. Primefac (talk) 15:02, 8 January 2023 (UTC)[reply]

Just a ping that I answered you at: https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia_talk:Text_of_the_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License&diff=1132579220&oldid=1132570362&diffmode=source although commenting on your discussion because we probably should move the discussion somewhere more centralized -so others can participate, too-, either on wiki or on Phabricator. :-) I pinged legal already and I am waiting for their advice, too on how flexible we can be. Regards, and thank you for answering! --JCrespo (WMF) (talk) 15:17, 9 January 2023 (UTC)[reply]

@JCrespo (WMF) thanks; are there other wikitext pages that are being monitored that may also need to be dealt with similarly? — xaosflux Talk 15:20, 9 January 2023 (UTC)[reply]
Let me check the code and will get back to you. --JCrespo (WMF) (talk) 15:22, 9 January 2023 (UTC)[reply]
As far as Mediawiki-content controlled pages for enwiki, I found only 2: check_legal_html!https://en.wikipedia.org/wiki/Main_Page and check_legal_html!https://en.m.wikipedia.org/wiki/Main_Page, and then wikibooks, aside. Only contents in MediaWiki:Wikimedia-copyright are checked(and the main page redirect should not be moved without also updating that code)- but after rendering into the Main page. We should wait for legal to answer first, maybe the check is not needed anymore in the current form. Or maybe we could change the alert to just check the links exist and that would give you more flexibility, rather than forcing you to notify us every time. --JCrespo (WMF) (talk) 15:38, 9 January 2023 (UTC)[reply]
@JCrespo (WMF) thanks, this seems somewhat useless if MediaWiki:Wikimedia-copyright being the same is enough, as it links to the actual license external from that page! (Either a local copy such as we have at Wikipedia:Text of the Creative Commons Attribution-ShareAlike 3.0 Unported License - and could just edit. Or completely outside of our control such as when it links to [20] and could be changed or corrupted there. — xaosflux Talk 15:43, 9 January 2023 (UTC)[reply]
I don't necessarily always understand the lawyer's requests, but I am sure to follow their advice to avoid legal problems. :-) My guess is that at some point in the past, the footer disappeared due to a software bug/html rendering issue and that could have had legal consequences for us. I believe things like the license and the privacy policy are important enough to merit alerting over not having them! I don't know the details- what I know is that we (system administrators) get an alert when the footer is edited and want to make that better for us, in the most reasonable manner possible! Our lawyers understand the wiki, and they will know the best way to keep things editable while minimizing risk, I have no doubt- this is not about closing up things! --JCrespo (WMF) (talk) 15:52, 9 January 2023 (UTC)[reply]
In any case, removing the alerts is one of the possible outcomes indeed, in which case you wouldn't be affected at all. --JCrespo (WMF) (talk) 16:01, 9 January 2023 (UTC)[reply]
I gave you a personal thank you, in addition to mentioning it publicly on the ticket, for your role giving feedback on how to improve this particular legal check. Regards. --JCrespo (WMF) (talk) 17:26, 12 January 2023 (UTC)[reply]

Tech News: 2023-02

MediaWiki message delivery 01:06, 10 January 2023 (UTC)[reply]

Add topic

Hi! When did you start to become an admin MintyEditor (talk) 05:47, 12 January 2023 (UTC)[reply]

In 2006. — xaosflux Talk 11:06, 12 January 2023 (UTC)[reply]

Feedback request: Wikipedia style and naming request for comment

Your feedback is requested at Talk:Andrew Tate on a "Wikipedia style and naming" request for comment. 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 16:30, 14 January 2023 (UTC)[reply]

Wikipedia:Bots/Noticeboard Accidental revert

My apology for reverting your edit as it had nothing to do with your change. I was trying to select the "diff" link on a page in my watchlist and I accidentally clicked the "revert" link on your edit instead. I undid the revert as soon as I realized what I had done. RedWolf (talk) 23:39, 15 January 2023 (UTC)[reply]

No worries, accidents happen. Cheers! — xaosflux Talk 23:40, 15 January 2023 (UTC)[reply]

The Signpost: 16 January 2023

Tech News: 2023-03

MediaWiki message delivery 01:08, 17 January 2023 (UTC)[reply]

The best dude 2023

I don't believe you actually processed the unblock for The best dude 2023. :) -- Yamla (talk) 16:15, 17 January 2023 (UTC)[reply]

@Yamla if I didn't make the block, I wouldn't have, and I don't have high hopes but figured a little WP:ROPE will tell. — xaosflux Talk 16:17, 17 January 2023 (UTC)[reply]
Sorry, I meant I believe that user is still blocked. You are of course welcome to lift the block, I just think you haven't done that yet. --Yamla (talk) 16:18, 17 January 2023 (UTC)[reply]
@Yamla oooooooo, thanks for that - done. — xaosflux Talk 16:20, 17 January 2023 (UTC)[reply]
Fingers crossed this person justifies your good faith in them. Have a great day! --Yamla (talk) 16:21, 17 January 2023 (UTC)[reply]
I had meant to, but collided with my rename. — xaosflux Talk 16:21, 17 January 2023 (UTC)[reply]

Not so weird flex

Hello, Xaosflux! I find myself in need of your technical advice. I was updating the SqWiki main page some days ago when I noticed that it doesn't render nice on mobile. Then I tried seeing what happened with EnWiki (I'm not an avid mobile wikiuser myself so I hadn't concentrated on such details before) and there I saw that the whole page layout changed, its "blocks" being rearranged in a very optimized column manner. Trying to replicate the same effect, I was searching around the source code to see what made this happen and eventually I learned about the existence of flexing in CSS. Given that I just learned about it I haven't been able to achieve much yet. Can you help me make SqWiki's main page behave in a similar manner as EnWiki's does in regard to that? - Klein Muçi (talk) 07:21, 19 January 2023 (UTC)[reply]

@Klein Muçi sorry, I don't have the cycles to work on that right now. You can try asking for a volunteer over at WP:VPT. — xaosflux Talk 10:30, 19 January 2023 (UTC)[reply]
It's okay. Apparently the problem is far more complex than just using Display:Flex as I was hoping when I wrote that. Experimented a bit around. Maybe it should wait a bit. — Klein Muçi (talk) 13:33, 19 January 2023 (UTC)[reply]

all images on wikipedia do not work

Hi for some all images on wikipedia do not work please help me fix it thank you The best dude 2023 (talk) 16:19, 19 January 2023 (UTC)[reply]

@The best dude 2023 what happens if you try to load an image directly, such as by this link? — xaosflux Talk 16:47, 19 January 2023 (UTC)[reply]
It will not load at all... The best dude 2023 (talk) 14:55, 20 January 2023 (UTC)[reply]
Not sure, sounds like a problem on your client - possibly with an extension. Try another browser. — xaosflux Talk 15:03, 20 January 2023 (UTC)[reply]
I use safari The best dude 2023 (talk) 15:37, 20 January 2023 (UTC)[reply]
@The best dude 2023 yes, try another browser, ensure it is a current release, ensure your operating system has current TLS/SSL support. Nothing else I can really do for you from here; you can try asking over at commons:Commons:Village pump/Technical. — xaosflux Talk 15:40, 20 January 2023 (UTC)[reply]
It loaded but it says Restricted Site The best dude 2023 (talk) 15:52, 20 January 2023 (UTC)[reply]
No idea, sounds like something on your network in your browser; if you can verify that the "restricted site" message is coming from a WMF server (not just something your browser generated) you can open a bug report here. — xaosflux Talk 15:55, 20 January 2023 (UTC)[reply]
I do work for a organization so maybe they blocked it The best dude 2023 (talk) 15:58, 20 January 2023 (UTC)[reply]
That happens, sometimes it isn't a direct block, but an extension that is blocking it too - if you don't control your network and computer you should start by contacting your org helpdesk. — xaosflux Talk 16:32, 20 January 2023 (UTC)[reply]
Ok thank you for your help The best dude 2023 (talk) 19:14, 20 January 2023 (UTC)[reply]
Sorry for wasting your time. The best dude 2023 (talk) 16:10, 20 January 2023 (UTC)[reply]

Account hacked

Hi I am reporting a hacked account The best dude 2023 (talk) 15:17, 23 January 2023 (UTC)[reply]

Are you saying your account was hacked? Please review WP:COMPROMISED. --Yamla (talk) 15:21, 23 January 2023 (UTC)[reply]
No my friend got hacked The best dude 2023 (talk) 15:23, 23 January 2023 (UTC)[reply]
Please provide the account name and evidence of this so we can block the compromised account. --Yamla (talk) 15:25, 23 January 2023 (UTC)[reply]
And do so at WP:ANI, not here. — xaosflux Talk 15:31, 23 January 2023 (UTC)[reply]
Sorry but the account name is Dummy boy 2.0
and here is evidence "Ha ha ha i hacked this account no one can stop now lol lol lol" The best dude 2023 (talk) 15:35, 23 January 2023 (UTC)[reply]
@The best dude 2023 see above, post this at WP:ANI. — xaosflux Talk 15:38, 23 January 2023 (UTC)[reply]
Ok i did it sorry The best dude 2023 (talk) 15:46, 23 January 2023 (UTC)[reply]
OP blocked as a vandal sock. ― Blaze WolfTalkBlaze Wolf#6545 17:28, 23 January 2023 (UTC)[reply]

Tech News: 2023-04

MediaWiki message delivery 23:44, 23 January 2023 (UTC)[reply]

OMG

You are the man. (ref this Special:Diff/1135488182) Thank you very much, for everything you do and thank you very much for the things you've helped me with. - FlightTime (open channel) 00:21, 25 January 2023 (UTC)[reply]

Just saying :P - FlightTime (open channel) 00:23, 25 January 2023 (UTC)[reply]

Reply as opposed to Edit

In other words, Reply works properly, but Edit is totally screwed up. Milkunderwood (talk) 02:39, 28 January 2023 (UTC)[reply][reply]

When you go to that preferences page, which skin is currently selected? — xaosflux Talk 12:43, 28 January 2023 (UTC)[reply]
Frankly, I don't know -- I just accepted all the defaults. I use WP just to look up information, and edit only to the extent of making small corrections to obvious spelling or grammatical problems. I've never bothered to figure out the jargon here, such as "skins". In the meantime, Edit seems to work more or less properly, except when it doesn't, jumping to top of page instead of to the correct Section.
(This is a copy/paste from our original discussion, to your talkpage. I very much appreciate your help and interest, but I'm another distressed user who wishes that far better than "good enough" had been left alone. If there were a way for users to choose the look and feel of WP as it used to be, I'd definitely be there instead.) Milkunderwood (talk) 10:04, 29 January 2023 (UTC)[reply]
Oh, and also, both times I've gone to Preferences, the Save button has been grayed out. Milkunderwood (talk) 10:09, 29 January 2023 (UTC)[reply]
The save button will always be greyed out until you make a change. I asked you to go there and look so I could try to guide you, but you never answered. If you want to reset all your options to the current default, you can go to these two pages and confirm: Special:Preferences/reset / Special:GlobalPreferences/reset. Note, there is no way to "undo" a preference reset. — xaosflux Talk 11:16, 29 January 2023 (UTC)[reply]
You may first want to actually check that Skin setting. It is right at the top of the page here: Special:Preferences#mw-prefsection-rendering, it says "Skin" and only one can be selected at a time. The new default is "Vector (2022)", the older default that you may want to try is "Vector legacy (2010)". — xaosflux Talk 11:18, 29 January 2023 (UTC)[reply]
Hey, it works! Thank you! I never understood what all that gobbledygook was, other than giving me a headache. (If I didn't reply, I don't live on WP, but just visit when I need to. Most questions I might ask are never responded to.) Milkunderwood (talk) 16:15, 29 January 2023 (UTC)[reply]
Good to hear you are fixed! — xaosflux Talk 20:48, 29 January 2023 (UTC)[reply]
Oh, I am so happy now! Thank you again! Milkunderwood (talk) 00:23, 30 January 2023 (UTC)[reply]

Hi, there's a community ban discussion going on at WP:AN#User:Doug Coldwell. Just before the votes, it says:

Per WP:CBAN, "discussions may be organized via a template to distinguish comments by involved and uninvolved editors". Please declare prior involvement and post in the "Involved" section only if you were previously involved.

I looked at the policy and saw no guidance on what makes an editor "involved". I was hoping you might know how this works, in practice if not policy. Also, how does an "involved" editor's vote compare to an "uninvolved" editor's vote when the discussion is closed? The whole thing seems pretty odd to me, but I don't generally vote - or even pay that much attention to - these discussions. Thanks.--Bbb23 (talk) 16:32, 29 January 2023 (UTC)[reply]

@Bbb23 creating such a section doesn't appear to be required by policy, in general declaring involvement is beneficial so this may just make it easier. — xaosflux Talk 20:53, 29 January 2023 (UTC)[reply]
Beneficial to whom? Other editors? The closer? I still don't get it, but it's not important, thanks for your reply.--Bbb23 (talk) 21:02, 29 January 2023 (UTC)[reply]
@Bbb23 the purpose of the CBAN is to determine if the community should ban someone - so if someone is in a personal dispute with the subject they may still have something to contribute but could be biased, and the closer could take that in to consideration. It is likely a short way to help someone just call that out instead of starting threaded comments about the other participants possible involvements. I don't think it is used often like that. — xaosflux Talk 21:09, 29 January 2023 (UTC)[reply]

Tech News: 2023-05

MediaWiki message delivery 00:04, 31 January 2023 (UTC)[reply]

Minor template space cleanup

Do you have plans for {{Uw-ublock-nonsense/doc}}? It looks like the parent template uses shared documentation. If some random editor had created it, I would TFD it, but I figure that you either have plans for it or know how to use CSD G7. Thanks. – Jonesey95 (talk) 17:24, 31 January 2023 (UTC)[reply]

@Jonesey95 deleted. — xaosflux Talk 17:55, 31 January 2023 (UTC)[reply]

Administrators' newsletter – February 2023

News and updates for administrators from the past month (January 2023).

Guideline and policy news

Technical news

  • The Vector 2022 skin has become the default for desktop users of the English Wikipedia.

Arbitration

Miscellaneous

  • Voting in the 2023 Steward elections will begin on 05 February 2023, 21:00 (UTC) and end on 26 February 2023, 21:00 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
  • Voting in the 2023 Community Wishlist Survey will begin on 10 February 2023 and end on 24 February 2023. You can submit, discuss and revise proposals until 6 February 2023.
  • Tech tip: Syntax highlighting is available in both the 2011 and 2017 Wikitext editors. It can help make editing paragraphs with many references or complicated templates easier.

Verified account

@Xaosflux Hello, can you give me a verified account flag? GlazaLubvi (talk) 21:20, 2 February 2023 (UTC)[reply]

Replied on your talk. — xaosflux Talk 21:32, 2 February 2023 (UTC)[reply]