Test Wiki:Community portal/Archive 9

The below text is preserved as an archive. Please do not edit this page.

Addition of interface admin protection level

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

 Not done. Requester block and no consensus achieved. X (talk) 18:25, 16 October 2023 (UTC)

---

I am proposing that interface administrator protection is added to help protect sensitive interface pages, i.e the sidebar and sitenotice pages, and also for protecting highly used templates. Zippybonzo (talk) 06:47, 10 July 2023 (UTC)

•  Oppose. X (talk) 11:13, 10 July 2023 (UTC)

  @X With what rationale? Zippybonzo (talk) 12:19, 10 July 2023 (UTC)

•  Weak Oppose I don't see why bureaucrat/steward protection isn't enough, particularly for the sidebar.Justarandomamerican (talk) 14:43, 10 July 2023 (UTC)

•  Weak oppose Per Justarandomamerican. AlPaD (talk) 08:14, 15 July 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Block review of Piccadilly

I'd like to determine whether consensus believes that Piccadilly creating a blank talk page for a test page is worthy of a 3 month block from talk namespaces. In my opinion a block from talk namespaces is unneeded but instead a final warning, and a filter to warn upon creation of talk pages with a size under 256 bytes (a signature and a few words). For the record, this wiki is a test wiki, not the English Wikipedia, meaning people can test, and they aren't random talk pages, they are talk pages of test pages. Zippybonzo (talk) 11:16, 11 July 2023 (UTC)

Or possibly limit the creation to exclude certain words (I.e hello, hi, guys), also, blocking at the request of a steward is mad, as the stewards can block for themselves, they are sysops too and I'd like to see their name in the block log if they authorised the block, as you don't see MacFan telling someone else to update the wiki. Zippybonzo (talk) 11:21, 11 July 2023 (UTC)

 Oppose changing the block. We’ve given Piccadilly so many changes and so many warnings. Why must we give another? I think the partial block is a good alternative to a indef full block. And there’s nothing wrong with blocking on the request of a steward because maybe they can’t get to a laptop or they’re very busy. I’ve done it before and there’s nothing wrong with it. X (talk) 12:33, 11 July 2023 (UTC)

 Oppose changing the block as per X's comment. Sav • ( Edits | Talk ) 12:46, 11 July 2023 (UTC)

 Comment: -- The blockage was not entirely at my request, only the change from 1 year to three months was made by Justarandomamerican at my request. Drummingman (talk) 14:07, 11 July 2023 (UTC)

Totally reasonable that they can somehow tell you to do it but not access their computer, I don’t think that’s a very good reason. Zippybonzo (talk) 02:12, 12 July 2023 (UTC)

I'm neutral on the block, to be honest. I'm just glad it isn't an indefinite sitewide block. Piccadilly (My Contribs | Talk to me) 12:51, 12 July 2023 (UTC)

@Piccadilly May I ask why you tested on talk pages again after many warnings? X (talk) 13:02, 12 July 2023 (UTC)

I'm not really sure to be honest. I can say that I wasn't thinking about possible consequences of my actions, which I know isn't an excuse. I think I need to make more of an effort to slow down and think about doing things rather than just rush into them like I tend to do. Piccadilly (My Contribs | Talk to me) 13:54, 12 July 2023 (UTC)

Alternate proposal: Prevent creation of talk pages but allow editing

I have an alternative proposal, to use an edit filter to prevent creation of talk pages for the remainder of the block, but allow editing. Any tampering with the filter will result in a desysop and 6 month block from all namespaces. Zippybonzo (talk) 12:29, 14 July 2023 (UTC)

Neutral. X (talk) 12:40, 14 July 2023 (UTC)

 Support as the least restrictive method of preventing disruption at the moment. Justarandomamerican (talk) 12:43, 14 July 2023 (UTC)

 Support Piccadilly (My Contribs | Talk to me) 12:52, 14 July 2023 (UTC)

Neutral. Sav • ( Edits | Talk ) 15:31, 14 July 2023 (UTC)

 Support AlPaD (talk) 08:16, 15 July 2023 (UTC)

I believe this can be implemented now, and anyone may remove the block as soon as it is implemented. If they edit existing talk pages to test editing functions, the block may be reinstated by any Bureaucrat. Justarandomamerican (talk) 16:19, 17 July 2023 (UTC)

Implementing... could take a while as I haven't used filters like this in a while. Zippybonzo (talk) 04:04, 18 July 2023 (UTC)

Should be done, give me a bit of time to test it and I'll be back with a full result. Zippybonzo (talk) 04:10, 18 July 2023 (UTC)

 Done Zippybonzo (talk) 04:25, 18 July 2023 (UTC)

Request for System Administrator: Zippybonzo

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

 Not done per block. MacFan4000 ^{(Talk Contribs)} 12:59, 6 August 2023 (UTC)

---

Hello TestWiki.Wiki Community,

I am proposing myself for the system administrator position, to help keep the server running and configured as we would like it, as our current sysadmin isn't as active as they could be, and I think I could help supplement them. My experience consists of having a pretty good understanding of MediaWiki and some PHP, and I am pretty experienced with GitHub and SSH.

Thank you for your consideration,

Zippybonzo (talk) 19:07, 1 August 2023 (UTC)

