User:Tailsultimatefan3891/Wiki changes to propose/Old/id

The following page documents a proposal in draft. This proposal has not yet been elaborated and approved by the community or a system administrator. It may be modified with or without prior community approval.

Jika Anda bukan penutur bahasa Indonesia atau ingin mengubah bahasa, silakan ubah dari bahasa di atas.

I have been working on it as a draft for a couple days as User:Tailsultimatefan3891/Wiki changes to propose. I have seen a couple of lacking permissions and we could need changes to the wiki, but I couldn't request them separately as I will get partially blocked from community portal. The all proposals are as follows, however, not every proposal will be passed, but multiple proposals may be passed at once. I have also made the flexibility for people to make some choices.

1. Add Consul Permission: I have noticeably seen a couple of times where policies are bureaucrat-protected. However I can see and we could request to add the consul permission to prevent common bureaucrats from changing such policies especially major edits. As a result we can make a permission in between bureaucrat and steward but please this is not to be confused with the consul permission on Public Test Wiki on Miraheze. In addition, consuls could also add and remove interface administrator, abuse filter administrator, blocked from abuse filter, suppressor, CheckUser, non-steward CheckUser, non-steward suppressor, et al rights. We could also add a level of protection meaning "Allow only consuls" used for edit, move, protect, and delete. Abuse filter administrator rights are packed in the consul permission. Please note that consuls can add or revoke consul rights. Again, to be a consul, an election must be held at the community portal. A consul term can be served for 6 months from last activity, again, those rights can be granted within 1 hour of revocation, otherwise, a reconfirmation vote election will be held.
2. Switching from reCAPTCHA to hCaptcha: I could have known that some MediaWiki sites used hCaptcha. reCAPTCHA is commonly used, however since Google's services and products are banned in China, due to its strict policies by the Great Firmware of China, reCAPTCHA being one of them, hCaptcha is available even in China, so try it, hm? Instead of users having to be requested in China all the time, it can reduce the amount of users to be requested or the requirement of using a VPN to not request an account and make an account all indepedently. You could switch it to Turnstile, but there are some restrictions on Turnstile since this is owned by Cloudflare, and it is a CAPTCHA alternative. And do not try to use e-CAPTCHA because it is a fake CAPTCHA (uses "Click allow if you are not a robot"), and do not implement other CAPTCHAs that say "Click allow (if you/to verify that/to confirm that) you are not (a) robot" as it is a fake CAPTCHA.
3. Reinstate Researcher Permission: To be available for testing and could be granted to or revoked from non-admins. It can view deleted history and pages.
4. MassMessage sender permission add: To be available for testing and could be granted to or revoked from non-admins. Sends mass messages.
5. Add flooder permission: To be available for certain tasks for administrators, for example, blocking many proxies or deleting a huge amount of spam pages, anything that is not controversial.
6. Add abuse filter bureaucrat permission: It can be granted or revoked by consuls allowing those in this group to grant or revoke abuse filter administrator or blocked from abuse filter groups.
7. Allow administrators to revoke admin rights from their own account: That's called resigning, however, they cannot revoke other administrators' admin rights.
8. Add the non-steward CheckUser rights: Can be used for non-testing purposes, can add or revoke CheckUser permissions to or from their own account. Can be granted by consuls. I've seen a number of Wikipedia administrators (sometimes bureaucrats) aged 18 or older that signed the Wikimedia Foundation confidentiality and non-disclosure agreement (e.g. Ponyo, verify) that often do not have the right to revoke bureaucrat rights from accounts (and sometimes cannot add or remove administrator or bureaucrat rights since they are not a bureaucrat) have CheckUser.
9. More flexibility with longevity of the steward permission: The inactivity policy for stewards can be inactive for 9 months as the maximum limit instead of 6 months, to be make room for consul's permission 6 months.
10. Add extended confirmed permissions and protection level: Extended confirmed users are packed into the administrator privileges. They are already granted to administrators. Extended confirmed permissions are granted when the user had made 500 edits and had been on the Test Wiki for at least a month (30 days). Can be used for testing. While not implicit, it can still be automatically or manually granted.
11. Add template editor permissions and protection level: Template editors are packed into the administrator privileges. They are already granted to administrators. Commonly used to edit some high-risk templates and modules. Not to be confused with the template administrator permissions. Can be used for testing.
12. Add template administrator permissions: Template administrators are used for templates and modules that require a high-risk sensitivity and may cause (effective/immmediate) damage if improperly edited. Unlike template editors, they are not packed into the administrator privileges and cannot be granted to their own account. They can edit pages not usually approved to administrators. No regular administrator can grant or revoke it, however bureaucrats can grant or revoke it as long as they are using this right properly. This permission is usually not meant for testing.
13. Add IP block exemption permissions: This permission is used for bypassing Tor blocks and open proxy and VPN blocks. It can be granted or revoked by administrators, bureaucrats and stewards (and obviously, system administrators). It is packed into the administrators rights and can be used for testing.
14. Add comments feature and comment administrator permission: Comments can be used for testing as long as it's not inappropriate for Test Wiki. Comment administrators can monitor it. Comment administrator permission can be used for testing and available in the administrator group.

So, the following sequences of code in PHP are as follows:

• $wgAddGroups['consul'][] = ['sysop', 'bureaucrat', 'checkuser', 'steward', 'reviewer', 'patroller', 'autochecked', 'autopatrolled', 'non-stewardsuppress', 'non-stewardcheckuser', 'abusefilter-restricted', 'abusefilter-admin', 'consul']
• $wgRemoveGroups['consul'][] = ['sysop', 'bureaucrat', 'checkuser', 'steward', 'reviewer', 'patroller', 'autochecked', 'autopatrolled', 'non-stewardsuppress', 'non-stewardcheckuser', 'abusefilter-restricted', 'abusefilter-admin', 'consul']
• $wgAddGroups['steward'][] = ['sysop', 'bureaucrat', 'checkuser', 'steward', 'reviewer', 'patroller', 'autochecked', 'autopatrolled', 'non-stewardsuppress', 'non-stewardcheckuser', 'abusefilter-restricted', 'abusefilter-admin', 'consul', 'steward']
• $wgRemoveGroups['steward'][] = ['sysop', 'bureaucrat', 'checkuser', 'steward', 'reviewer', 'patroller', 'autochecked', 'autopatrolled', 'non-stewardsuppress', 'non-stewardcheckuser', 'abusefilter-restricted', 'abusefilter-admin', 'consul', 'steward']