Change Details

It makes sense to have namespace edit notices in the MediaWiki namespace, but I don't see why edit notices for base pages should be there. It bloats the message cache and requires elevated privileges. editinterface is effectively the highest privilege level -- it allows you to hijack the browser of anyone viewing the site. Why should setting an edit notice for a single page require such permissions? Also, T85372 proposes adding edit notices for categories, and I don't think they should be in the MediaWiki namespace either. I suggest adding a {{#editnotice}} parser function which would copy the expanded wikitext into page_props. To fetch edit notices, MW would check page_props for the page itself, the base page, and the categories the page is in. By default, {{#editnotice}} on a category would only affect edits to the pages in the category, not edits to the category page. The messages would also continue to be checked for some suitable deprecation period. To mitigate the risk of a DoS via edit notice preventing the editing of a page, there would be a request parameter notice=false which disables the display of edit notices. API editing would also be possible. For expedient review, category and base page notices would be labelled with a link to the page which generated them. I would like product manager review of this idea. In particular I would like to know if anyone can think of any likely negative community consequences for a reduction in permissions required for setting edit notices.

It makes sense to have namespace edit notices in the MediaWiki namespace, but I don't see why edit notices for base pages should be there. It bloats the message cache and requires elevated privileges. Why should setting an edit notice for a single page require such permissions? Also, T85372 proposes adding edit notices for categories, and I don't think they should be in the MediaWiki namespace either. I suggest adding a {{#editnotice}} parser function which would copy the expanded wikitext into page_props. To fetch edit notices, MW would check page_props for the page itself, the base page, and the categories the page is in. By default, {{#editnotice}} on a category would only affect edits to the pages in the category, not edits to the category page. The messages would also continue to be checked for some suitable deprecation period. To mitigate the risk of a DoS via edit notice preventing the editing of a page, there would be a request parameter notice=false which disables the display of edit notices. API editing would also be possible. For expedient review, category and base page notices would be labelled with a link to the page which generated them. I would like product manager review of this idea. In particular I would like to know if anyone can think of any likely negative community consequences for a reduction in permissions required for setting edit notices.

It makes sense to have namespace edit notices in the MediaWiki namespace, but I don't see why edit notices for base pages should be there. It bloats the message cache and requires elevated privileges. editinterface is effectively the highest privilege level -- it allows you to hijack the browser of anyone viewing the site. Why should setting an edit notice for a single page require such permissions? Also, T85372 proposes adding edit notices for categories, and I don't think they should be in the MediaWiki namespace either. I suggest adding a {{#editnotice}} parser function which would copy the expanded wikitext into page_props. To fetch edit notices, MW would check page_props for the page itself, the base page, and the categories the page is in. By default, {{#editnotice}} on a category would only affect edits to the pages in the category, not edits to the category page. The messages would also continue to be checked for some suitable deprecation period. To mitigate the risk of a DoS via edit notice preventing the editing of a page, there would be a request parameter notice=false which disables the display of edit notices. API editing would also be possible. For expedient review, category and base page notices would be labelled with a link to the page which generated them. I would like product manager review of this idea. In particular I would like to know if anyone can think of any likely negative community consequences for a reduction in permissions required for setting edit notices.