May 13 2021
May 12 2021
Idea: __PING__ and __NOPING__ magic words. Talk pages would be __PING__ by default. Content pages would be __NOPING__ by default. Wikis would typically add __NOPING__ to all archive templates. There could be safeguards against false positives, like "Ignore edits with multiple section headings" or "Ignore edits that start and end on different indentation levels." When an edit is ignored for one of these reasons, notify the user that no ping was sent (rather than the status quo, where you only get a "failed notification" message if the notification was sendable but not delivered.) That way false negatives aren't that big of a deal. And maybe have a way for users to intentionally disable pings for an edit, like by including "NOPING!" in their edit summary.
Sep 5 2017
Since this is affecting the display of a large number of en.wp pages, I've boldly set it as high priority. My apologies if I shouldn't have.
Sep 4 2017
@Dbrant Yep, it's working fine now. Thanks. Although I did get an error when I tried to edit a Lua module on the app. Just a generic "an error occurred," not the "page protected" message I was running into here. Is that a known bug(/feature?), or should I report it?