User talk:Mlaffs/Archives/2019/May

WBDY Move
I moved WBDY (former AM station) to WBDY (AM) to make room for a disambig page as there is now a WBDY-LP. Had a user make an edit referencing the LP station on the AM's page. So I made the LP page. No biggie. Anyway, could you check and make sure I did the move and subsequent cleanup correctly, please? Thanks! :) -  Neutralhomer •  Talk  • 21:39 on April 30, 2019 (UTC)
 * Looks right. Cleaned out a couple of incoming links still pointing to the dab page, and added another entry, but that's it. Mlaffs (talk) 21:52, 30 April 2019 (UTC)
 * Nice, thanks! :) -  Neutralhomer •  Talk  • 22:41 on April 30, 2019 (UTC)

ArbCom 2019 special circular
   

This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:46, 4 May 2019 (UTC)

WDTW-FM
I'm confused. WLQB still has the same letters.— Vchimpanzee  •  talk  •  contributions  •  16:02, 4 May 2019 (UTC)
 * Well, now I'm confused. I'm not sure what you're asking. Mlaffs (talk) 16:28, 4 May 2019 (UTC)
 * Okay, you are very busy and can't remember what you did two months ago. I nearly moved WLQB because the Wlinks in some articles were wrong.— Vchimpanzee  •  talk  •  contributions  •  16:55, 4 May 2019 (UTC)
 * I know there was a whole little dosey-do of call signs by iHeart. WLQB in North Carolina changed to WLLZ, then WDTW-FM, then back to WLQB, all in the space of about two weeks. WDTW-FM in Detroit changed to WLLZ as part of that process, because they rebranded the station. But it's all settled there since, what, mid-March? If there was a suggestion there would be more change, you're right, I don't remember that. Mlaffs (talk) 17:02, 4 May 2019 (UTC)
 * This was one of several changes that didn't get changed back. I very nearly corrected the situation in the wrong way.— Vchimpanzee  •  talk  •  contributions  •  17:12, 4 May 2019 (UTC)

Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.

Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.

We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.

For the Arbitration Committee, -Cameron11598 21:04, 4 May 2019 (UTC)