Questions:

• Im not convinced there’s a huge need for another system administrator. If elected, what would your first action be, to prove there’s a need for an action. X (talk) 19:12, 1 August 2023 (UTC)

To close my open pull request on GH to add checkuser-log to the steward user group as per an above discussion. Zippybonzo (talk) 19:13, 1 August 2023 (UTC)

Discussion:

Support

Oppose

•  Oppose -- I'm sorry to say it: To my knowledge, Zippybonzo is not (has not been) a steward or system administrator on a Wikimedia, Miraheze or other large wikifarm. On these wikis, you only become one after a thorough review and vote. To me, that is a hard requirement for a system administrator. SA has the unlimited power to shut down an entire wiki (database lock and unlock) block anyone and deny anyone user rights. Therefore, this right can only be granted to highly trusted users. At the moment, I am not convinced that Zippybonzo meets this requirement. Of course, technical competence is also very important. But I think that is secondary to the above requirement. Drummingman (talk) 09:59, 5 August 2023 (UTC)

  Just to be completely clear here, I am one of the most trustable users on this wiki, given my reputation on enwiki. Now whether you don't believe that holding trusted positions on the largest wiki in the world is 'trusted' is a different question, which I will not ask. However your definition of trusted is very specific. Based on how you think technical competence is secondary to trust, I don't believe this vote is taking into perspective both the need of a sysadmin for this wiki, and other factors. Zippybonzo (talk) 11:05, 5 August 2023 (UTC)

  •  Oppose -- I agree with Drummingman's thoughts and opinions. I am also opposing due to Zippybonzo's passive-aggressive response to the opposal by Drummingman. Sav • ( Edits | Talk ) 21:17, 5 August 2023 (UTC)

• Strongest oppose Per Drummingman and Zippybonzo is blocked for sockpuppetry and abuse on 3 wikis. He has destroyed moviepedia 2 times and he can hack other accounts. AlPaD (talk) 11:06, 6 August 2023 (UTC)
•  Oppose per Sav. X (talk) 12:02, 6 August 2023 (UTC)

Neutral

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Block review of Zippybonzo

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Although I am involved by participating, consensus is clear here: All arguments in favor of unblocking Zippybonzo, even conditionally, have been refuted, and therefore there is consensus against unblocking Zippybonzo. Justarandomamerican (talk) 00:46, 9 August 2023 (UTC)

---

I'm not one to usually interfere with the runnings of other wiki's, however, it's come to my attention that Zippybonzo was blocked here for some schenanigans that went on last week on another wiki. I don't see a policy in place where harmless pranks can result in a block here, and I'd like to call the community's attention to the block and ask that it be lifted.

While it really shouldn't have happened, generally speaking I don't see off wiki conduct (like a prank) needing something as significant as an indefinite block labelled as a Steward action.

The user on the other end of the prank actually threatened Zippybonzo with violence, which resulted in an indefinite block on my TestWiki along with a lock of their global account. That conduct I can certainly see resulting in an indefinite block. Dusti (talk) 14:47, 7 August 2023 (UTC)

I tend to agree with this assessment. Unless the off-wiki matter involves serious issues such as severe harassment or threats of violence, like noted above, I don't see how people's actions on one wiki should affect their standings on other wikis. Piccadilly (My Contribs | Talk to me) 14:51, 7 August 2023 (UTC)

I oppose. The reason for said block is clearly stated and so, his block should remain active. Sav • ( Edits | Talk ) 15:57, 7 August 2023 (UTC)

A prank requires the other party to laugh. Severely disrupting a wiki and then claiming it was a prank after the owner of said wiki repeatedly attempted to stop said disruption doesn't work. It's like playing a prank on the Wikipedia community as an admin by deleting an article on a president of the United States and then blocking Jimbo. This was intentionally inflicting emotional harm on (trolling) another member of this wiki, Cocopuff2018, and therefore I have no problem with the block. Justarandomamerican (talk) 16:26, 7 August 2023 (UTC)

I simply don’t believe my actions on one wiki should be carried over to an entirely unrelated wiki. The actions were unwise, but I did not violate the policies of that wiki. Zippybonzo (talk) 16:57, 7 August 2023 (UTC) copied to the community portal by X (talk).

This response is.. not good. A wiki or other community does not have to codify: "Disrupting us is prohibited." That is assumed to be the case. Justarandomamerican (talk) 17:05, 7 August 2023 (UTC)

Whilst that is true, there is no reason the block from an entirely unrelated wiki should be carried over to this wiki. Zippybonzo (talk) 17:20, 7 August 2023 (UTC) - moved to the community portal by X (talk).

There is a valid reason for extending the block to this Wiki. Even though this is a Test Wiki, we must uphold responsibility and avoid any form of abuse, a concept that seems to have been misunderstood in your case. Sav • ( Edits | Talk ) 17:31, 7 August 2023 (UTC)

It's not being carried over. You intentionally inflicted emotional distress upon a fellow member of this wiki, which earned you a block on this wiki to prevent further problems and deter your disruptive behavior. Justarandomamerican (talk) 17:33, 7 August 2023 (UTC) (edit conflict)

