Wikipedia:Edit filter noticeboard/Archive 14

Archive 10

←

Archive 12

Archive 13

Archive 14

Update to filter 707

I recently made an update to the code that can potentially exclude users withdrawing their own report, here's what I made:

page_id == 26204397 /* False positives reports page */ &
!("confirmed" in user_groups) &
(
    (
        /* Prevent the removal or modification of [[WP:EFFPR]] headers */
        contains_any(
            removed_lines,
            "__NONEWSECTIONLINK__",
            "__NOINDEX__",
            "<noinclude>",
            "{{Wikipedia:Edit filter/False positives/Header}}",
            "{{shortcut|WP:EF/FP/R|WP:EFFPR}}",
            "</noinclude>"
        )
    ) | (
        /* Page blanking or report meddling from non-confirmed users */
        (
            new_size < 300 &
            old_size > 300 |
            edit_delta < -250
        ) &
        /* Allow users to withdraw their own report */
        !(
            user_name in removed_lines &
            user_name in page_recent_contributors
        )
    )
)

Any improvements or suggestions? Thank you. Codename Noreste 🤔 Talk 08:17, 8 October 2024 (UTC)

Moving !("confirmed" in user_groups) & down might make sense, as headers shouldn't be removed by other users either. Nobody (talk) 08:24, 8 October 2024 (UTC)

I like the idea, but I don't think there's really a lot of cases where a user would need to withdraw a report. Reports are responded to within a pretty decent amount of time, and archived fairly quickly after response anyways. EggRoll97 ^(talk) 15:45, 9 October 2024 (UTC)

Edit filter 1298

Going to just bring this one here in case there's any opinions about it, but Hey man im josh has brought up 1298 (hist · log) on my talk page as having flooded his log with false positives (ones in which he used Capricorn right after creating the redirect). Given the sheer number of false positives and the lack of much use of the edit filter to correct these uncategorized redirects, is there anyone who would object to disabling the filter? For context, see here for the discussion being referred to on my talk page. EggRoll97 ^(talk) 21:56, 11 October 2024 (UTC)

I feel like these kinds of log-only maintenance filters are often not a good idea. In my experience, these quickly ended up unmonitored and unused. I'm also personally wary of the edit filter being used for non-abuse related stuff much of the time. There are definitely legitimate use cases, but I think many requests at EFR for non-abuse related use cases were (are?) unnecessary. ProcrastinatingReader (talk) 22:40, 11 October 2024 (UTC)

I have 3 main issues with it.

1. Rcats are entirely optional. Would it be nice if people included them more? Absolutely, but a lack of them doesn't mean there's necessarily an issue. There's an implication based on this filter's existence, I believe, that a lack of rcats on the immediate creation of a redirect is a bigger sin than it really is.

2. The false positives. I often create a redirect and immediately tag it. I don't remember all the tags off the top of my head, I know the relevant ones that exist, but I don't know all the templates and I don't try to memorize them because I have tools to add the tags. I know where to find them in Capricorn and what to search in the page curation bar to add the tags. However the edit filter will still show these entries anyways.

3. If someone is looking for redirects to add tags to they'd be better served with a database query of some kind. Ideally something to the effect pages with redirects without rcats, sorted by target so that proper tagging can be done in batches.

Anyways, while I think there were good intentions with this filter, I don't believe it's actively used and helpful. It's more likely to drown out some relevant entries in an individuals abuse logs in my opinion. Hey man im josh (talk) 22:58, 11 October 2024 (UTC)

I know it was mentioned in the user talk discussion, but I'll re-mention it: This filter was created as a result of this request (permalink), which, disclaimer, I took part in.

Also pinging @Geardona as the original poster of the request (even if it was a request for a warn filter). – 2804:F14:80EB:C501:DD4E:2EFB:9ECB:8A56 (talk) 20:20, 12 October 2024 (UTC)

I sometimes patrol that filter log and add rcats where I'm sure, so I'd like the filter to stay enabled. Also I'm not sure if Josh knows this, but it's possible to add rcats while creating a redirect with Capricorn. If it's really that big an issue, then we can just add an exclusion for him (or the sysop user group for example) to the filter. Nobody (talk) 05:21, 14 October 2024 (UTC)

