I don't have a better idea for a name, but having "Current issues" on the sidebar, suggests a place to report current issues/bugs about MediaWiki, not to have site discussion.
Perhaps Village Pump would be better. Its wiki specific jargon, but at least its unlikely to confuse people just wanted support for MW.
As it's a proper noun, I think it should be with the current capitalisation. (Also all the other ones should be updated back to being proper case, as they are standard MediaWiki terms; was there a discussion about changing them?)
That's MediaWiki's default; the link there is unedited. See MediaWiki:Recentchanges -- page doesn't exist so it inherits the default from i18n/en.json. All of the default sidebar links are sentence case.
I see "village pump" as a common noun: "set of pages used to discuss the technical issues, policies, and operations of a Wikimedia wiki" (Wikidata). Looking at the Wikidata entry, most village pump pages on other wikis use sentence case, as well as similar pages like "Reading room", "Water cooler", and "Beer parlour".
It's hard to translate "village pump" to other languages when it's more a slang or argot than the actual meaning of "village pump" (where's the pump here?)
Hello! I recently joined the Wikimedia Foundation as a software engineer. I am working on WikiLambda/Abstract Wikipedia. I tried to create a page to instruct others how to get this extension up and running locally but was admonished not to do so (with a very intimidating cat picture). How can I create this page?
A policy regarding the removal of advanced permissions (such as: administrator, bureaucrat, interface-administrator, etc.) was adopted by global community consensus in 2013. This community, while initially excluded from the activity review, decided in August 2020 to opt-in. Accordingly, the stewards are reviewing the activity of the accounts with advanced permissions based on the admin activity review policy.
To the best of our knowledge, we have determined that the following users meet the inactivity criteria (no edits and no logged actions for more than 2 years):
These users will receive a notification soon in their talk pages, asking them to start a community discussion if they want to retain some or all of their permissions. If the users do not respond, then their advanced permissions will be removed by the stewards without further notice.
We've excluded the following accounts as we believe that those accounts were granted permissions as part of their work and/or services as employees/contrators of the Wikimedia Foundation.
Amusso (WMF)
PEarley (WMF)
Heatherawalls
If you belive those should be included in the review as well, or we missed someone, please inform us.
Please let us know at the stewards' noticeboard on Meta-Wiki if you have any questions or concerns.
The original proposal says this is motivated by security reasons; I have 2FA enabled and do get my talk page notifications, so I think it should be fine to not remove mine?
As far as I’m aware, simply editing here was enough to let you keep everything. The AAR process doesn’t make exemptions for 2FA but now that you’ve edited you’re no longer “inactive.”
As long as the user replies to the notice and clearly states that they want to keep their advanced permissions (as VasilievVV did above), and the community is not opposed to it, that is enough for the stewards and it prevents the automatic removal of permissions. The post above gives VasilievVV also means that VasilievVV won't be notified again unless he fails to make an edit or log action in the next two years.
I think an external link, [https://wordpress.org WordPress], would be warranted on Extension:AuthWP, but I cannot add it. Similarly, I cannot set download-link in the ExtensionInstall template to [https://github.com/gonenlab/AuthWP/archive/master.tar.gz Download]. Is there anything that could be done about that?
You have now made enough edits to this wiki that you should now be able to add external links without triggering the edit filter. That said, (speaking to other users watching this page, not to you), given the frequency with which this comes up, would it make sense to exempt edits to the Extension namespace from that filter, since they are often not spam?
@Pppery: I would not encourage loosening the filter, because link spamming is a chronic problem and the filter does a very good job of filtering them out.
One (Special:AbuseLog/216211) is page corruption caused by using VisualEditor on a translatable page, which would likely have been rolled back if it went live, but is technically a false positive.
One (Special:AbuseLog/213630) is vandalism that got erroneously detected as spam because it broken a link.
That totals fifty-nine incorrectly blocked edits and forty-one correctly blocked edits. Are you sure that the filter [applied to the Extension namespace] does a very good job of filtering [link spam] out?
Yes, that still does a good job overall (considering how much link spam was there before), but seeing that most of the supposed false-positives are in the Extension namespace, I am open to, and am fine, with your loosening of the filter to exclude edits in that namespace.
Come to think of it: in the interest of reducing traffic such as this, it may be worthwhile to reword the message presented to the user upon having an external link rejected. I don't recall precisely what it said, but it made me think that is was due to a per-user or even per-instance restriction that would have to be manually lifted by a human administrator. If the message were to indicate that you can't add links until you've got sufficiently many edits under your belt, I would not have started this duplicate thread.
The message is MediaWiki:Abusefilter-warning-linkspam. I'd be willing to consider proposed rewordings, although of course any advice given there will also be read by actual spammers.