Archives

1 (to 26 January 2006) 2 (to 28 January 2006) 3 (archive of a discussion started on January 29, 2006 at the incidents noticeboard) 4 (to 28 January 2006) Old noticeboard #1 (February 2006→December 2008, clerks' coordination board) Old noticeboard #2 (December 2008→March 2010, clerks' coordination board) 5 (January 2006→May 2009) 6 (May 2009→June 2012, noticeboard merged) 7 (June 2012→September 2014) 8 (September 2014→September 2015) 9 (3 October→4 November 2015) 10 (October 2015→March 2021) 11 (April 2021→present)

This page has archives. Sections older than 4 days may be automatically archived by ClueBot III when more than 2 sections are present.

The box at WP:A/C used to be on the left side of the page. There is a parameter used in {{ArbComOpenTasks}} called |acotalign=left, but that parameter seems to no longer do anything, and the box now floats way down bottom-right. I tried a few things to fix this but they didn't work. Complicating things, for whatever reason the box floats left in preview. Any ideas? -- Tamzin^{[cetacean needed]} (they|xe) 06:41, 23 November 2024 (UTC)[reply]

Tamzin, it looks fine on my screen? It appears that |acotalign= was removed in 2012, so that parameter has been worthless for over a decade at this point. HouseBlaster (talk • he/they) 02:47, 8 December 2024 (UTC)[reply]

@HouseBlaster: What skin are you using? I'm using Vector-22. Checking now, it does align left in Vector. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 03:06, 8 December 2024 (UTC)[reply]

Tamzin, I am a Vector 2010 user; probably should've though to check the default skin! I don't see enough space to have it left-aligned while still keeping the other two sidebars. Thinking out loud in writing, do we need the dispute resolution sidebar there? It is not a current arbitration request. Thinking even more in print, I am wondering if WP:A/C can be BLAR'd to Wikipedia:Arbitration/Requests, which has all of the information at WP:A/C and more. HouseBlaster (talk • he/they) 03:16, 8 December 2024 (UTC)[reply]

I find A/C a very helpful page to access ArbCom recent changes without having to load a whole noticeboard. Seemingly many others do too. Would there be some way to make ACOT's total width flexible? At the moment it looks like all the widths are hardcoded. Alternately, this works. It's a little ugly with the DR template down there, but putting three sidebars together is gonna look a little ugly no matter what. Or as a third option, you could force all three boxen into a table. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 03:23, 8 December 2024 (UTC)[reply]

Well, it was an idea. Happy to keep it around if people find it useful :)

Forcing all three into a table looks even worse on my screen. It forces ACOT to be super narrow. I think your proposed edit (moving the least relevant item to drop below) is the least bad option which does not involve reïnventing the wheel. If someone wants to work on making ACOT's width flexible, I think that would be awesome, but with current stuff I am reluctant to sign up for doing that myself. Happy to let you do the honors of reinstating your edit; also happy to do it myself. HouseBlaster (talk • he/they) 03:39, 8 December 2024 (UTC)[reply]

@HouseBlaster: Idea just popped into my head the other night: Why not just redirect it to Template:ArbComOpenTasks? -- Tamzin^{[cetacean needed]} (they|xe|🤷) 05:43, 1 January 2025 (UTC)[reply]

 Done BOLDly; if anyone has objections revert (and I waive the prohibition on reverting clerks in arbspace for this particular edit). HouseBlaster (talk • he/they) 06:44, 1 January 2025 (UTC)[reply]

Parameters to set widths on pages, or arbitrary floats, inhibit display at mobile resolution. Setting width is a no-go from that perspective. Setting a different kind of float is possible in TemplateStyles and if that's pursued should be pursued there. Izno (talk) 04:15, 8 December 2024 (UTC)[reply]

Now that the balanced editing restriction exists, thought I'd get the ball rolling on my proposed implementation for it. Of course, entirely up to y'all how to do it, but at least the way I envisioned it, the to-dos are:

1. Create a parameter for {{pp-extended}} like |ctop=, then add that to all ARBPIA pages in the AE log. @SilverLocust and I talked a while about if there's any way to avoid this, because it is the most time-consuming part of implementation, but we couldn't come up with any other approach that would avoid false positives. Still, maybe room for brainstorming here. But I also know @Elli had volunteered to do this all themself as penance for proposing the thing. :P
2. Add {{Contentious topics/talk notice|a-i}} to all talk pages of said articles, where it isn't already present. This part should be a simple AWB/JWB run.
3. Create an edit filter for edits to pages with either of those templates on them. This bit's pretty easy.
4. Create necessary template-y stuff.
5. [Optional but good idea] Look for pages that may have been protected with ARBPIA in the summary but not logged. Correctly log them, then apply tasks 1&2 above. Quarry 89895 shows a lower bound for all pages protected that way (based on references to the case or Israel in summary), while Quarry 89896 shows an upper bound (based on any word starting with "Arb"). Even the latter is only 3,123 pages, so this actually shouldn't be too hard to sift through.
6. [Optional but good idea] Maintain a tool to track percentage of hits to that filter. And good news! I already did that for y'all. Working prototype at https://n-ninety-five.toolforge.org/. (Get it? Because it tracks filtering rate?) Would be more than happy to transfer primary maintainership to a clerk or arb on request.
7. [Optional but good idea] Have a bot maintain tasks 1&2 going forward, each time a new page is ARBPIA-ECP'd.

-- Tamzin^{[cetacean needed]} (they|xe|🤷) 02:29, 24 January 2025 (UTC)[reply]

@Tamzin: See filter 1339 and EF/R and my talk page. I can discuss it more in about an hour. SilverLocust 💬 03:13, 24 January 2025 (UTC)[reply]

The way I've done the edit filter allows #1 to be skipped: The article/draft just needs to be EC protected, have a protection template (via Module:Protection banner), and have a PIA notice on the talk page (that doesn't use |section=yes) (via Template:Contentious topics/page restriction talk notice base). Placing missing PIA talk notices certainly needs doing, and I intend to go about that soon. SilverLocust 💬 05:26, 24 January 2025 (UTC)[reply]

Hmm. I like that on a technical level. But in terms of the remedy as written, does that satisfy that are subject to the extended-confirmed restriction under Arab–Israeli conflict contentious topic procedures? A page might be ECP'd as a regular admin action, and then have the CTOP banner added to talk unrelatedly. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 05:51, 24 January 2025 (UTC)[reply]

In my view, if it isn't really subject to ECR, then |section=yes should be added to clarify that. I also made the tracking category Category:Wikipedia pages subject to the extended confirmed restriction related to the Arab-Israeli conflict to allow one to look for pages that don't seem to belong. SilverLocust 💬 06:02, 24 January 2025 (UTC)[reply]

That's a good point. I do think there would still be occasional exceptions—maybe a list or broad-concept article that touches on PIA at several points, but is mostly not about PIA, but gets ECP'd for other reasons. Maybe there should be a special parameter to disable this in edge cases? |disable-BER-tracking=1 or something. Also, there should probably be a filter tracking addition of the ARBPIA talknotice by non-admins, if there isn't already, as that's the other realm where I could see this approach leading to problems. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 06:09, 24 January 2025 (UTC)[reply]

I don't understand |section=yes to mean there's just one section that touch upon PIA, just that it isn't a page whose "topic relates to the Arab-Israeli conflict, broadly interpreted". (The older template, Template:ArbCom Arab-Israeli enforcement, instead has |relatedcontent=yes as the parameter name, which is clearer about this.)

As an alternative to a filter, you can add the tracking category to your watchlist and view category changes, especially using RelatedChanges. SilverLocust 💬 07:20, 24 January 2025 (UTC)[reply]