I mean, is a non-abuse filter with apparently 102,147 hits over the past six months really something that's practical to monitor? That's 500 new additions per day- when compared to other common non-abuse filters, we see it trips ten times as often as filter 1030 (URLs with tracking parameters) and 1,254(oops! you broke an sfn), and five times as often as 550 (nowiki tags). Again, with all due respect to people who do monitor it- I think there might be much more efficient solutions that don't clog up individual editor's filter log. GreenLipstickLesbian (talk) 06:13, 14 October 2024 (UTC)

I always thought that it would be better to have a tracking category for these redirects instead of a filter, but not sure if it's possible to get consensus for a tracking cat with possibly millions of redirects. Nobody (talk) 06:46, 14 October 2024 (UTC)

If there wouldn't be consensus for a tracking category, is getting around that by using an edit filter for something non-abusive really the better option? Hey man im josh (talk) 12:34, 15 October 2024 (UTC)

I think it's better than having nothing at all. Especially since it's easy to remove sysops or individual users from the filters. Nobody (talk) 14:40, 15 October 2024 (UTC)

@1AmNobody24: There are millions of redirects without rcats. This is not the way to address the problem, nor is it anywhere close to an efficient way to do so. By keeping a filter such as this active we're flooding the abuse log and reducing the effectiveness of it for a few individuals who would like to occasionally find redirects to add rcats to. If those individuals have that desire, I encourage them to instead join WP:NPP and patrol the massive redirect backlog we typically have. Hey man im josh (talk) 15:01, 15 October 2024 (UTC)

I agree that for new redirects NPP is better, it's one of the main reason I've considered applying for it. But at the same time there are millions of old redirects and ones from autopatrolled users that go unnoticed. I think there should be a way to track them. Be it a maintenance cat, a query, a filter or a external tool doesn't matter to me. Nobody (talk) 15:18, 15 October 2024 (UTC)

The old redirects, and this not being actually abusive in any sense of the word, is exactly why this edit filter doesn't make sense to keep in my opinion. Hey man im josh (talk) 15:20, 15 October 2024 (UTC)

I requested a quarry query (thank you Cryptic) to see how many uncategorized redirects we have. Based on this query, it appears we have 6,265,917 uncategorized redirects at the time of the run. They also provided a sample of 10,000 uncategorized redirects. A quarry query like this, in my opinion, would be far more useful for folks attempting to categorize redirects than flooding the logs. Pinging @1AmNobody24 and @Geardona, as they've been the only two I'm aware of who expressed interest in using this filter to tag redirects. Hey man im josh (talk) 18:00, 15 October 2024 (UTC)

That looks great, thanks for doing it. I'll probably ask Cryptic for some sorted querys then and start gnoming away. Given this, I have no objections to disabling the filter. Nobody (talk) 18:36, 15 October 2024 (UTC)

The missing datum here is that there's 11,150,454 total redirects in mainspace. So less than half are categorized. —Cryptic 18:48, 15 October 2024 (UTC)

 Done Given the Quarry query seems to alleviate all concerns, I've deleted the filter. EggRoll97 ^(talk) 19:19, 15 October 2024 (UTC)

graph links broken

The links to filter graphs from Special:AbuseFilter result in a page that says "Internal error". -- mikeblas (talk) 19:07, 20 October 2024 (UTC)

You mean https://ptwikis.toolforge.org/Filters:enwiki? Can confirm the error happens.

This seems like something that would also be a good fit for WP:VPT, if there's no immediate response here.

Last person to update that link was @WOSlinker in Nov 2020. – 2804:F14:80D7:A301:3134:44A8:18ED:5881 (talk) 19:35, 20 October 2024 (UTC)

The problem is that the replica database this tool uses doesn't have the `abuse_filter_log` table available anymore. Probably because of the new protected variables thingy? XXBlackburnXx (talk) 20:24, 20 October 2024 (UTC)

Most likely. There is a new box on edit filters saying "I understand that details of this filter will be hidden from users who cannot see protected variables", which likely shows up since global abuse filter helper now has abusefilter-access-protected-vars. I presume this new introduction may have broken it, though that's not necessarily the only reason. I've also raised this issue at WP:VPT. EggRoll97 ^(talk) 03:27, 23 October 2024 (UTC)