I tend to agree with Zippybonzo on this point. I think each wiki should be a "fresh start" so to speak, where as long as a user doesn't cause any serious disruption on this wiki, they shouldn't be blocked based on off-wiki matters. If we're going by the principle that Justarandomamerican suggests, then to be honest I would probably be blocked here as well because of issues from thetestwiki.org and Wikimedia. So why is it that off-wiki matters don't count against me but they do for Zippybonzo? Piccadilly (My Contribs | Talk to me) 17:34, 7 August 2023 (UTC)

No, because your issues do not involve trolling members of this wiki. In this case, it actually affects this wiki due to causing emotional distress to its contributors, and deserves a block. Justarandomamerican (talk) 17:37, 7 August 2023 (UTC)

Proposal

I have an idea regarding this block situation. I understand that some undesireable things have happened between Cocopuff and Zippybonzo, but maybe we can unblock Zippybonzo (with a steward's agreement) on the condition that any undesireable behavior here will result in a reblock? I think that's reasonable. Piccadilly (My Contribs | Talk to me) 21:13, 7 August 2023 (UTC)

That sounds reasonable, how about we word it like this: "Any behavior that is disruptive to this wiki, in the judgment of a Bureaucrat, shall result in an immediate indefinite site-wide reblock, account creation disabled, autoblock enabled, with other settings being at the Bureaucrat's discretion." Justarandomamerican (talk) 21:21, 7 August 2023 (UTC)

Yeah that sounds good to me. Piccadilly (My Contribs | Talk to me) 21:36, 7 August 2023 (UTC)

I'd like clarification on what would become of Zippys sysop/IA/crat status, if this proposal was implemented. X (talk) 22:09, 7 August 2023 (UTC)

IA is already removed, and should stay as such for the foreseeable future. Crat shouldn't be allowed until a certain period of time has passed, around 6 weeks IMO, but sysop should be regranted. Justarandomamerican (talk) 22:17, 7 August 2023 (UTC)

I’m going to oppose this alternate proposal due to some discord messages Zippy has left me. You can email/DM me if needed. X (talk) 10:53, 8 August 2023 (UTC)

Please can you provide me evidence of these Discord messages? You have my contact information. Sav • ( Edits | Talk ) 15:11, 8 August 2023 (UTC)

strong oppose, im sorry but i dont trust him at all. and he was just recently block I think it's still too early. Cocopuff2018 (talk) 14:47, 8 August 2023 (UTC)

• Unfortunately, I must oppose at this point in time, as ZB has said privately he is tempted to abuse this wiki. The block will prevent such a thing from happening. Justarandomamerican (talk) 16:31, 8 August 2023 (UTC)

  Echoing the sentiments of @Justarandomamerican, I stand unfortunately oppose as well. Having personally encountered the comments posted by ZB, I agree with the concerns raised. Sav • ( Edits | Talk ) 16:38, 8 August 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Request for Stewardship: Justarandomamerican

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

With no one voting against and the only neutral reservations/abstain being about a (now closed) another wiki, where otherwise no objection came from other users, there is a clear consensus to promote to steward. On behalf of the steward-team, congratulations. Drummingman (talk) 16:05, 27 August 2023 (UTC)

---

I nominate myself for Stewardship due to there only being 1 regularly active Steward, Drummingman. MacFan4000 is semi-active, and Dmehus? He has not been active since the 3rd of July. I've been active here for quite a bit, and it's not really a great idea to have 1 active person taking care of most Steward maintenance tasks, so I volunteer to be the second. Account Security: I have a strong password securing my account and MFA enabled. Justarandomamerican (talk) 20:26, 18 August 2023 (UTC)

Questions

Self-imposed FAQ

1. When will you use the suppression toolset?

   I will use it in any of the following scenarios: Personally identifiable information of anyone being shared without their consent, PII of an apparent minor being shared, anything else that the public at large should not be able to view, as sysop rights are easy to obtain, that is the purpose of the wiki, and external links containing one of those three scenarios. Justarandomamerican (talk) 20:26, 18 August 2023 (UTC)

2. When will you use the check user toolset?

   I will use it only to investigate, respond to, and/or prevent disruption such as sockpuppetry or vandalism, in accordance with the Privacy policy's abuse provision. Justarandomamerican (talk) 20:26, 18 August 2023 (UTC)

Other Questions

1. . What is your take on off wiki/off site behavior impacting a user account here? Let's say on another wiki, unrelated to this site. Dusti (talk) 14:11, 19 August 2023 (UTC)

   I do not feel it warrants a block or other action, unless it materially affects this wiki, such as off-wiki harassment by a contributor to another contributor, or if, in the totality of the circumstances, it could result in disruption here. Justarandomamerican (talk) 14:36, 19 August 2023 (UTC)

Support

1. I'll kick this off with your first support. Dusti (talk) 01:36, 20 August 2023 (UTC)
2. Trusted user. AlPaD (talk) 07:08, 26 August 2023 (UTC)
3. Trusted and experienced user. Sav • ( Edits | Talk ) 08:02, 26 August 2023 (UTC)
4. Trusted user. Chqaz (talk) 17:07, 26 August 2023 (UTC)

Neutral/abstain

1. I’m going to be neutral here, and I feel that Justa should withdraw this and wait. A wiki that the candidate and I were stewards on was recently closed because of actions taken by the steward team. I don’t think that starting an RfS on another TestWiki days after another one was closed, partially because of our actions, is a good look or idea. X (talk) 01:57, 20 August 2023 (UTC)

   This has been discussed at length in private by us two and ZB, a user who is de facto banned by the community on this wiki (declined block review) due to their actions, and it was decided that the closure was wrong overall. Justarandomamerican (talk) 02:06, 20 August 2023 (UTC)

Yes, but that is our personal opinions, not the opinion of the site creator and operator. In his opinion, we completely ruined the wiki. Which is why the above still, regardless, stands. X (talk) 02:09, 20 August 2023 (UTC)

He can operate his site as he wishes, including resetting the wiki even though the community thinks it was wrong, and he could even rule the wiki as an absolute dictator without consequence. There is no rational cause --> effect sequence here: I take action based on off-wiki and on-wiki repeated civility issues, that does not cause the site as a whole to be ruined. I have no other involvement in the points MTzh brought up, I believe, although I do not remember them and they can no longer be accessed. Justarandomamerican (talk) 02:18, 20 August 2023 (UTC)

My point is that a block you placed that, while I do believe it was correct, partially led to the reset and closure of a wiki. I just think it’s too soon. X (talk) 02:34, 20 August 2023 (UTC)

Other comments

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Proposal to merge editor and reviewer

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Phab request created: See T68. X (talk) 12:46, 14 September 2023 (UTC)

---

Rights attached to editer and Rights attached to reviewer are exactly the same and one is enough.--Chqaz (talk) 01:39, 28 August 2023 (UTC)

I would say that the only part of this that can be debated is which right they should be merged into. I say it should be reviewer, as the more sensible name. Justarandomamerican (talk) 15:48, 1 September 2023 (UTC)

I agree. Username (talk) 05:51, 3 September 2023 (UTC)

I also agree that the editor right can just be deleted. X (talk) 11:23, 10 September 2023 (UTC)

I concur, this has my vote. Sav • ( Edits | Talk ) 12:52, 10 September 2023 (UTC)

I agree with merge. AlPaD (talk) 11:29, 14 September 2023 (UTC)

I also agree. TenWhile6 (talk | SWMT) 11:32, 14 September 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

1 year spam blocks- Automatic, or status quo?

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

 Done! Justarandomamerican (talk) 21:51, 2 October 2023 (UTC)

---

Currently, our spam abuse filters are set to block anon users for 6 months, and a human administrator extends it to 1 year upon confirmation of spam. Would it be better to simply have our spam abuse filters block for 1 year? Justarandomamerican (talk) 13:12, 28 September 2023 (UTC)

 Support blocking for one year automatically. X (talk) 17:03, 28 September 2023 (UTC)

 Support--Chqaz (talk) 04:55, 2 October 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Proposal: Remove the ability for IP editing

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

While there is some support, there isn't a strong consensus. Personally I would want to allow IPs to perform legitimate test edits. Since three isn't strong consensus for or against, I will call this unsuccessful. MacFan4000 ^{(Talk Contribs)} 01:52, 26 October 2023 (UTC)

---

I suggest removing the ability for IPs to edit all pages. The sole purpose of this wiki is to test administrator tools, which IPs cannot do. In addition, the only IPs that edit this wiki are used by an LTA for spam, which is mostly caught by an abuse filter. X (talk) 17:06, 28 September 2023 (UTC)

 Support. Username (talk) 19:46, 30 September 2023 (UTC)

 Support--Chqaz (talk) 04:54, 2 October 2023 (UTC)

 Support Sav • ( Edits | Talk ) 07:41, 2 October 2023 (UTC)

I created T69--Chqaz (talk) 12:31, 2 October 2023 (UTC)

Neutral, leaning oppose Oppose. Weighing the pros and cons gives me a neutral opposing stance. This would prevent some abuse, but multiple accounts can easily be created to continue that abuse. In addition, this may have a deterrent effect on good faith users. Justarandomamerican (talk) 12:42, 2 October 2023 (UTC)

Reconsidered, opposing, I think this is overall negative, as it deters good faith users by making them think they are not welcome to test, and prevents abuse only from the laziest LTAs. Justarandomamerican (talk) 21:48, 2 October 2023 (UTC)

 Oppose -- I think it's important that people who want to test feel welcome, even if they would rather not create an account yet. Further per Justarandomamerican. Drummingman (talk) 14:22, 2 October 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Category:Advanced users

Hello, I've observed that Jody recently created this page and combined other sysop groups into it without prior discussion on the Community Portal. Both Justarandomamerican and I have since reverted these edits. Consequently, I'd like to open a discussion regarding the fate of this page—whether it should be retained or deleted. Warm regards, Sav • ( Edits | Talk ) 13:57, 5 October 2023 (UTC)

I don't really see a problem with it. Doesn't seem to be a problematic category, but this function is already done by Category:Administrators and Category:Bureaucrats, and similar, so it's somewhat redundant. EggRoll97 (talk) 19:12, 5 October 2023 (UTC)

I'd say it should be retained, and all the permissions categories should be put into it, to create a category tree. Although I can comprehend what Username was thinking, in that there should be 1 category, the better way to do that is to categorize all the advanced user categories into the advanced users category. Justarandomamerican (talk) 21:44, 5 October 2023 (UTC)

I concur, so keep it as it currently is? Sav • ( Edits | Talk ) 07:01, 7 October 2023 (UTC)

Yes. Justarandomamerican (talk) 14:02, 7 October 2023 (UTC)

Apologies

I deeply regret the oversight that resulted in some of you having your rights removed unfairly. In my sleep-deprived state, I misread "3 months" as "1 month." I want to offer my sincere apologies for any inconvenience this may have caused.

I have taken immediate action to rectify this mistake. All actions against you have been reverted, and your rights have been reinstated. While I won't mention names, I trust that those affected will know who they are.

Once again, I apologize for any frustration or confusion this may have caused. Thank you for your understanding.

Warm regards, Sav • ( Edits | Talk ) 03:26, 14 October 2023 (UTC).

Non-steward oversighters/checkusers - alternate proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

There is unanimity in one area of this proposal, and no consensus for another. There is unanimous consensus to allow non-Stewards to access the suppressor tools, but there is no consensus to allow them to access the checkuser tools. I will implement this myself through pull request within the week starting tomorrow (Sunday, December 3rd). (involved closure) Justarandomamerican (talk) 14:35, 2 December 2023 (UTC)

I propose allowing non-stewards to access checkuser/oversight tools, similar to the above proposal, but without the unblockable right. Being that the implementation of this could result in a lack of transparency with the community, I think that 2 additional groups should be added.

non-steward-suppressor:

With the following rights: suppression-log

Add groups to own account: Suppressor

Remove groups from own account: Suppressor

non-steward-checkuser:

With the following rights:

checkuser-log

Add groups to own account: Check user

Remove groups from own account: Check user

These users can be appointed by either: 1) Community consensus, closed by a steward 2) Steward consensus, at least 2 stewards support giving the right

