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.
I think that it would be natural to log the {{Welcome-arbpia}} under filter No. 602, since it's a sort of a contentious topics notification that makes users aware of the topic area as well as restrictions within it. Currently, someone who checks the filter logs would miss when somebody is assigned the template, which could lead to redundant notifications. If we log this, it would be improved.
I had thought that they got rid of the super formal requirements for "awareness" when we moved from DS to CTOP. But looking at the language in CTOP, there is still some strictness for the first CTOP alert. Maybe it's worth a WP:ARCA to see if ArbCom is OK with this sort of thing. — Red-tailed hawk(nest)05:57, 27 December 2024 (UTC)[reply]
In my mind, the obvious obstacle to it being considered sufficient for awareness is that it only mentions one of the three restrictions active in the area. —Compassionate72720:29, 27 December 2024 (UTC)[reply]
I think we should stick with considering that template an informal introduction. Perhaps /alert/first could be transcluded into the Welcome-arbpia template, so it's presented at the same time, which would allow it to be considered a CTOPS formal alert? That would satisfy the requirement that the specific template be used, and still present a summary picture of CT procedures, rather than legalese alone. EggRoll9702:39, 28 December 2024 (UTC)[reply]
Filter 869 and checkyourfact.com
I think that checkyourfact should be removed from line 3, given that the recent RfC closed with the source being deemed generally reliable (see: WP:CHECKYOURFACT). I would ordinarily do this myself, though I participated in the discussion, so I'm asking someone else to do it. — Red-tailed hawk(nest)22:22, 31 December 2024 (UTC)[reply]
user_rights variable unavailable on edit filter log entries on this project
For now, unlike Meta and other projects, there are only the user_groups variable available on enwiki. Because of this, I have listed some various filters that might need a temporary workaround until user_rights can be brought back here:
Anyone know the technical reason that enwiki doesn't have this? Is this something we can change with a #wikimedia-site-config phab ticket? Is there a reason we turned it off? –Novem Linguae (talk) 06:26, 1 January 2025 (UTC)[reply]
We definitely used to have it. I remember seeing it pop up in filter hits before. I wonder if it was disabled as part of IP masking? EggRoll9722:02, 1 January 2025 (UTC)[reply]
Yep, this was caused by thesethreechanges back in August. All those changes are "correct" (see WP:EF/TP#user_rights), but combined they have the side effect of removing user_rights from most hits (though the filters listed above will continue to work fine). If anyone wants it back (for testing purposes), we can create a filter like "user_rights; /* and other variables we want */; false;" to force its generation. Compare filter 1201 (hist·log). Suffusion of Yellow (talk) 19:04, 3 January 2025 (UTC)[reply]
Are you saying that user_rights will show up in the details of every filter log as long as a filter is always checking its value?
It makes sense as an optimization, it's just surprising that it's shown at all in the logs of filters that don't use it (before, after).
Correct; there's one variable dump shared by the all the log entries from a single action. Non-lazy-loaded variables just appear in every hit. Not sure about IP addresses, but based on a few minutes of checking on testwiki, it looks like user_unnamed_ip is replaced with a placeholder if viewed without the appropriate rights. With the "Enable revealing IP addresses for temporary accounts in AbuseFilter" option unchecked in my preferences, I can still view testwiki:Special:AbuseLog/105182 but user_unnamed_ip is an empty string. With the option checked, the full IP does show even though testwiki:Special:AbuseFilter/94 isn't checking it. Suffusion of Yellow (talk) 01:42, 4 January 2025 (UTC)[reply]
Exclude pages that have "emoji" in their title from filter number 680
Those articles are about emojis themselves, and preventing people from inserting emojis on articles about emojis limits collaboration and defeats said articles' purpose. Therefore i kindly request that all users should be free to insert emojis on articles that have the word "emoji" or "emojis" in their title, for example Eggplant emoji and Pile of Poo emoji. 67.209.130.188 (talk) 08:14, 9 January 2025 (UTC)[reply]
Looking at the articles in the category (few that there are) to see how often this is a false positive vs disruptive edits, I only found a single false positive (log) vs a handful of disruptive ones. I mean that's admittedly not a lot of disruption, but it's still some.
Regarding that false positive (as well as the page title exclusion), that's why !(old_wikitext rlike emoji) (instead of removed_lines) should solve that specific problem, if such FPs happen often.Regarding the articles in the category, what category are you talking about? Codename Noreste (talk)02:49, 10 January 2025 (UTC)[reply]
The words the category are a link to Category:Individual emoji, that's the category both example pages are part of (and the one my speculative change added).
Like Daniel I also checked the past filter hits, though for the whole category, and only found the one good attempted edit - that's why I was asking if there were more example articles, as if this is it then the filter is way more likely to stop bad edits than not, by not excluding emoji articles. – 2804:F1...BA:8B28 (::/32) (talk) 15:28, 10 January 2025 (UTC)[reply]
But the problem is that emoji is a variable for the emoji regex, and there are only Unicode blocks for emojis. For now, regarding the page title exclusion, I agree with Daniel. Codename Noreste (talk)02:40, 10 January 2025 (UTC)[reply]