Request for Edit Filter Helper - Zippybonzo

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Zippybonzo (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

Zippybonzo (talk · contribs · count) • Heya all, I’m requesting Edit Filter Helper for 2 main reasons. Firstly, I’d like to be able to help out with private filters, I’ve got a decent level of experience with regex and the filter syntax, and secondly, when handling cases of vandalism, I have a script that shows filter hits in contributions, and quite frequently, they are private filters, which often add insight as to whether the user is potentially an LTA, which helps with my anti-vandalism work. It will also allow me to help process private filters false positives. Zippybonzo | talk | contribs (they/them) 16:12, 19 October 2024 (UTC)

• I don't really see that you have done much with filters recently. Xtools says that you've only made 112 edits to WP:EFFPR, when the average benchmark is around 500, and only 3 have been in the last 3 months. I don't really see you in the page history of WP:EFR suggesting regex or actual filters either recently and xtools says you have only made 1 edit to that page. On this very page, you haven't made any edits (besides this request) since february. I'm leaning oppose to granting this right to you for now until you can demonstrate that you are active in the area. Like many have said, this right is only given to the most trusted users and is similar to being granted sysop privileges. After one to two years of solid work in this area, I think you would be ready for this right. – PharyngealImplosive7 (talk) 18:00, 19 October 2024 (UTC)
• All I wanted to say is above, so oppose. Not enough recent contributions to EFFPR, nor enough at all. Your only contribution to EFR has been to suggest using the spam blacklist once. If you succeed in admin elections, which you are currently running in, this will be moot, though, since EFH is implicit in sysop. EggRoll97 ^(talk) 18:07, 19 October 2024 (UTC)

  @EggRoll97, the reason for requesting access was primarily to assist anti vandalism work, and the occasional handling of EFFP reports. Admittedly the whole request is moot atp, however I’m not expecting to succeed in AELECT because I’ve not been recently active enough, but I digress. It’s more that frequently when I come across disruptive editors tripping filters, they are private and it makes it a pain to handle said editors. The mention of EFFP was intended to come across as an, “as well it would mean I could” rather than a “that is why I am requesting”. Zippybonzo | talk | contribs (they/them) 18:28, 19 October 2024 (UTC)

  You satisfy the necessity for trust, but EFH is not generally given for anti-vandalism. This isn't meant as a slight against you, just that EFH is very rarely given, and I don't see much of a need here. The majority of filters are public filters (174 public filters, 157 private filters), and deal with most vandalism. Without a significant need past just anti-vandalism, I'm afraid my oppose remains. EggRoll97 ^(talk) 18:37, 19 October 2024 (UTC)

• Because of the concerns mentioned above, I oppose. The comment above is relevant, given that EFH is handed out to highly trusted users (comparable to holding either the administrator privilege or an advanced global permission) who want to help with filters, such as authoring either conditions that can track LTAs or somewhat complex regex to private filters. I would recommend helping on EFR and EFFPR for at least one whole year, then you might be ready to give a more solid explanation about your demonstrated need for this highly sensitive right. Codename Noreste 🤔 Talk 19:58, 19 October 2024 (UTC)
• The earliest closure has started, so could an admin close as not granted? – PharyngealImplosive7 (talk) 15:18, 28 October 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

"Dumb premise"

Via Wikipedia:Administrators' noticeboard/Incidents#Vandalsock – yet another viral challenge. We appear to have a filter that intercepts social media and 'viral' nonsense, so please can someone add edits that include "dumb premise" and/or "bloodless series" to that filter? 81.2.123.64 (talk) 17:34, 23 October 2024 (UTC)

Which filter is this? EggRoll97 ^(talk) 04:40, 25 October 2024 (UTC)

I think they mean 614 (hist · log) Nobody (talk) 05:22, 25 October 2024 (UTC)

Hmm, perhaps any more evidence of further disruption, in addition to these two accounts mentioned on the ANI archive link? Codename Noreste 🤔 Talk 15:44, 25 October 2024 (UTC)

Seems fairly infrequent. I'm not necessarily eager to add the new terms without a bit more evidence of present disruption. EggRoll97 ^(talk) 22:32, 30 October 2024 (UTC)

Question about the 'Arbitration contentious topics alerts' filter

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

• 602 (hist · log)

Maybe don't change the filter just to accommodate my unwillingness to create an account (again, like 707 at the top), but is there any reason for this filter to only go off for confirmed-or-up editors like it's currently setup? Is it just optimization? I have alerted people of contentious topics before (though, I think, only once: diff). – 2804:F1...88:7F3B (::/32) (talk) 22:09, 29 October 2024 (UTC)

By removing "confirmed" in user_groups, the filter should apply to ALL non-bot users, similar to 1016 (hist · log). Codename Noreste 🤔 Talk 17:38, 30 October 2024 (UTC)

I'm okay with removing the confirmed check (possibly replacing with !"bot" in user_groups instead? On the other hand, it's unlikely a bot would be tripping this filter). I'll leave it for a day or so in case anyone feels the need to comment regarding it with any objections. EggRoll97 ^(talk) 22:23, 30 October 2024 (UTC)

