@Kadi, Does this mean that sysops will also be able to grant the permission?

@Dreamy_Jazz, I haven’t tested this with other filters, but if the issue where you cannot save the edit after a warning always occurs, this is a problem that requires an immediate fix.

Oops, I linked by mistake another gerrit change to this task. Is there a way to remove this link? In the gerrit itself I already fixed the problem. Sorry!

On he.wiki, common edit summaries are הז"י and הפרת זכויות יוצרים. Less common, and somewhat ambiguous but still often suggestive of copyright infringement, are העתקה and הועתק.

Edits on hewiki from the recent period (starting from the beginning of May): 1, 2, 3

I've sent patches to the master branch and the REL1_44 branch. I'm not sure if the policy allows introducing changes that are not critical security issues. If possible, I believe this is something that should be included in 1.44 and not just in 1.45. Thank you for the report!

@STei-WMF The community (hewiki) has approved the change. When would it be possible to deploy it on our end? Thanks.

There is also an open discussion on the Hebrew Wikipedia, and so far, everyone seems to be in favor. If no objections are raised by the end of the standard one-week discussion period, when will it be possible to deploy the change there?

I came here for the same reason - I happened to come across an edit tagged as "T144167" and thought it might be an error. Is there an intention to address this? If not (at least in the near future), I believe a clear description of the tag should be provided so that it is clear what needs to be fixed in the articles themselves.

That's right, my mistake. I corrected it.

Thanks everyone!

Agree with @Fuzzy's suggestion above.

In T275319#9813641, @Fuzzy wrote:

However, I suggested a straightforward change to address our immediate need, which is using 2*$wgMaxArticleSize as the limit for the page post-expand include size.

It doesn't make sense that because in Hebrew letters each character counts as two bytes, in the Hebrew language we can insert texts that are half as long as in languages written in Latin letters.

@Anoop The difference in gender already exists, and we just wanted to add shortcuts to the "משתמש" (user) space from several names and genders.
Thank you!

Hi @Anoop.
It seems that the creation of the shortcut to the משתמש (user) space did not work as we wanted.
My intention was to create a shortcut from the names "מש", "שמש", "משת" and "שמשת" to the space, like all the other abbreviations, and not define it as another name for the space. What stems from this problem is that there are user talk pages named "שמש" (both from the recent changes page, both in the page title and in the link).

Great. I'd be happy to wait for final approval from Hyphen (which has been a little less active lately).
Thank you very much for the great investment.

Looks good, but still lacks what I wrote in paragraph 2. Thank you for your investment.

I would love to receive the final code, thanks!

@Anoop Sorry for the late reply.
4 small notes:

1. It seems to me that using $wgExtraGenderNamespaces is unnecessary, and you could put it in $wgNamespaceAliases. Our goal is not to rename the user space, but to add a shortcut, like all other shortcuts. I think it could be:

		'מש' => NS_USER,
		'משת' => NS_USER,
		'שמש' => NS_USER_TALK,
		'שמשת' => NS_USER_TALK,

2. In addition, we want to change the space "portal" (פורטל) to "מדור", similar to changing "category" to "תגית" (tag). How can this be done?
3. Besides adding the draft space, we also want to add shortcuts to it:

		'טי' => NS_Draft,
		'שטי' => NS_Draft_TALK,

4. Other shortcuts, which for some reason do not appear yet:

		'מד' => NS_Portal,
		'שמד' => NS_Portal_TALK,

Hope I didn't miss anything...
Thanks!

I only need it for hewikinews, and not for all Hebrew wiki sites. Is it also done through there?

@Anoop Some changes:

'wgNamespaceAliases' => [
	'+hewikinews' => [ // T349581
		'מי' => NS_SPECIAL,
		'ש' => NS_TALK,
		'מש' => NS_USER,
		'משת' => NS_USER,
		'U' => NS_USER,
		'שמש' => NS_USER_TALK,
		'שמשת' => NS_USER_TALK,
		'וק' => NS_PROJECT,
		'שוק' => NS_PROJECT_TALK,
		'וח' => NS_PROJECT,
		'שוח' => NS_PROJECT_TALK,
		'קו' => NS_FILE,
		'שקו' => NS_FILE_TALK,
		'מו' => NS_MEDIAWIKI,
		'שמו' => NS_MEDIAWIKI_TALK,
		'תב' => NS_TEMPLATE,
		'שתב' => NS_TEMPLATE_TALK,
		'עז' => NS_HELP,
		'שעז' => NS_HELP_TALK,
		'קט' => NS_CATEGORY,
		'תג' => NS_CATEGORY,
		'שתג' => NS_CATEGORY_TALK,
		'שקט' => NS_CATEGORY_TALK,
		'פ' => /* Portal */ 100,
		'שפ' => /* Portal talk */ 101,
		'Portal' => 100,
		'Portal_talk' => 101,
		'Draft' => 118,
		'Draft_talk' => 119,
		'י' => /* Module */ 828,
		'שי' => /* Module talk */ 829,
	],
],
'wgExtraNamespaces' => [
	'hewikinews' => [
		14  => 'תגית',
		15  => 'שיחת_תגית',
		100 => 'מדור',
		101 => 'שיחת_מדור',
		118 => 'טיוטה', // Draft - T349581
		119 => 'שיחת_טיוטה',
	],
],

Through $wgExtraNamespaces I defined namespace number 14 as "תגית" (tag), and not as the default - "קטגוריה" (category). Should I add to "wgNamespaceAliases" an abbreviation from the old name, or is it automatic? Thanks, Neriah.

The title "Unchecked" has been removed. @Shalomori123 Was there anything else we wanted in this matter?

The fault gets worse! There are runs that haven't worked for a few days (ex: https://meta.wikimedia.org/wiki/Special:GlobalRenameProgress/Ne_Shokot_Pinolkwane - started 4 days ago and nothing moved.) Needs urgent treatment!

@Teles Checking now I couldn't find any. Do you still have the problem?

In my opinion, this would also be useful for other journals [e.g., the deletion and protection journal], which sometimes also have bots (for example, bots that protect the main page templates and bots that delete references from draft).

@Aklapper Seems like a good idea. can you send it there?

@Aklapper Is there a way to speed up the treatment? This task went unanswered for a long time.

Hello!
The request has been pending for several months without treatment. Is there anything to do?

@Zabe, So can you add?

@Zabe Is it also possible to enable the "editautoreviewprotected" bot (allow it to edit pages protected by the new protection)?

@Zabe Can you then install only the first protection? (Not by the interface editors)

@Zabe So how is there such a thing in hewiki?

@Zabe Are you planning to remove the interface editor permission?

@Zabe, I do not know if it is possible to create a new permission, because I did not ask in wikisource if it is possible. Is it possible without creating a new permission?

yes.

@Ladsgroup, @Zabe When will they handle the request? I opened the vote on interface protection for this. If this is an extension, I'll open a vote on it.

@Ladsgroup what? I did not understand...

yes.

@Urbanecm The main page templates need to be protected with high protection, and there are also non-sysop users who want to edit them. Now they are condemned that only those with 4 days of experience can edit, but want to raise it. I defended all these patterns, because of the corruption. It is necessary. I do not want anyone to be able to create an account, wait 4 days, and destroy the main page. Need higher protection. And as for interface protection, I wanted it for the "edit posts".

OK.

The Hebrew Wikipedia already has it, right?

Do you want the appropriate code for your server?

Send the right code for you?

@Aklapper @ZabeMath I do not understand. what am I supposed to do now? Turn elsewhere?

So when will it work?

It did not work.

@Urbanban,
sysop could not yet grant reviewer permission.