New requirements for user signatures/vi

Nhiều wiki có các quy tắc về các chữ ký thành viên tùy biến. Nhóm phát triển sửa đổi đang cần bạn cho ý kiến về đề nghị chuyển một số quy tắc này sang mã nguồn trong phần mềm của Wikipedia. Thay đổi này sẽ làm cho người ta có thể trả lời các lời nhận xét riêng trong trang thảo luận một cách dễ dàng hơn và sử dụng một số công cụ khác.

Bên dưới có thêm chi tiết về đề nghị và lý do:


 * Nhóm đang cần các thông tin phản hồi sau: Phản hồi: Phản hồi của bạn
 * Tại sao đề nghị thay đổi này: Bối cảnh: tại sao cần thay đổi?
 * Các thay đổi được đề nghị: Đề nghị: các quy tắc phê chuẩn chữ ký
 * Các ảnh hưởng đến bạn: Ảnh hưởng: ảnh hướng của các thay đổi



Phản hồi: phản hồi của bạn
The team wants your feedback about this proposal.

Please post your comments about these questions on the talk page:


 * 1)  Would these signature validations create any problems on your wiki? 
 * 2)  What do you think the team should be aware of before making this change? 
 * 3)  What should be done about existing signatures that don't meet the new limits?  For example, should they be disallowed?

Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.



Bối cảnh: tại sao cần thay đổi?
In 2019, volunteers from 20 Wikimedia projects and usergroups, along with staff from the Wikimedia Foundation, participated in the Talk pages consultation. It was an effort to define better tools for on-wiki communication.

One of the outcomes of this consultation was a request for an easier way to reply to specific comments on talk pages.

In order for this feature to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them.

The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself. This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.

This additional consistency in the format of signatures would improve existing features, like "mention" notifications, which are only sent if the signature can be detected in your edit.



Đề nghị: các quy tắc phê chuẩn chữ ký

 * This is an archived record of a previous proposal. Please do not modify it. A summary of the conclusions reached is in the  section.

Nếu không gặp trở ngại lớn, thay đổi này có thể xảy ra vào tháng 4 năm 2020. Nếu nhóm cần thực hiện các thay đổi lớn do lời phản hồi của các bạn, quá trình này cũng có thể tốn thêm thì giờ.

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.



Không cho phép một số trường hợp HTML hư hỏng và lỗi Linter khác
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 this address.

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.



Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp
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. (The link must be for a page on the wiki the signature is used on; or  – e.g., to a different language of Wikipedia – are not sufficient.) 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.



Không cho phép nhúng “lồng” trong chữ ký
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.

Disallow line breaks in signature

 * This is an archived record of a previous proposal. Please do not modify it. A summary of the conclusions reached is in the  section.

The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal carriage return and line feed characters, not and.

At this time, you cannot add these characters to a custom signature in Special:Preferences. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically.



Ảnh hưởng: các ảnh hưởng của thay đổi


Các chữ ký hiện tại được ảnh hưởng như thế nào?
Any existing signatures that would become invalid under the new rules are still allowed (grandfathered in). When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid. But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.

We're looking for feedback as to whether you would like existing invalid signatures to be disallowed. If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.



Các thay đổi này xảy ra lúc nào?
Please comment before 31 March 2020. The Editing team will make decisions about this project in early April. The results will be posted on the talk page.

If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback.



Chúng ta sẽ nhận ra các thay đổi như thế nào?
We'll include another notice in Tech/News when this change is about to be deployed.



Các lỗi phê chuẩn chữ ký xuất hiện như thế nào?
The HTML/lint errors include links to existing documentation about lint errors, such as Help:Extension:Linter/missing-end-tag, and a button to highlight the problematic part of the signature.

The required link errors include example wikitext syntax to use.

Original proposal
Phần lớn đề nghị được cộng đồng chấp thuận. Do các lời nhận xét của người tình nguyện, nhóm phát triển đã thực hiện một số thay đổi nhỏ và làm rõ một số điểm.


 * 1) Không cho phép một số trường hợp HTML hư hỏng và lỗi Linter khác
 * 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 </tt> and <font ></font> will not be banned at this time.  This decision does not prejudice any future decision for or against removing these obsolete HTML tags.
 * 1) Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp
 * 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) Không cho phép nhúng “lồng” trong chữ ký
 * This will be implemented as originally planned.

Quá trình thực hiện thay đổi này là:


 * ✅ 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.

2021 proposal
The line break characters carriage return and line feed (but not the HTML codes for them, e.g., and ) are disallowed.