A user may not hold both suppressor and checkuser rights, unless they apply for steward. X (talk) 17:13, 16 October 2023 (UTC)

•  Support: No inherent problems with this, although NSSs should have suppressionlog as Stewards do without the suppressor flag. Justarandomamerican (talk) 00:47, 17 October 2023 (UTC)

   Amended X (talk) 01:15, 17 October 2023 (UTC)

  Partially supporting. With suppression, I have no problem granting it to non-stewards as well. I therefore support that part. Granting a checkusser to non-stewards is not a good idea in my opinion. That right is so sensitive with privacy that I prefer to keep that with the stewards and since we have 4 stewards of which 2 are active and 1 semi-active, I see no reason to grant it to non-stewards as well. And otherwise, steward elections can always be held. Drummingman (talk) 08:50, 23 October 2023 (UTC)

  I don't think there's a serious actual privacy issue, although I can see your point that someone with non steward checkuser access would be practically on the same level of trust as Stewards. Justarandomamerican (talk) 02:22, 26 October 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Formalize Test Wiki:Blocks and bans as a guideline

This practically just formalizes practice and existing consensus. However, compliance with it should not be mandatory as with policies, but rather strongly recommended. This contains some things that simply aren't worthy of policy (see the blocks section), but it should be some form of community recommendation. Justarandomamerican (talk) 17:28, 21 October 2023 (UTC)

