Private filters should not be discussed in detail here; please email an edit filter manager if you have specific concerns or questions about the content of hidden filters.
Did other cleanup there, the current list of names is useless, and the group is really the right way to handle that anyway. — xaosfluxTalk12:20, 10 June 2024 (UTC)[reply]
A quick thought: Should WP:EFM be a page instead of a section?[edit]
I've wondered for a while whether WP:EFM should be an actual page (similar to WP:EFH), rather than just a section on the edit filter page. Does anyone have any thoughts about whether this might break WP:CREEP, or whether this might be beneficial? EggRoll97(talk) 01:34, 20 June 2024 (UTC)[reply]
I don't object to this thought at all, but it's also worth noting that administrators can only modify edit filters that use restricted actions, as well as being able to enable such actions on filters. Codename Noreste 🤔 Talk03:34, 20 June 2024 (UTC)[reply]
Will do, though functionally the only restricted action is block-autopromote, which hasn't been used in over a decade, and would likely need multiple discussions to just have a single filter with it enabled anyways. EggRoll97(talk) 21:31, 20 June 2024 (UTC)[reply]
@EggRoll97 the revocation criteria prob need work, as it is generally not appropriate for admins to just remove this from other admins, as opposed to the non-admin EFMs. — xaosfluxTalk23:59, 20 June 2024 (UTC)[reply]
If this is going to contain any changes from the current content that are meaningful, like criteria for revocation, we should have a slightly more formal discussion/approval of the changes. E.g. "The editor has failed to report to an administrator after noticing unauthorized use of their account..." - if I were ever to notice unauthorized use of my account, I don't think I would be reporting it to admins on each wiki I have advanced rights. I would change my passwords and probably mention it to stewards, perform a crosswiki audit of every action performed recently, and likely reach out to the WMF security team since I have 2FA and would be curious how someone had bypassed it, but why do I need to tell an enwiki admin if when compromised the account didn't make any changes on enwiki? --DannyS712 (talk) 01:00, 21 June 2024 (UTC)[reply]
Also "If a previous application for edit filter manager or edit filter helper was unsuccessful" - I think I had an unsuccessful EFH request before I was granted it, but when I applied for EFM this currently suggests that I should have pinged the participants of the successful EFH discussion. I.e. I should have told the people at Special:Permalink/909783210#EFH for DannyS712 (2) about my EFM request, which would feel like canvassing to me. --DannyS712 (talk) 01:03, 21 June 2024 (UTC)[reply]
@DannyS712: I've removed the "edit filter helper" bit currently, that was just a copy direct from WP:EFH, I thought I took out the helper one. The intention was only to require notification about prior EFM requests. As for the account security language, I'm pretty sure that's just the standard language, but I don't see much reason for it to be in there honestly. It was just part of EFH and so got copied over. EggRoll97(talk) 01:55, 21 June 2024 (UTC)[reply]
@Xaosflux: I should ask, why would removal of this right from an admin not be considered appropriate? Admins are able to self-grant, so their granting of edit filter manager rights isn't subject to a community process in the same manner as non-admin EFMs (they are given adminship at RfA, though that doesn't necessarily assess technical ability unless the admin is running on being a tech-admin). I'd actually think it should be easier to remove from an admin, considering it would be trivially easy to regrant (just a talk page discussion between the revoking admin and the revokee), compared to the process to re-grant to a non-admin (a formal request to WP:EFN, requiring the action of an admin to re-grant). EggRoll97(talk) 01:55, 21 June 2024 (UTC)[reply]
@EggRoll97: I'm seeing a lot of WP:CREEP in there. For example, it's never been a convention that disabling a filter, or changing it from disallow to log-only requires discussion. Sometimes, the meme dies a natural death, or the LTA gets bored, and a discussion will be the very thing that brings them back. I think any new rules for EFMs should be in response to some problem that's actually happened, not a problem that might happen. Suffusion of Yellow (talk) 21:42, 23 June 2024 (UTC)[reply]
Tonight I made a couple edits to WP:EFH and WP:EFM that reduce WP:CREEP. We had a couple very detailed procedures for things that almost never happen, so I deleted those sections or changed them to a couple sentences. Hope it helps. –Novem Linguae (talk) 04:12, 24 June 2024 (UTC)[reply]
98 (hist·log) (Creating very short new article, public)
Per Wikipedia:Edit filter/Traps and pitfalls#user_rights, I would suggest changing !"extendedconfirmed" in user_rights & on line 4 with !contains_any(user_groups, "extendedconfirmed", "sysop", "bot") & because of this: but this will not work as expected if the user did not grant editprotected when setting up a bot password.. user_rights may be limited if the user has logged in using a bot password, or is editing with an OAuth application. Thank you. Codename Noreste 🤔 Talk00:41, 21 June 2024 (UTC)[reply]
Heads up: as of last WP:THURSDAY attempting to save certain filters will give you a Fatal exception of type "MediaWiki\Extension\AbuseFilter\Parser\Exception\UserVisibleException". See the task for details. If you need to disable a filter and can't wait for the problem to be fixed, just blank and disable it, but remember you won't be able to restore the old version until the bug is fixed. Suffusion of Yellow (talk) 01:36, 24 June 2024 (UTC)[reply]
Wouldn't be against it, though warn seems to already be working fairly well. Basically, I see the technical accuracy, but not the necessity of setting it to disallow. EggRoll97(talk) 20:36, 4 July 2024 (UTC)[reply]
There are 7 days, 6 hours, 8 minutes and 34 seconds until the earliest closure. (refresh)
Hello, everyone. This has been a few months after my failed nomination back in February, but after I have addressed your concerns seriously, I am requesting the edit filter helper right again. But this time, I now intend to assist with writing filters using my basic knowledge of regular expressions.
I have proposed additions to filter 936 (hist·log) (implemented by Suffusion of Yellow via email), and I have written and requested updates on 1292 (hist·log) (a global filter that tracks 1292's target was implemented on Meta as 344 (Meta admins only)) and 1308 (hist·log) (both filters are maintained by Ingenuity except the global filter, in which that global filter is maintained by SHB2000 on Meta), and 1313 (hist·log). Given these filters' sensitive detection strategies, I do not intend to discuss their details on public or outside of the edit filter mailing list.
With respect to account security and nonpublic information, I use a strong password and have 2FA enabled on my main account, and I have signed the confidentiality agreement for nonpublic information (verify).
Strong support – I've worked with Codename Noreste pretty much ever since I became an admin on Meta and his work on edit filters is priceless. He's also very proactive on maintenance, which is critical for EFH. --SHB2000 (talk) 04:13, 6 July 2024 (UTC)[reply]
Done -- zzuuzz (talk) 19:58, 8 June 2024 (UTC)[reply]
