If this were not feasible because it overloads things then of course that is the end of it. At that point it should be considered if there is a way to better advertise the feature or make it more intuitive for those who would benefit from seeing it, as I think it is currently very obscure and heavily underutilized.

I like this idea. It's particularly useful for people with cross-wiki presence but who might not understand this option exists since it's poorly advertised (buried at the bottom of a preference menu). I don't think it would do any harm to people who only participate in one or a couple wikis and in fact it would help in cases where people need to be 'centrally notified' of something through Meta but aren't regular participants there (especially say, global username violations or something to do with a wiki request when they're only active on one). If it's not feasible to make this a default then perhaps there is a way to make people more aware - I think more people would use this if they knew.

This re-post is intended to correct an issue with the original request's domain without requiring a resubmission or sacrificing the requestor's place in line so far. Original submission; (T10015#202048)

Hello, I've gone through some of the requests to verify requestor so far to try and make the process faster. A fellow wiki creator should be continuing verifications tomorrow; there isn't much left so it should be finished then.

Likewise, same circumstance as FatBurn.

I also have this issue and racked up 5 unremovable alerts so far with the Qualitipedia Central Wiki. On the frontend the actual alerts (and the page) show nothing. and I believe the error is 500, saw it appear once. I suspect it's the same problem as here, an odd database glitch after the upgrade. This has just been reported on the Stewards' noticeboard as well, which I will point to this task as it sounds identical.

As possible I strongly encourage interfacing with the local wikis. I suspect a lot of traffic that would benefit from an announcement, simply does not pass through Meta or its CN.

I have encountered the identical error here on another wiki natively hosted on Miraheze. The file can be (and was) moved, but a local administrator and myself as a Steward were unable to delete it.

This on the other hand seems more likely to be connected. Blog on Crappy Games Wiki

I doubt it's directly related and I can make another task if desired, but on the topic of broken pages I am finding this RfC on meta in particular is incapable of loading, producing 502 or 503 every attempt.

Fully agree with John's take. I would say I've observed some of that confusion occur with the end user as well wondering about particular phrasing that may not have been best suited. I'm inclined to see the qualifiers become more general and let WCs use discretion in amending the description (through one post) to make notations.

The StructuredDiscussion issue has been reported at https://phabricator.miraheze.org/T8402.