Due to non-participation, I'll withdraw this within 4 days. Justarandomamerican (talk) 20:37, 11 November 2023 (UTC)

Withdrawn. Justarandomamerican (talk) 23:31, 16 November 2023 (UTC)

Block appeal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Though their behavior is utterly unacceptable (as an AuADHD person myself, it's no excuse), I have taken the advice from Dmehus below. Piccadilly, you are indefinitely prohibited from editing Test Wiki due to repeated sockpuppetry. If you wish to be unblocked, you must go through staff@testwiki.wiki, after at least a 6 month abstention from editing Test Wiki, using your main account or other accounts. At least 2 of the current 4 Stewards must endorse your appeal to be unblocked, and they have the discretion to forward it to the community instead. Justarandomamerican (talk) 03:09, 26 November 2023 (UTC)

Piccadilly sent this into the staff email address today: "The issues I have had on the wiki have been making random talk pages, using bad language in some of my edits, spamming random letters, and evading my block through IP addresses. I am not sure of all the reasons I thought any of that would be okay, but I do remember thinking at times "this won't hurt anything" or "I'll undo this right afterwards so nobody will even notice". I definitely should have been thinking more maturely or at least sensibly when doing any testing on the wiki. If I am allowed back, I will be extremely careful in all my tests on the wiki. I also promise to adhere to any conditions that might be set for my unblock, including when I can ask for administrator and/or bureaucrat." Are there any community objections or comments about her return? Justarandomamerican (talk) 23:31, 16 November 2023 (UTC)

Proposal: Ban Piccadilly indefinitely

I would like to propose a site ban of Piccadilly for an indefinite period of time, as the person who posted the block appeal and found CheckUser evidence. Piccadilly, you should take a break from wikis and prove you can stop socking. The fact that you used IPs to evade your block is utterly unacceptable, as you know the consequences of block evasion and sockpuppetry. You also seem to lack the ability to stop yourself, which is required if you want to be here, and you lacking it has caused severe disruption. Justarandomamerican (talk) 16:56, 17 November 2023 (UTC)

• Support as such behavior is really unacceptable. 64andtim (talk) 08:43, 24 November 2023 (UTC)
• I don't know the circumstances that gave rise to their original block, or whether the block was imposed by a mainly testing permissions bureaucrat or Steward. If, and only if, the original indefinite block was either (a) made by a Steward directly or (b) reviewed thoroughly and endorsed by a Steward, then I support an indefinite block (you can call it a ban, if you want, but I don't personally like the word ban as that implies permanence here and we also don't have a "site ban" policy (nor do I think we need one), provided it's a steward-imposed indefinite block/ban that carries the community's endorsement but would oppose any sort of "community ban" as, fundamentally, I tend to oppose community bans for the following several reasons, notably:
  1. Philosophically speaking, we elect amongst ourselves Stewards, whom we entrust to make these decisions. Each Steward has different criteria for effecting certain user control measures in terms of restriction, severity, and duration. Users are always provided an opportunity to appeal, then an uninvolved Steward should review the circumstances and decide whether the sanction is appropriate, restorative and protective but, crucially, not punitive. If we're to then second guess ourselves and defer to the community on every major user control decision, what is the purpose of Stewards after all?
  2. This is more of a Test Wiki-specific reason, but Test Wiki's community, aside from several core users is transitory in nature. Users come and go frequently and often have to "follow the herd mentality" of a few in community discussions, which is not a substantive community consensus
  3. I suspect the behaviour is more of Piccadilly's reversion to the mean of not being to help themselves. They're good-faith, have made positive steps in terms of reforming themselves and even been a constructive contributor for several months, but then they revert to non-constructive gibberish outside of their own userspace and clearly marked test pages. The sockpuppetry is more of a symptom of their self-disclosed ADHD + autism, in being frustrated by stewards not responding to their appeal. That's not to excuse it, but I do think it provides a mitigating circumstance

In summary, subject to the conditions I described above, I think they need a clear break, so no objections from me in imposing a steward-imposed indefinite block/ban on Test Wiki, provided it's made clear that (a) the appeal venue is to staff[at]testwiki.wiki and to Stewards and (b) that an appeal will only be considered after a reasonable break (of say, a minimum of 1 and maximum of 6 months) from date of last confirmed sock (note that each confirmed sock would reset the appeal date, which is why, in Piccadilly's case, a 1 month minimum block period can be the minimum sanction necessary; if they continue, it effectively becomes a longer block because the appeal date keeps getting pushed out, but, if they can keep their nose clean and steer clear, then they've shown they still have the capacity to follow direction from Stewards and, by extension, the community, which is always our aim). If the above is true, Justarandomamerican, please feel free to self-close this and impose the block/ban as such and make clear your appeal conditions, which could include appeal to a single steward alone or require support from a plurality of stewards (i.e., at least 50%). Dmehus (talk) 02:30, 26 November 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Move Test Wiki:Request permissions to Test Wiki:Request for permissions

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

 Done. Justarandomamerican (talk) 20:47, 2 December 2023 (UTC)

Per Wikipedia, their requests page is under that title. Username (talk) 19:56, 4 November 2023 (UTC)

 Support per consistency. Sav • ( Edits | Talk ) 20:03, 4 November 2023 (UTC)

Doing... as relatively uncontroversial. Justarandomamerican (talk) 20:46, 2 December 2023 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Merry Christmas!

Merry Christmas to all those here at The Test Wiki.

Have a wonderful day and all the best for 2024!

Lots of love, Sav • ( Edits | Talk ) 17:51, 24 December 2023 (UTC).

userRightsManager gadget is broken

I tried to approve a user's permission request with the userRightsManager gadget and found that the gadget is not working properly. Can the interface administrators fix this issue? LisafBia (talk) 19:07, 1 January 2024 (UTC)

I've reviewed the code and tested the script. It appears to be working for me. Could you please provide more details on what isn't working for you? X (talk) 14:20, 26 January 2024 (UTC)

 Fixed, the move to Request for permissions broke the script initially. Justarandomamerican (talk) 14:21, 26 January 2024 (UTC)

Makes sense, thanks for the fix. X (talk) 14:23, 26 January 2024 (UTC)

Request for Suppressor right

I request oversight rights from our community for 2 days. I will only use it for testing and I promise not to compromise anyone's privacy. LisafBia (talk) 21:05, 1 January 2024 (UTC)

 Not done as suppressor is not a test right and will not be given to those who are not stewards or community elected non-steward suppressors, for obvious privacy concerns. X (talk) 19:46, 25 January 2024 (UTC)

One question: as the suppressor right isn't a test right, is the non-steward suppressor right also a non-test right? – 64andtim ^(talk) 20:11, 25 January 2024 (UTC)

Indeed. And therefore it is not meant to be tested. It is meant only for serious suppression.

The user right is not intended as a test flag like most roles here. It is intended only for serious suppression. System administrator, steward, checkuser, suppressor and non-steward suppressor are emphatically not test roles. Drummingman (talk) 20:25, 25 January 2024 (UTC)

Interface admin is also somewhere in the middle. It isn't a testing right, but some people do use it for that. X (talk) 20:28, 25 January 2024 (UTC)

My IA right

Could a steward remove my IA permission, please? Thanks a lot, and goodbye! Username (talk) 06:23, 13 January 2024 (UTC)

Dear, @Username  Done. Thank you for your edits, we look forward to seeing you again. Kind regards, Drummingman (talk) 10:21, 13 January 2024 (UTC)

---

I thought I was ready to go. But I guess I feel like staying longer considering I've worked so hard on keeping this wiki organized, and I have left some things that have yet to look completed. Can somebody grant me my rights back, please? Thank you! Username (talk) 21:43, 28 January 2024 (UTC)

@Jody: I have granted you back the crat and admin rights. A steward will have to do the IA bit. EPIC (talk) 21:53, 28 January 2024 (UTC)

Glad to have you back. Courtesy ping @Justarandomamerican & @Drummingman. X (talk) 21:57, 28 January 2024 (UTC)

 Done, welcome back. Drummingman (talk) 22:22, 28 January 2024 (UTC)

Thanks, all. Username (talk) 23:27, 28 January 2024 (UTC)

Proposal to change an abuse filter warning

Hello, everybody.

I propose moving [[MediaWiki:Newuser-externallinks]] to MediaWiki:Abusefilter-warning-newuser-externallinks, and changing the text of the filter warning message to something like this:

Warning: An automated filter has identified this edit containing external links. Test Wiki may not be used as a vehicle for promotion, and may result in being blocked from editing. If this edit is constructive, you may click "Publish changes" again to confirm it. If you received this message in error, please inform an administrator of what you were trying to do.

Any inputs or concerns about this? If there are no objections, I'll be happy to do those changes in a few days. Thanks. – 64andtim ^(talk) 18:27, 25 January 2024 (UTC)

As the original creator of the customized warning, I  Support this change. Justarandomamerican (talk) 01:08, 26 January 2024 (UTC)

 Done. X (talk) 13:07, 26 January 2024 (UTC)

RFC: Clarify the inactivity policy for Non-steward suppressors

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

 Passes. Non-steward suppressors will be held to a 3 month inactivity requirement. X (talk) 18:54, 28 January 2024 (UTC)

---

This is a rather simple proposal. Shall the inactivity policy:

1. Be amended to include a 3 month inactivity period for Non-steward suppressors,
2. Be amended to include a 1 year inactivity period for Non-steward suppressors; or
3. Be amended to include another inactivity period for non-steward suppressors?

Justarandomamerican (talk) 17:38, 26 January 2024 (UTC)

 Support 1 as proposer. 3 months seems plenty enough, rather than the 1 year inactivity period granted to Stewards and Sysadmins. Justarandomamerican (talk) 17:39, 26 January 2024 (UTC)

 Support option #1 per Justa. X (talk) 17:41, 26 January 2024 (UTC)

 Support the #1 option. – 64andtim ^(talk) 18:05, 26 January 2024 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Another proposal to import Edit filter warning template

I was thinking if I could import the Edit filter warning template from the English Wikipedia, but leave out the report error since there is no edit filter false positive page on Test Wiki. Any inputs, concerns or objections?

When triggering an abuse filter, it shows a red box with text; maybe we could add that proposed template under the name "Abuse filter warning", and protect it under an appropriate protection as a high-risk template? Thank you. – 64andtim ^(talk) 18:05, 26 January 2024 (UTC)

We can also redirect people to here (the community portal) to report false positives, or to contact an administrator directly. I think having some form of template would make things easier, so no objections. Justarandomamerican (talk) 18:07, 26 January 2024 (UTC)

One more question: is bureaucrat protection appropriate when protecting a high-risk template? – 64andtim ^(talk) 18:10, 26 January 2024 (UTC)

In this case, it would be, since the template would be used in the interface, and not protecting it as such would allow users without the edit interface right to edit the interface. You can use discretion when protecting pages. Justarandomamerican (talk) 18:12, 26 January 2024 (UTC)

Fine by me! X (talk) 18:25, 26 January 2024 (UTC)

Since there are no objections, I'll implement them, but do we keep the report error button that can redirect here to the community portal or not? – 64andtim ^(talk) 15:42, 27 January 2024 (UTC)

Yes, you can redirect it to the community portal. X (talk) 15:44, 27 January 2024 (UTC)

 Done, but it took a little bit of trial and error for the url to actually work. – 64andtim ^(talk) 16:37, 27 January 2024 (UTC)

Mobile edit

Does anyone have an idea why this and this was marked as mobile web edits, considering that I am on a computer? EPIC (talk) 19:10, 28 January 2024 (UTC)

That is weird, never heard of that happening before. Were you using mobile view when making the edits? X (talk) 19:21, 28 January 2024 (UTC)

It's possible you switched to mobile view and didn't realize it, like X said above. Justarandomamerican (talk) 19:25, 28 January 2024 (UTC)

I was using the normal desktop view, but checking e.g. FuzzyBot, it seems to be the same for some of those edits as well. EPIC (talk) 19:26, 28 January 2024 (UTC)

As far as I know, FuzzyBot uses the same tags as the edit/log entry that was made to cause it to perform an action. I'm not sure what could have caused that software-wise. @MacFan4000: Not urgent at all, but this is an odd technical situation. Justarandomamerican (talk) 19:28, 28 January 2024 (UTC)

New filters made today

Today, I have decided to make filter 121 which prevents personal attacks or harassment on user/user talk pages, and filter 122, which prevents new users from editing others' user pages.

Confirmed users and sysops may edit user pages, but they may not add {{unlocked userpage}} on a random user page; it may only be done by the user themselves or a steward.

Any opinions or input? Thanks. – 64andtim ^(talk) 19:10, 29 January 2024 (UTC)

LGTM. X (talk) 19:38, 29 January 2024 (UTC)

Mind if I test adding the unlocked userpage template on your userpage if this can be prevented by the filter? – 64andtim ^(talk) 19:52, 29 January 2024 (UTC)

Go ahead. X (talk) 19:53, 29 January 2024 (UTC)

Per Special:AbuseLog/5852, the filter is working as intended. – 64andtim ^(talk) 19:56, 29 January 2024 (UTC)

Piccadilly socks

I'm going to be combing over the logs and trying to compile a list of all the account Piccadilly has used and block them all with the same reason. I then might make some LTA pages like Wikipedia has to inform people of a little more about how to detect and deal with specific LTAs. X (talk) 22:52, 29 January 2024 (UTC)

Maybe should we disable filter 92? The target of the filter hasn't returned since 2022. – 64andtim ^(talk) 23:27, 29 January 2024 (UTC)

It is very specific and isn't hurting anything as is so I don't know if there's really a need to disable it. X (talk) 23:28, 29 January 2024 (UTC)

You know what? I agree, maybe we should keep it enabled. – 64andtim ^(talk) 23:34, 29 January 2024 (UTC)

Yeah, they were a pretty big issue "back in the day". Would hate to have them come back because they know our protection has been disabled. X (talk) 23:35, 29 January 2024 (UTC)

 Done, feel free to improve. X (talk) 02:22, 30 January 2024 (UTC)

RFC: Allow non-steward suppressors to perform "steward actions"

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Resolved. Justarandomamerican (talk) 00:15, 30 January 2024 (UTC)

Hi all,

Looking back in my original proposal to create the non-steward suppressor group, I found that I forgot to add the ability to perform steward actions to the list. I think this is quite needed as suppression blocks are a large part of the job, in addition to evidence for blocks being hidden behind a suppression. For transparency, see User talk:Justarandomamerican#Suppression log for part of the reason why this is being proposed. Thank you. X (talk) 00:00, 30 January 2024 (UTC)

Discussion:

Steward actions and other special types of blocks are mainly governed by long standing practice. In this case, our information page on these practices includes a suitable alternative meant for suppression reasons, such as completely inappropriate vandalism or personal information without consent that has to be suppressed. If this proposal is about allowing the group to basically become steward-lite through formal capacity, then  Oppose. NSSs should stay within their scope of suppression. Justarandomamerican (talk) 00:05, 30 January 2024 (UTC)

No, that is not at all the goal of the proposal. It is strictly to allow them to call blocks steward actions. My apologies, I should have worded that better. X (talk) 00:07, 30 January 2024 (UTC)

Withdrawn per Justa's solution. X (talk) 00:11, 30 January 2024 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Abuse filter request

I'm not quite confident in using regex the abuse filter rules yet, so can someone who is create an abuse filter that disallows common phrases used by Piccadilly? Check their deleted contributions for details (and most things they do that need to be disallowed need no exceptions.) Justarandomamerican (talk) 02:29, 30 January 2024 (UTC) edited to correct 02:40, 30 January 2024 (UTC)

I'm not really familiar with regex, but I can design the code and body of said filter. Will create it, but someone else may need to create the regex. – 64andtim ^(talk) 02:31, 30 January 2024 (UTC)

Thanks! I'm not too inclined in the specifics, so likely made a mistake in saying regex, AbuseFilter rules are a custom language. Justarandomamerican (talk) 02:34, 30 January 2024 (UTC)

I have done a lot of trial and error with abuse filters, so I've managed to gather a little knowledge. I can help too! X (talk) 02:38, 30 January 2024 (UTC)

Will create the message later targeted not just for the intended target, but for all LTAs. In addition, another special message if the filter is set to both disallow and block. – 64andtim ^(talk) 02:42, 30 January 2024 (UTC)

Never mind, looks like filter 88 is active. – 64andtim ^(talk) 05:36, 30 January 2024 (UTC)

User:Void

Void's userpage is still steward protected even though they are not a steward. Please unprotect. X (talk) 18:03, 30 January 2024 (UTC)

 Done by @Justarandomamerican X (talk) 23:55, 30 January 2024 (UTC)

RecentChanges pages

Here, I've put this page as a candidate for deletion:

• Test Wiki:RecentChanges

I don't see a need for this page considering it has always been unused. Additionally, we have always been maintaining this message and it has existed slightly longer than the link listed above. Username (talk) 00:45, 31 January 2024 (UTC)

Fine by me. X (talk) 01:28, 31 January 2024 (UTC)

---

 Done by Justarandomamerican. Username (talk) 01:50, 31 January 2024 (UTC)