602 already excludes bots. Codename Noreste 🤔 Talk 23:06, 30 October 2024 (UTC)

You're right, it does. My bad. EggRoll97 ^(talk) 01:42, 31 October 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Request for Edit Filter Manager or Edit Filter Helper

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Z. Patterson (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

As a newly returned Wikipedian, I am interested in helping make or change edit filters to decrease the likelihood of disruptive editing. I was away from Wikimedia for several years, but I decided to come back. In 2024, I learned programming languages, and I also analyzed some edit filters before I came back. Thank you for your time and consideration. Z. Patterson (talk) 04:11, 2 November 2024 (UTC)

@Z. Patterson: Is this a request for EFM or for EFH? They are extremely different groups. See here for a description of edit filter managers and here for edit filter helpers. As a side note though, I will note that you don't appear to have any edit filter related contributions to your record, and generally those who successfully request either group have demonstrated a high level of experience. Can you point to any edit filter work you've done? EggRoll97 ^(talk) 05:10, 2 November 2024 (UTC)

See below. Z. Patterson (talk) 05:16, 2 November 2024 (UTC)

Welcome back to Wikipedia. The permission you are requesting is not given to users solely based on knowledge of regex and filter syntax; it is granted only to highly trusted users who have demonstrated need for it. I do not see any edits on edit filter-related pages, and this request is your only contribution to this noticeboard. This is also only your fourth edit since 2015. I would suggest spending one to two years reviewing edit filter false positive reports and suggesting changes to public filters before requesting EFH. – DreamRimmer (talk) 05:12, 2 November 2024 (UTC)

I understand now. Thank you. Z. Patterson (talk) 05:13, 2 November 2024 (UTC)

Z. Patterson Is it safe to assume the above comment is a withdrawal of this request? EggRoll97 ^(talk) 05:14, 2 November 2024 (UTC)

Yes. For now, I plan to withdraw this request and wait until I get more experience. Z. Patterson (talk) 05:15, 2 November 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Disable 1288?

1288 (hist · log)

In accordance with the process defined at Wikipedia:Edit_filter#Requesting_edit_filters, I propose the disabling of filter 1288 following concerns raised by Codename Noreste at EFFPR about false positives. I can't really describe this one, but EFHs/EFMs/sysops will be able to take a look. I have emailed the administrator who enabled the filter as of 19 days ago for clarification and discussion regarding the matter, but have received no response. In the filter results, I see a mix of common vandalism (which is either caught by other filters or would probably be caught immediately at RecentChanges) and false positives, but as far as I can tell, not a lot that actually matches the filter's intent. This is a cursory review, I'd welcome anyone setting me straight on it if I'm missing a large swathe of true hits. EggRoll97 ^(talk) 22:29, 30 October 2024 (UTC)

I can confirm that the target mentioned in the notes of filter 1288 aren't using any of the IP addresses in the ranges within the filter, and therefore, I strongly support this. Yes, they even know 1273 is for them. Codename Noreste 🤔 Talk 23:01, 30 October 2024 (UTC)

Sorry, been busy recently and haven't been able to respond much. Feel free to disable the filter. I don't expect to have the time to maintain it in the foreseeable future, unfortunately. —Ingenuity (t • c) 02:26, 3 November 2024 (UTC)

 Done Per consensus. EggRoll97 ^(talk) 02:34, 3 November 2024 (UTC)

Edit to 614

@Codename Noreste: suggested that we should modify the part of 614 (hist · log) that says (?:sean\s(?:\"?diddy\"?\s)?(?:(?:combs)|(?:john)))|(?:p?\s?didd(?:(?:y)|(?:ler)))|(?:puff\sdaddy)|(?:p\sdiddy) into sean\s?(?:\"?diddy\"?\s?)?(?:combs|john)|(?:p\s?)?didd(?:ler|y)|puff\s?daddy. As he said, this version of that code is less expensive in general. I have tested it thoroughly, and it seems to work about as well as the expanded code. – PharyngealImplosive7 (talk) 00:27, 4 November 2024 (UTC)

Request

My apologies but I am proposing a new crosswiki LTA filter, however, the request page explicitly states that such request be directed to wikipedia-en-editfilterslists.wikimedia.org, but to prevent possible outing, I refrain from doing so. I am willing though to send a Wikipedia email... ToadetteEdit (talk) 09:29, 4 November 2024 (UTC)

Feel free to send me the mail and I'll post it on the list for you. Nobody (talk) 09:43, 4 November 2024 (UTC)

Edit filter manager for Codename Noreste

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Codename Noreste (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

Hello, everyone. A few months ago, I was granted the edit filter helper right (as of July 13) and the global abuse filter helper right (as of September 6), and I am requesting the community to be granted the edit filter manager privilege as a non-administrator. My technical competence has improved significantly over the last few months when working with local and global filters as an EFH and a GAFH, and I have helped with the following filters: filter 707 (a previously disabled filter that currently stops disruption at EFFPR), a new private filter on the edit filter mailing list, and Meta filters 324, 344, 345, 360, 362, 365, 375, and 377.

Furthermore, if the permission was granted, I also plan to import some of Meta's private filters to here if needed, to fix any filter's regex or conditions if issues arise, to add or modify the conditions of local LTA filters that I have authored/maintained/edited on behalf on some edit filter managers (mainly 936 , 1292 , 1308 , and parts of 1319 ), and to commit to reducing the current backlog of the edit filter mailing list by implementing suggestions.

I understand that this privilege is extremely dangerous if used on the wrong hands or with malicious intent, and I will use extreme caution and common sense when editing filters, especially when editing regex strings. I confirm that 2FA is already enabled on my main account, and I am available to respond to any feedback, questions, or concerns. Thank you for your consideration. Codename Noreste 🤔 Talk 05:00, 7 November 2024 (UTC)

Discussion

• Support. Extremely active on the edit filter mailing list. –Novem Linguae (talk) 07:41, 7 November 2024 (UTC)

  Courtesy links:

  • meta:Steward requests/Global permissions/2024-09#Global abuse filter helper for Codename Noreste
  • Wikipedia:Edit filter noticeboard/Archive 13#Edit filter helper for Codename Noreste (third nomination)
  • Wikipedia:Edit filter noticeboard/Archive 12#Edit filter helper request for 64andtim

  –Novem Linguae (talk) 07:46, 7 November 2024 (UTC)

• Procedural note: The administrator's noticeboard has been notified in accordance with WP:EFM at Special:Diff/1255917465. EggRoll97 ^(talk) 07:55, 7 November 2024 (UTC)
• Support. Despite a minor lingering concern over eagerness on overhauling filters, I will chalk this up to mainly a difference of opinion. I have no doubt as to their technical competency, and I haven't noticed anything majorly problematic. The comments by Daniel actually reminded me of multiple specific incidents in which I cautioned Codename Noreste via email about publicly talking about filters that were intentionally private. Because of that, I must oppose given I cannot trust in their discretion in good faith. EggRoll97 ^(talk) 08:00, 7 November 2024 (UTC)
• Support. Trusted and well experienced user. --TenWhile6 08:38, 7 November 2024 (UTC)
• Neutral On one hand, I know that they have made great contributions, especially to certain LTA filters, both here and on meta. On the other hand, there have been some discussion like this and this one which just didn't leave me with a good feeling. I've also seen comments by them that they intended to run for EFM next year or a year after they get EFH. What changed? Nobody (talk) 08:53, 7 November 2024 (UTC)

  (updated response) About the first discussion, I have changed my decision to run for EFM yesterday, and for Meta adminship, I decided not to run for that to avoid hat collecting. For the second discussion you mentioned, the CAPTCHA bypassed when I tested it with my alt/test account. An IP address mentioned that to me, and I told them there were no further replies to the task related to the CAPTCHA action after thanking them for the notification. For these two, I assumed good faith. Because of some very active LTAs, per the first sentence, that's what led me to run for EFM yesterday. I also have another filter targeting 1311's target in mind. Codename Noreste 🤔 Talk 15:13, 7 November 2024 (UTC)

  While I still don't understand what exactly happened in my CAPTCHA conversation, I didn't see it as anything to give a bad impression about, just some level of failure of communication.

  I won't vote, but I guess the only thing I'd ask of you, Codename Noreste, because it's recent, is what your thought process was behind revealing vague details about the LTA filter 1288 - I know of course that you're not the first to talk about some aspect of a private filter in vague terms, but I still want to know how you approach this. – 2804:F1...EF:A81F (::/32) (talk) 03:10, 8 November 2024 (UTC)

  I apologize for these two mistakes that I may have done, but as I said before regarding filter 1288, see here. Codename Noreste 🤔 Talk 03:33, 8 November 2024 (UTC)

  I meant revealing that the filter was focused on specific ranges of IPs, obviously that LTA would know about 'filter 1273', considering that was the public name of the now disabled filter 1288 ('LTA 1273'), as well as the public name of other filters targeting them. Was it because they weren't using those IPs anymore, so you felt that that information wasn't useful anymore, or what? I just want to understand how you decide if a detail like that is fine to talk about in public or not. – 2804:F1...EF:A81F (::/32) (talk) 03:47, 8 November 2024 (UTC)

  I did not mention what are the specific ranges used within the filter, but we should not discuss further about the vandal, and let's continue with my self-nomination for EFM. Codename Noreste 🤔 Talk 04:33, 8 November 2024 (UTC)

• I do not see anything significant to oppose, and 1AmNobody24's diffs do not appear to be significant. I do wonder whether this user is ramping up too fast though. Leaderboard (talk) 11:50, 7 November 2024 (UTC)
• Support per above. I've made filters with CN before, and fully trust him with this right. Changed to neutral because I don't know about these concerns but because they seem significant. – PharyngealImplosive7 (talk) 15:42, 7 November 2024 (UTC)
• CN seems to be a trustworthy user and I don't doubt their abilities; I'm sure they will do good work if they become an EFM. The request seems a little on the early side to me though. CN only registered 17 months ago and this is a flag that is sometimes considered more sensitive than sysop. I'm good either way, but just want to be cautious. Ternera (talk) 16:59, 7 November 2024 (UTC)
• Oppose. Codename Noreste has previously revealed private filter information on multiple occasions (in addition to the above example) in a way that has likely damaged the effectiveness of several filters, and I remain concerned about their discretion with sensitive data. It often seems like the point is to demonstrate their access to private information rather than necessity. They are also very persistent about low priority changes, which does not inspire confidence in how they might approach an expanded role. I am also concerned their approach could lead to filters becoming more complex and difficult to maintain. Combined with a persistent and unnecessarily urgent focus on acquiring permissions, I am concerned that they lack the caution and restraint essential for an EFM. Regretfully, I am closer to recommending a review of their EFH status than supporting this promotion to EFM. Daniel Quinlan (talk) 11:24, 8 November 2024 (UTC)
• Oppose for now per the above, and discussion on the mailing list. — TheresNoTime (talk • they/them) 14:17, 8 November 2024 (UTC)

Because of the ongoing criticism and concerns, I officially withdraw this. Codename Noreste 🤔 Talk 15:03, 8 November 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

1178 was temp. disallow

Just a FYI that I quickly set 1178 to disallow for a while just now due to an active LTA at Wikipedia:Teahouse — I was actively monitoring & making changes as needed. It is no longer set to disallow. — TheresNoTime (talk • they/them) 21:22, 12 November 2024 (UTC)

EFFPR

Just noting that EFFPR was semi protected for 48 hours about ~16 hours ago. Seems kind of long. – 2804:F1...B0:60FE (::/32) (talk) 02:19, 13 November 2024 (UTC)

Yeah I know, but I guess you have to deter the socks somehow. – PharyngealImplosive7 (talk) 02:22, 13 November 2024 (UTC)

Not that I expect anyone to do this, but it seems surprisingly possible to create better system (temporarily activated when needed) by creating a filter that disallows every non-autoconfirmed edit at EFFPR (with an appropriate banner telling them that their report is saved pending a bot check) and also create a bot that checks each disallowed edit to see if it's a new report and then checks if the IP/account that made the report triggered an LTA filter (or any filter at all) recently, and if it looks okay (criteria of your choice) the bot then adds the report... but that's like, a crazy idea.

-

But I digress, semi protection is fine too, I just think it's useful for people who frequent EFN to know if a longer-than-usual protection was done.

So there, you have been informed. – 2804:F1...B0:60FE (::/32) (talk) 03:10, 13 November 2024 (UTC)

That all makes sense, but it might be quite difficult to implement such a system for such a niche purpose. – PharyngealImplosive7 (talk) 14:37, 13 November 2024 (UTC)