New requirements for user signatures/zh

許多維基對於使用者自訂簽名有一些要求. 編輯團隊正在徵求您對該計畫的意見，以將其編寫到維基百科的軟體中. 這樣能夠讓在討論頁面上回复特定留言及使用其他一些工具更加方便.

您可以在下面找到建議內容及其原因的詳細資訊：


 * 團隊正在尋求什麼反饋： 意見：您的反饋
 * 為什麼提出此更改： 背景：為何更改？
 * 提出了什麼更改： 計畫：簽名驗證要求
 * 這些更改會怎麼影響您： 影響：變化的影響

如果沒有發生重大阻礙，則可能在2020年4月進行此更改. 如果團隊需要根據您的反饋做出重大更改，則將需要更長的時間.

意見：您的反饋

團隊想要您對此提案的任何反饋.

請您在討論頁發表有關這些問題的留言.


 * 1) 簽名驗證會在您的維基上造成任何問題嗎？
 * 2) 您認為團隊在進行此更改之前應該注意些什麼？
 * 3) 不符合新限制的現有簽名應要如何處理？ 例如，是否應禁止使用它們？

請不要因上述問題而限制想法，團隊希望聽到您想分享的任何反饋.

背景：為何更改？

在2019年，來自20個維基媒體計畫和用戶組的志願者及維基媒體基金會的工作人員，參與了討論頁諮詢，為了定義維基上更好的交流工具.

這次諮詢的結果之一是請求回覆討論頁面上特定留言的更簡便方法.

為了使此功能正常運作，該軟體需要簽名是「機器可讀的」以能夠更可靠地檢測使用者的留言並允許對其回覆.

問題是，儘管許多維基已經有必要的簽名要求，但是這些要求並未包含在軟體中. 這增加了有人設定破壞維基約定的簽名的可能性，且可能使人們更難以參與討論.

額外簽名格式一致性能改善現有功能，例如「提及」通知，僅在能夠從您的編輯中檢測到簽名時才發送通知.

計畫：簽名驗證要求 The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature. Under the Editing team's proposal, existing signatures will *NOT* be affected. 禁止一些無效的HTML和其他Linter錯誤 Most importantly, this change would disallow unclosed formatting tags, like or the corresponding wikitext markup, , without a matching closing tag (in this case,  or  , respectively). Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.

The check would also identify misnested tags, like  (either both of the , or both of the  , tags should be on the outside), and stripped tags, which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above).

Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like  and . While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors.

A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at Help:Extension:Linter#Documentation of lint issues.

Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to Parsoid. 要求連結到使用者頁面、討論頁或貢獻頁 Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page. For example, "mention" notifications are not sent, and forthcoming DiscussionTools will not allow replying to comments with these invalid signatures. Gadgets and other tools that interact with signatures also may not work as expected.

This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software. 在簽名中禁止“嵌套”的替換引用 Some use of subst: markup and tildes would also be disallowed in signatures. Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments. All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software. Simple subst: markup is still allowed.

影響：變化的影響

現有簽名會發生什麼改變？

任何在新規則下無效的現存簽名將仍允許（祖父條款） 當您查看偏好設定時將會看到警告消息. 如果您嘗試更改簽名，新的簽名必須有效. 若您不修改它，當您簽名時仍會繼續使用舊的無效簽名，而且您能夠不受影響地修改其他偏好設定.

我們正在尋找您認為現存無效簽名是否要禁止的反饋. 如果禁止無效簽名，受影響的使用者在他們的留言簽名時將會插入預設簽名，直到他們修正自訂簽名.

這些更改何時會進行？

請在2020年3月31日前留言. 編輯團隊將在4月初對此項目的做出相關決定. 結果將會發布在討論頁.

如果沒有發生阻礙，則可能在2020年4月進行此更改. 如果團隊需要根據您的反饋做出重大更改，則會推遲此日期.

我們如何知道有哪些更改正在進行？

要部署此更改時，我們將在Tech/News中再次發送通知.

簽名驗證錯誤看起來的樣子如何？

HTML/Lint錯誤包括了指向相關Lint錯誤現有文檔的連結（例如Help:Extension:Linter/missing-end-tag），以及用來醒目標示簽名中含有問題部分的按鈕.

必要連結錯誤包含了可供使用的範例維基語法.

Outcome
The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified.


 * 1) 禁止一些無效的HTML和其他Linter錯誤
 * The scope of these changes will be reduced. Misnested and stripped tags will be rejected.  Some low-priority errors will still be accepted.  Specifically, obsolete HTML tags like   and   will not be banned at this time.  This decision does not prejudice any future decision for or against removing these obsolete HTML tags.
 * 1) Require a link to user page, talk page or contributions
 * This will be implemented as originally planned.
 * For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages. Thus, a signature of  would be acceptable (one local link, one link to another wiki), but a signature that includes only links to another wiki, or only redirects from a former username, will be invalid.  This is for technical reasons.
 * 1) Disallow "nested" substitution in signature
 * This will be implemented as originally planned.

The process for implementing this change is:


 * A general announcement will be made in Tech News when the new requirements are deployed.
 * Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.
 * Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.
 * Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.

Third-party wikis will be able to enable this change manually.

注释