Template talk:Flag
Add topicLatest comment: 6 years ago by SVTCobra in topic Protection
Protection
[edit]{{makeprotected}}
•–• 16:44, 11 November 2017 (UTC)
- @Acagastya: So, what's your reasoning here? The page is semi-protected against casual vandalism. Why does it warrant full protection? --Pi zero (talk) 20:46, 11 November 2017 (UTC)
- @Pi zero: protect against renaming. I should change the wording. It is to add rename protection, like when an article is published.
•–• 03:50, 12 November 2017 (UTC)- @Acagastya: The precaution on published articles has a technical motive: renaming in the first days/weeks after publication can cause duplicate entries in feeds. Renaming this would probably be a bad idea, but it wouldn't have those sorts of off-site technical repercussions. --Pi zero (talk) 04:54, 12 November 2017 (UTC)
- @Pi zero: what I am trying to say is this template {{makeprotected}} should be used when we want to request a page to be protected. For example, if I publish an article, that has to be protected. So I would use this template on talk page. Why flag should be protected? As a precaution, otherwise if someone moves this template and breaks the redirect, it would be disastrous. At least until someone fixes it and then protects it against vandalism.
•–• 05:09, 12 November 2017 (UTC)- Anything could get messed up if vandalized. I try to resist letting that, in itself, become a reason for full protection. Some used in thousands (or even hundreds) of places might justify some additional precautions. Off-site technical repercussions could justify additional precautions. But this template is expected not to be use used in very many places at a time. --Pi zero (talk) 05:20, 12 November 2017 (UTC)
- @Pi zero: what I am trying to say is this template {{makeprotected}} should be used when we want to request a page to be protected. For example, if I publish an article, that has to be protected. So I would use this template on talk page. Why flag should be protected? As a precaution, otherwise if someone moves this template and breaks the redirect, it would be disastrous. At least until someone fixes it and then protects it against vandalism.
- @Acagastya: The precaution on published articles has a technical motive: renaming in the first days/weeks after publication can cause duplicate entries in feeds. Renaming this would probably be a bad idea, but it wouldn't have those sorts of off-site technical repercussions. --Pi zero (talk) 04:54, 12 November 2017 (UTC)
- @Pi zero: protect against renaming. I should change the wording. It is to add rename protection, like when an article is published.
Not done This request seems to have been declined. --SVTCobra 17:13, 7 January 2018 (UTC)