Jump to content

Wikipedia:Village pump (idea lab)/Archive 24

Add links
From Wikipedia, the free encyclopedia
Village pump (idea lab) archive  

This page contains discussions that have been archived from Village pump (idea lab). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

< Older discussions · Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62

Guide for evading detection of new accounts for use with WP: Cleanstart?

I haven't been able to find any successful examples to someone being given a WP: cleanstart. Maybe someone could link to some for my edification. I'm concerned that the spirit of this policy is not being respected, because editors' accounts are being blocked once it is discovered that they had a pre-WP:Cleanstart account, even though they are attempting to WP:Cleanstart from those old accounts! Seems like a classic Catch-22 situation.

Personally, I have been diligently trying to implement WP: Cleanstart with no luck, as my new accounts keep getting found! Could an experienced editor who has successfully used WP: Cleanstart post some tips and tricks to having one's new accounts go unnoticed long enough to make a cleanstart? This project really needs a "Newcomer's guide to evading detection of new accounts". Please help!Definitely New Editor (talk) 23:59, 24 November 2017 (UTC)

My troll alarm is beeping here. Home Lander (talk) 00:05, 25 November 2017 (UTC)
Please WP:AGF. How can we have a WP:Cleanstart if we can't even figure out how to prevent others from connecting our new WP: Cleanstart account to our old ones? Please, successful WP:cleanstart users, tell us what did and did not work for you. Definitely New Editor (talk) 00:31, 25 November 2017 (UTC)
The reason why you don't see any successful examples is because editors who have successfully clean started don't leave a bread crumb trail connecting their new account with their old one. There's not a userpage banner for "this account is a clean start account", that would defeat the purpose. Some disclose their connection privately to the Arbitration Committee, but you won't find evidence of that. If you really want to clean start, and your old account isn't blocked (because then you aren't allowed) then you need to leave your old pattern of editing behind and find something completely different to do here. If you decide to abandon one account and then make a new one to go right back to doing exactly the same thing as before, someone's going to notice. All of this is stated in the WP:CLEANSTART essay. Ivanvector (Talk/Edits) 01:05, 25 November 2017 (UTC)
Also, don't call your account "Definitely New Editor" and then immediately inquire about how to evade detection. WP:AGF has limits. Ivanvector (Talk/Edits) 01:07, 25 November 2017 (UTC)
In fact, since I'm on a roll now, I'll say you should disclose your clean start relationship to Arbcom if you have a good-faith reason to do so. If you're identified to the Committee, you should escape being blocked if a Checkuser connects your new account to your actually abandoned and not blocked account. Ivanvector (Talk/Edits) 01:10, 25 November 2017 (UTC)

BLP unreliable source filtering

I've been following a long-running but slow-moving dispute on a BLP for a while, and it occurred to me today it would be useful to be able to tag a BLP as (for example) having a disputed date of birth, and being able to partially blacklist certain websites (such as IMDb or famousbirthdays or wikia or other known unreliable sources) from being reinserted as sources on those articles. I really have no idea how such a thing would be implemented, but it would save some biting of new users who try to add these disputed sources in good faith, not knowing of the controversy. Just putting it out there. Ivanvector (Talk/Edits) 18:18, 27 November 2017 (UTC)

Could possibly make an invisible template and then trigger the abuse filter on edit using the template or a hidden category it adds. --Izno (talk) 18:25, 27 November 2017 (UTC)

Translations

I do not understand why translations are only for only extended confirmed users. I think it should be for any new user. The reason I state this is because some people's only desire to create a Wikipedia account is to provide translations for languages they know and understand, imagine all the possible Wikipedians were turning away because they found you must have made 500 edits and have been on Wikipedia for 30 days. YuriGagrin12 (talk) 23:45, 28 November 2017 (UTC)

@YuriGagrin12: You can read the discussion which put that requirement in place. --Izno (talk) 02:30, 29 November 2017 (UTC)

Perhaps we should stop issuing warnings to IP addresses for obvious vandalism

Since the early days of Wikipedia, it has been common practice to post warning templates to users and anonymous editors engaging in problematic activity, and to avoid blocking without proper warning. For many policy issues, like original research and copyright issues, it is important to point out what someone is doing wrong and give them the opportunity to correct their mistakes. However, are we really so naive to think that someone who writes "<3" or "Fuck you!" in the middle of an article is doing so to improve the project? Even if they're just experimenting rather than trying to inflict damage (which is realistically what most of the vandalism is anyway), anyone with the required common sense to be a functional contributor at Wikipedia should know such actions do not contribute to the encyclopedia. However, placing the warning templates on IP talk pages can cause more problems per WP:BEANS if, for example, Malice Boy decides to brag about the size of his penis on the article about quantum physics using a school computer or dynamic IP at home, ignores the "you have new messages" banner when he is warned, and the warning is instead read by Curious Middle School Girl, who would have never even thought to vandalize an article until reading the warning and suddenly wonders what happens if she decorates a bunch of pages with smile emojis and the word "poop."

I would propose that, instead of feeding trolls and potentially giving people new bad ideas, we just put the standard welcome template on IPs' talkpages when they engage in obvious test edits or vandalism, not referencing any particular edit or accusing them of vandalism. Perhaps we should edit {{Welcome}} to include information about the sandbox and the blocking policy, although all of this is already accomplished by {{Shared IP}} and the related templates. Instead of warning them four times before reporting to WP:AIV, I would propose reporting after four reversions.

The problem would be getting everyone on the same page with this when many people are used to the old way. We would definitely need to change the project pages pertaining to vandalism and recent changes patrolling, and update tools like Twinkle to reflect the new way of doing things, but what about people who have been RC patrolling for years and have the current way ingrained in their minds? Perhaps we could have a bot notify all rollbackers, Twinkle users, Huggle users, etc? Perhaps we should go more extreme and full-protect IP talk pages, or set up an edit filter with a friendly reminder?

What is the rest of the community's thoughts on this? PCHS-NJROTC (Messages)Have a blessed day. 22:06, 2 October 2017 (UTC)

I don't like this idea very much. How do you distinguish between someone who is blatantly vandalising and a genuinely misguided editor? Obviously the extreme cases are easy to tell apart, but what about in betweeen? Of course we're not so naive to think that blatant vandals don't know what they are doing, but there's no harm in putting a warning (I remember reading somewhere that friendly warnings may actually discourage warnings, but I don't have a source and may be wrong. From a practicality standpoint, warnings also serve as a tool for vandal fighters to quickly tell how much vandalism a user has done, where it would be much more time consuming to check their contributions (not all contributions that aren't current are reverted, and not all reverted edits are vandalism. Semi-automated tools like Huggle and STiKi and ClueBot NG use warning templates to decide when to report a user, and this would not be possible with your proposal, especially as humans would have a much harder time doing so. It's true that warning templates may cause a WP:BEANS effect, but simply not using them would be unviable. Thanks, Darylgolden(talk) Ping when replying 11:21, 3 October 2017 (UTC)
I agree that after an IP address has been reallocated the warning ceases to be useful and may become counterproductive. The problem is that we don't know which IP addresses have been reallocated. We also have the problem that an IP address may have multiple users, sometimes a whole country, and that the proportion of vandalism edits may reflect that. We also have the issue that admins and vandalfighters need to know a bunch of information about an IP address that we currently make public but would probably do better by restricting to confirmed registered editors. ϢereSpielChequers 11:53, 3 October 2017 (UTC)
From a practicality standpoint, warnings also serve as a tool for vandal fighters to quickly tell how much vandalism a user has done That's another issue in itself. Even static IP addresses get reassigned when big institutions change internet providers, go out of business, etc., and as WereSpielChquers points out, a lot of warnings on an IP representing an entire country, fortune 500 corporation, university campus, school district, etc. can make several instances of people just messing around one time look like one person who needs a listing at the long-term abuse page. I agree that people who do things like add original research need to be warned, but telling people that writing "poop" or "this movie sucks" on articles is unacceptable and that they need to stop their malicious activities at once is kind of silly. If it's a registered user, it may be possible to convince him or her to be more constructive, but if an IP represents 100,000 people and someone else just reading Wikipedia sees the orange banner before the vandal, what is the point? Surely the bots could be reprogrammed to analyze how many of an IP's edits have been reverted in the last hour rather than how many vandal warnings have been placed. PCHS-NJROTC (Messages)Have a blessed day. 16:34, 3 October 2017 (UTC)
To be clear, I'm not saying we should just block people for one instance of "poop" or "hi!!!," but if a little girl or old lady just messing around doesn't get the message after the first two instances of her edits being reverted within seconds, she's not very useful to us as a contributor even if she tried to be constructive. PCHS-NJROTC (Messages)Have a blessed day. 16:50, 3 October 2017 (UTC)
We normally go through four levels of warnings before we block vandals. Though particularly blatant and egregious stuff can earn you an instant block. That system works pretty well, yes you get the occasional false positive at least on the warning messages, but it is pretty much unheard of for a non vandal to get a block for vandalism. More importantly, when a newbie warns someone for vandalism when they are just in an editing dispute there is a good chance that they will use the fairly anodyne level 1 warning. We could go through a scientific review of the existing system and see if it is still the most effective way to deal with vandals, but the potential gain of moving to three or five warnings is probably minimal. Remember when a vandal is on a spree we need to stop them, and we need to do it in a way that doesn't piss them off so much that they become one of those perennial problem users. I see bigger potential gains in moving to some sort of selective block where blocking an IP address only blocks people using the same sort of device as was used for a particular vandalism edit. That could dramatically reduce our false positive blocks. ϢereSpielChequers 13:14, 4 October 2017 (UTC)
As stated above, the warnings, even if ignored by IP vandals, serve a valuable purpose in fighting vandalism because they're a record of the number of times the IP has been warned. It would be too much work to go through each IP vandal's contribution history to decide whether the IP should be reported at WP:AIV. In the scenario of one student at a school getting a warning which inspires other students at the school to commit additional acts of vandalism, eventually there will be a school block and the students will have to create individual accounts if they want to edit on Wikipedia. Strawberry4Ever (talk) 20:59, 3 October 2017 (UTC)
...or there will be a "schoolblock" placed on the entire nation of Qatar because an admin based his block off of the number of warnings on Qatar's IP address. PCHS-NJROTC (Messages)Have a blessed day. 16:03, 4 October 2017 (UTC)
The more infamous Qatar IP address. No "schoolblocks," but occasionally people would try a long term "anonblock." Warning that IP address for "poop" vandalism must have been very productive when it was active. Speaking of static IPs getting reassigned and administrators basing their actions off of the number of warnings an IP has, what is our plan of action when a former school IP that has been blocked for six years gets reassigned by Verizon Business to the White House, Donald Trump makes improper but good-faith edits that half way resemble his Tweets, an admin doesn't bother to check the current WHOIS information, and schoolblocks the White House for exactly eight years? A lot of Wikipedians would probably think that was hilarious, but I doubt WP:COMCOM and the WP:RC Patrol would enjoy dealing with the wrath of President Trump, his supporters, and endless alt-right media outlets declaring war on Wikipedia over it, especially if ARIN clearly says it belongs to the White House rather than the middle school it's tagged as belonging to. PCHS-NJROTC (Messages)Have a blessed day. 16:10, 4 October 2017 (UTC)
I don't think we should base Wikipedia policy on these extreme examples. It's ridiculous for the entire nation of Qatar to have a single IP address. If vandalism from Qatar gets too bad then in my opinion the IP address should be blocked, but that's something for the admins to worry about. As for the problem of Donald Trump not being able to edit from an IP which has been blocked, I'm sure a call from the White House to the Wikipedia Foundation would lead to a quick solution. Strawberry4Ever (talk) 17:05, 4 October 2017 (UTC)
(EC) If an admin does a block that is out of policy then we can deal with that as and when it happens. Unless we think policy is not being followed I suggest we focus on ideas that would work within or change policy such as Wikipedia:Blocking_IP_addresses#Block_lengths ϢereSpielChequers 17:15, 4 October 2017 (UTC)
Those are valid problems, but how exactly does not warning IPs do anything to solve that? Darylgolden(talk) Ping when replying 09:51, 5 October 2017 (UTC)
I think there is merit in discussing this further. Now first, I'll note we are in the idea lab not proposals. If this was formulated as a formal proposal, there would be nothing wrong with simply saying no, but the point of the idea lab is to brainstorm how to address an issue not simply dismiss it.
I start by challenging the notion that the "existing system works fine as it is". I'm saying this from the point of view of an OTRS agent; we are struggling to keep up with the flood of questions sent to this venue, and there is one class of queries that seems to be growing. Someone writes in to complain that they have never done anything wrong, yet they received a message on a talk page that they have been vandalizing. While we know that this is because they have a dynamic IP and happen to be logged in that time with the same IP as someone else who has vandalized Wikipedia, they don't know that. Some of the people are merely questioning, while others are a bit more irate. We do explain to them the situation, but given the prevalence of dynamic IP's, I don't think it's acceptable that we are issuing messages that are troubling to some of our readers. I think our canned message mentioned something about dynamic IP's but I can tell you from experience, we still get a lot of emails on this issue.--S Philbrick(Talk) 14:35, 5 October 2017 (UTC)
That may be a problem, but the proposed cure is worse than the disease, in my opinion. Better is to encourage editors to include {{subst:sharedIPAdvice}} when posting warnings on IP talk pages. Strawberry4Ever (talk) 14:56, 5 October 2017 (UTC)
Another solution would be to disallow IP edits and make everyone create an account if they want to edit on Wikipedia. However, that would be a major change in philosophy and I don't expect it to happen. Strawberry4Ever (talk) 15:03, 5 October 2017 (UTC)
That's a perennial proposal that would come with its own bag of problems. IP vandalism would come to an immediate end, but vandalism (and editing in general) would spike because the massive amount of {{Schoolblock}}s, {{Anonblock}}s, and {{Rangeblock}}s would begin to expire, and those IPs would stay unblocked short of checkuser intervention. In my opinion, that would be a good thing because it is said that most edits by anons and newbies are in good faith, and now people who used to have to jump through hoops if they wanted to edit can simply make an account and edit, while the truly repetitive producers of filth would be identified and appropriate IP blocks could be placed by checkusers (although the change would be a real pain in the ass for the checkusers). The down side is that I believe autoblock is, or at least was, a hard block, and I know that because there have been times I have tried to edit from shared IPs caught up in an autoblock and wasn't able to edit even with an account. However, that is a problem that can easily be solved by programming autoblock to only block anonymous users and disable account creation. I kind of think disabling anonymous editing is a good idea, but I doubt the community will go for it now anymore than they have in the past. PCHS-NJROTC (Messages)Have a blessed day. 18:45, 7 October 2017 (UTC)

Just add to the point I made above (and I apologize these links are ones you cannot read unless you are an agent), the following are three OTRS tickets I've handled in the last hour, all complaining that they been accused of vandalism and they have not vandalized anything. I don't think it's a good situation that we are leaving messages that are misinterpreted. Perhaps the message needs to be rewritten to make it clearer but it almost certainly doesn't apply to the person reading it.

Did the warnings on the talk pages include {{subst:sharedIPAdvice}}? Strawberry4Ever (talk) 16:47, 8 October 2017 (UTC)
I didn't check, the complaints rarely identify the IP address. I usually offer to help them create an account, and that occasionally happens, but I typically don't look at the warning.--S Philbrick(Talk) 18:02, 8 October 2017 (UTC)
Another one today. Someone writing in, spitting nails, because they've been falsely accused of vandalism. I'm calming them down, but it's not a great way to start. And I'm mentioning it here because most editors will be unaware of this problem.--S Philbrick(Talk) 20:28, 11 October 2017 (UTC)
Yet another one a few minutes ago. An editor, quite incensed about a message placed in 2009. We need to rethink our policy.--S Philbrick(Talk) 01:59, 12 October 2017 (UTC)
  • Ban IP editing - Said it before and I'll say it again - It's about time we done away with IP editing - If you wanna be a valued contributor then create an account, Sure not all IPs are vandals however most are so IMHO it's about time we done away with this whole "Anyone can edit" crap, Sign up or go elsewhere. –Davey2010Talk 21:12, 8 October 2017 (UTC)
Do you have any statistics to show that most IP editors are vandals? (I'm not necessarily disputing it, but claims like that need evidence.) Boing! said Zebedee (talk) 21:20, 8 October 2017 (UTC)
I'm afraid not - I'm only going by my years of editing here but as I can't physically prove it I've struck that part, Thanks, –Davey2010Talk 21:25, 8 October 2017 (UTC)
Ah, OK - it would be nice if we did have some stats on the proportion of IP edits that are vandalism, though. Boing! said Zebedee (talk) 21:34, 8 October 2017 (UTC)
Even if it were 50% vandalism we shouldn't ban IPs, and with the edit filters preventing most vandalism the proportion of IP vandalism is likely to have fallen a lot since 2009. More to the point; If the theory is true that vandals do the minimum necessary to do their vandalism while goodfaith editors are lured in by making things easy and inviting for them, then banning IP editing would lose us some good edits and make some vandalism less easy to find. I suspect that's an over simplification, and banning IPs would lose us some vandalism, as well as making some vandalism harder to find. but it would lose us a proportion of our goodfaith newbies and that is a price we should be loathe to pay. ϢereSpielChequers 08:16, 12 October 2017 (UTC)
The makes vandalism harder to find argument also means makes biting newbies more likely. For example, the IP address I am editing from right now is a corporate proxy that seems to have produced more vandalism than good faith edits. If I didn't have an account and made a simple edit from this IP, an RC patrol may look at the edits from this IP and assume bad faith because other people from this corporate proxy have vandalized. Disabling IP editing would ensure that editors are evaluated by their own edits, not edits from other people using the same IP address. I can't tell you how many times I've seen someone leave a nastygram for a school or corporate editor who made a good-faith edit because the RC patrol shot first and thought later didn't think about it. PCHS-NJROTC (Messages)Have a blessed day. 11:51, 12 October 2017 (UTC)
Can I just remind folks that this discussion is not about banning IP editing, but about whether "we should stop issuing warnings to IP addresses for obvious vandalism" (to quote the heading)? Boing! said Zebedee (talk) 12:04, 12 October 2017 (UTC)

I've seen more IP edits that are good faith recently; I can't easily prove that, but it's more a gut feeling, and I did bring it up at a recent meetup. IP editing in mainspace is important because it keeps a low barrier to simple fixes such as typos, that we'd lose if people had to go through the rigmarole of registering; conversely vandals would have no issue in registering for a throwaway account. I'm not sure of the value of editing other namespaces, except in limited circumstances such as edit requests; I think if you want to discuss things, you should have an account. (The clue's in the name - you should make yourself accountable for what you say). Going back to the original point, I assume good faith wherever possible, even if an edit is disruptive and a block may still be deserved. If that's the case, often I'll give them the boilerplate block template that tells them how to appeal, plus some hand-written advice. Usually, I'll be late on the scene and the user will have had warnings from other editors anyway. If I am absolutely certain that I am dealing with an obvious vandal, they get an instant block with "vandalism" as the reason, and nothing else. Ritchie333 (talk) (cont) 21:35, 8 October 2017 (UTC)

I've been arguing that blocking shared IPs (or blocking entire /16 and /24 ranges) over petty nonsense hinders the mainspace for a long time now, and while proposing any restrictions on admins blocking these IPs or ranges would be WP:HORSEMEAT, the response I have received is that people using the said IPs and ranges can just register an account, people say minor fixes in articles aren't worth allowing an occasional instance of vandalism, whenever I've questioned a specific block on an admin's talk page I've been ignored or given some excuse (or, in one case, a rather heated and borderline WP:UNCIVIL reply), and any time I've questioned a specific block somewhere like WP:AN/I (including one rather ridiculous /16 range block labeled several companies and the Federal Aviation Administration as a "school"), I generally get scolded for daring to question it. Bear in mind, I'm not talking about IPs used by people like Willy on Wheels or Grawp, I'm talking about IPs that may have made silly edits weeks, months, or years ago, makes one dumb edit that involves emojis or random characters, and gets blocked for a period in excess of one year with {{schoolblock}} or {{anonblock}}-Likely a school based on behavioral evidence (I've seen major banks, insurance companies, and the U.S. military blocked with the latter). I agree with you that minor IP edits are beneficial to the project and that vandals are more likely to go to the hassle of creating an account than someone who sees a spelling mistake and wants to do the right thing, and since the softblocks prevent account creation, it's even less likely that such people are going to create an account since they'd have to do so elsewhere or request one via email, but considering the mentality of this community, I don't see anything changing in this regard anytime soon. On the other hand, reducing the chances of a WP:BEANS instance of a dumb emoji addition to an article about square roots causing to get General Electric or Harvard University blocked by addressing the way we warn IP editors MIGHT be plausible. Actually, what made me think of this is wondering if removing a false-flag ClueBot warning from an IP talk page could end up being a bad idea since it would generate the "new messages" banner. PCHS-NJROTC (Messages)Have a blessed day. 01:55, 9 October 2017 (UTC)

Another idea to Address my WP:BEANS theory would be to update Media Wiki so that the "new messages" banner goes away for IPs after one hour, if it isn't clicked before then. This would probably actually be a more practical solution, because it wouldn't require any major changes to the way we do things but would address the issue of a cellular-based editor seeing the banner because someone else in the same dynamic IP range engaged in vandalism four hours prior and never read the warning left for him/her. PCHS-NJROTC (Messages)Have a blessed day. 02:00, 9 October 2017 (UTC)

  • The issue of IP editors being warned for things that were done by other people on the same IP address seems legit to me, especially if they complain to OTRS about it. One solution would be to delete IP talk pages after a while. The other might be to hide the notification banners after a set time. The former might create issues with long term disruptive editors on stable IPs and the latter with IPs that are used for more than that set time. Jo-Jo Eumerus (talk, contributions) 14:57, 12 October 2017 (UTC)

Some of the ideas raised in the above discussion are already tackled at Wikipedia: Perennial proposals. There is the classic claim that we should ban edits from IPs, but as noted at Wikipedia: Perennial proposals, a good many edits by IPs are good faith edits which go to improve the encyclopedia. Vorbee (talk) 19:35, 12 October 2017 (UTC)

Is there any way to distinguish static IPs from dynamic ones? It would be nice if Wikipedia could treat them differently. Strawberry4Ever (talk) 20:37, 12 October 2017 (UTC)

How this would help us to distinguish between IPs who have made useful contributions to the encyclopeadia versus IPs who have committed acts of vandalism? An act of vandalism would make one an active IP, but so too would a sensible, informative edit. Vorbee (talk) 10:56, 13 October 2017 (UTC)

I think the point is to distinguish between a Static IP (whose address remains constant over potentially long periods and is therefore more likely to be used by only one person) and a Dynamic IP (same link) (where the address potentially changes every time you restart your router and is more likely to be used by unrelated editors) and thus perhaps soften the approach to dynamic IP users to reduce the possibility of appearing to accuse the wrong person. Boing! said Zebedee (talk) 11:13, 13 October 2017 (UTC)
It gets a bit more complex than that though. Due to NATting the IP recorded here is the IP of the router (whether static or dynamic), not even the machine on which the edit was done. Martin of Sheffield (talk) 11:32, 13 October 2017 (UTC)
That's true, so a single static IP (as we see it) can still be used by multiple editors at the same time - like school IP's, which can be big sources of vandalism. Boing! said Zebedee (talk) 13:23, 13 October 2017 (UTC)
...big sources of the same people who go home and vandalize or use their cell phones to vandalize. There are no truly static IPs; even "static" school IPs and corporate IPs get reassigned when institutions go out of business or switch internet providers. I distinctly recall a particular hospital's guest wi-fi network getting an IP address that clearly used to belong to a small school when the hospital switched from Comcast to Level 3 Communications (the edits, which predated the hospital's change in IP address, were to a school article and were rather immature).
One the other hand, while this thread was not started as a proposal to disable IP editing, and I was the one who first said that disabling IP editing is a perennial proposal, it may be worth revisiting because the mindset of administrators today is not the mindset of administrators ten years ago. Ten years ago, a non-university /16 range would have to be spewing out serious vandalism like an erupting volcano spewing lava for administrators to block it for a short period of time, and only seven years ago there was nothing that could be done to stop a particular person from vandalizing from Cricket Communications' range due to collateral damage, and the mere suggestion that we block AOL dial-up's IPv4 range due to IP-hopping vandalism was controversial, but now we /16 ranges that aren't even specific to a particular ISP and America's fourth largest wireless carrier's IPv6 range is softblocked due to a "dog and rapper vandal." Schools and enterprise networks used to never be blocked for more than one year, and now I have seen ten year blocks on them. The excuse is that people can create accounts if they want to edit, well, vandals may indeed do that, but the person fixing a spelling error or updating an institution's top administrator's name probably won't. Then there's the issue of IPs that are NOT blocked but have had vandals use them; when an RC patrol sees nothing but vandalism, he or she may bite a newbie thinking it's the same person that vandalized. Disabling IP editing will ensure that vandals are warned and blocked based on their behavior, not good-faith newbies using the same IP as vandals. PCHS-NJROTC (Messages)Have a blessed day. 16:51, 13 October 2017 (UTC)
Yes, and a dynamic IP can be unchanging over the long term, like mine is - Virgin Media in the UK always re-assigns the same dynamic IP to the same router. Boing! said Zebedee (talk) 17:05, 13 October 2017 (UTC)
No Part of issuing the warnings to the IP Address talk page is to allow others who share the IP address to exert some peer pressure to encourage the vandal to behave. Also per the above, it shows a quickly visible history to decide if you need to issue a warning, go to AIV/AN/etc, or if you just need to silently revert and pretend like the vandalism never happened. Hasteur (talk) 19:24, 13 October 2017 (UTC)
And we know that these benefits outweigh the problem discussed herebecause ...? These benefits sound somewhat marginal and time dependent, respectively, to me. Jo-Jo Eumerus (talk, contributions) 19:42, 13 October 2017 (UTC)
You want me to prove Peer-Pressure? You want an editor or administrator to always have to spend extra time to see the previous history of an IP address over time? Do you like being a detached piece of wood placed within a body of semi saturated dirt? Hasteur (talk) 19:59, 13 October 2017 (UTC)
Redacted my post as it was way more tetchy than I like. I find it unlikely that this specific scenario of peer pressure happens frequently. I don't know how useful a non deleted list of previous warnings is, especially when they are fairly old. JoJo Eumerus mobile (talk) 20:30, 13 October 2017 (UTC)
{{Shared IP}} is good at helping organizations self police themselves. Warnings for things that are 4+ years old could (IMO) be deleted safely for IP editors, but I seem to recall a recent discussion establishing consensus to leave stale warnings in place. More recent ones I'm less wild about. Hasteur (talk) 00:39, 14 October 2017 (UTC)
Peer pressure? Sure, I'm going to peer pressure people working for the same company as I do in other states to stop vandalizing Wikipedia, sure I am. Even in an elementary school with only 500 students, what are the chances of someone other than the IT department or possibly a school administrator even knowing who is responsible for writing "poop" on the article about Sony Playstation? This problem is compounded when that elementary school isn't the only facility using the same IP; the 17 year old cheerleader who reads the warning might have some clout if it was someone at her school responsible for it, but she has no influence over the eight year old doing it in another town within the same county. Don't take the school house logo on {{Shared IP edu}} literally. PCHS-NJROTC (Messages)Have a blessed day. 01:15, 18 October 2017 (UTC)
Perhaps you could stow your humor for a moment and read Network administrators or other parties wishing to monitor this IP address for vandalism can subscribe to a web feed of this page in either RSS or Atom format. on the the template. I know there's been cases where based on what I saw warnings for IP content from my company, I could make an educated guess as to who did the editing and have a private word with them to see if there might be a way for them to edit productively. I know crazy thought, registered users trying to impart the Wiki ethos in users who aren't yet registered. Hasteur (talk) 02:02, 18 October 2017 (UTC)
Hmm, I always thought off-wiki harassment was something we frowned on, but maybe that's just me. I'm not going to lie, I've talked to people off-wiki about things happening on-wiki, and it's not always easy to narrow down who it is unless you're an IT person with access to network logs; in the case of User:LBHS Cheerleader, she found me to tell me she was sorry. Sometimes they'll write a name, but often it's one of their friends' names (it could be a boyfriend, a boy a girl thinks is annoying, a team mate... most of the vandals seem to be cheerleader-type girls or former cheerleaders; I know based off of the names there was a cheerleader who very likely knew me who was vandalizing from my school in 2006, but I have no idea which of the about twenty suspects was responsible for it, and the girls I asked about it claimed to know nothing about it). If this is the direction we want to go, we should talk about reviving WP:ABUSE, because that's going to be more effective at getting something done off-wiki than just hoping some other person sees our warnings. I've had thoughts about starting a new WikiProject to support and encourage abuse reporting, but operating a little differently than WP:ABUSE. My idea is to create a project that creates templates and phone scripts to send to/call ISPs, schools, employers, etc., creates lists of verified contact information for ISPs, schools, employers, etc, and creates tools to make it easier for Wikipedians to contact them, rather than having a project with investigators and contactors like before. PCHS-NJROTC (Messages)Have a blessed day. 12:54, 18 October 2017 (UTC)
Regarding those edits from my school, before you say "see, I told you," finding those edits had nothing to do with warnings and everything to do with me becoming a Wikipedian and finding them through curiously looking through the edits from Charlotte County Public Schools, a year after those edits were made. The softblocks that are kind of common place now kind of reduce the chances of people becoming Wikipedians. PCHS-NJROTC (Messages)Have a blessed day. 13:05, 18 October 2017 (UTC)
  • {{HughesNet}} is worth looking at; it's a template dedicated to a particular satellite internet provider where there is a very low likelihood of vandals or other problem users seeing the warning templates left for them, though as one can see on just about any IP that the template is posted on, people leave warnings for the IPs anyway. There were similar problems with {{AOL}} when dial-up internet access was still popular. PCHS-NJROTC (Messages)Have a blessed day. 18:25, 23 October 2017 (UTC)

For those talking about how wonderfully these warnings help vandal fighters

Out of six edits, three were good faith. @Widr: (why wasn't I around to oppose his RfA) decides to put a six year block on it. For the next six years, anyone wanting to make minor edits like this one will have to go out of their way to make an account. Lets examine this more closely: the IP represents more than 16,000 people, some of whom are mature adults at Charlotte Technical College, some of whom are staff, and some of whom are mature K-12 students who may not even have internet access at home, or have oppressive parents at home. There are incorporated cities with less than 16,000 people! Not to mention, imagine the person who made the minor test edit that resulted in this six year block is a fifth grade girl, and by the time she is a more mature sophomore in high school, she is smart enough to realize the entire district is still blocked because of her. Do you think that person will ever be comfortable being a Wikipedian? Do you think there's a chance this person may be turned off to even reading Wikipedia after that? Now imagine some of these school IPs represent over 40,000 users. There are entire counties areas with less people than that! Corporate IPs can represent even more people; some of them could easily have over 100,000 users. There are plenty of cases of IP addresses representing more people than the population of American Samoa that are blocked from editing Wikipedia because of how important these warnings are to vandal fighters. And as for reaching the actual vandals (or people who will peer pressure them) with these warnings, imagine throwing a note saying "hey, stop doing stupid stuff on the internet" out of an airplane over American Somoa or the U.S. Virgin Islands and hoping the right person picks it up... PCHS-NJROTC (Messages)Have a blessed day. 01:49, 22 October 2017 (UTC)

While it is sometimes possible for many people to be behind an IPv4 address, this is usually an exageration: areas are usually served with ranges, meaning that the person who caused an address to be blocked may later use an unblocked address, someone not responsible for the block may sometimes fall on a blocked address, etc... And of course most IP blocks are "spoon fed", very short (maybe too short, in the case of schools, especially that they're usually soft, allowing account creation). —PaleoNeonate – 01:58, 22 October 2017 (UTC)
Six years (which is not uncommon, in my observations) is a short block? By the way, speaking of ranges, the IPv6 rangeblock on T-Mobile US affects more people than the population of California and Texas combined. Last time I forgot to log in from T-Mobile, it was still rangeblocked. I think the people suggesting a revisit of disabling IP editing are onto the right idea; disable IP editing, change the autoblock feature so that it is "anonymous users only, account creation disabled," and then the places that need to be blocked will be blocked for an appropriate period of time, and checkuser can assist with long-term IP blocks on obviously recurring vandals. PCHS-NJROTC (Messages)Have a blessed day. 02:21, 22 October 2017 (UTC)
By the way, I rarely see schoolblocks or anonblocks that allow account creation. PCHS-NJROTC (Messages)Have a blessed day. 02:22, 22 October 2017 (UTC)
Yes range blocks are indeed more serious than single address blocks of course. I commonly see individual school IP addresses get a 1 year soft block (with a "please create an account" template added on their talk page), I'm not sure for school ranges. —PaleoNeonate – 16:27, 22 October 2017 (UTC)
The schoolblock template says please create an account at home and log in with it here. The reason it is worded that way is because the blocks generally prevent account creation. How many actually do that? A checkuser could theoretically answer that question with a check of a random sample of 10 shared IPs blocked with schoolblock or anonblock, and I'll bet we would find that these blocks indeed stop good faith editing. PCHS-NJROTC (Messages)Have a blessed day. 18:19, 22 October 2017 (UTC)
There is a problem here, but it isn't the warnings - that process still works fine. The problem is with an IP block length policy of "Most IP addresses should not be blocked more than a few hours, since the malicious user will probably move on by the time the block expires." being interpreted as a few years. Unless Widr had a reason to block that IP for such a long period? I haven't checked for sourced info on the those six edits, but I'd describe three as vandalism and three as unsourced. Only if you try and source those edits yourself can you know if they were actually goodfaith or badfaith. Perhaps we need an RFC to review our policy in this area, it may be that quality requirements have now risen to the point where school blocks of years make sense. Or perhaps PCHS-NJROTC and Widr can tell us if they checked the unsourced edits that PCHS-NJROTC describes as goodfaith. I would feel more comfortable with such a long block if those unsourced edits were actually known to be sneaky vandalism. Conversely if they were checked out as legit I'd be inclined to support an unblock. ϢereSpielChequers 12:04, 22 October 2017 (UTC)
I checked the three good faith edits, and sources show that the edits were proper. The change to Lemon Bay High School was correct according to the school's website (I probably should add a citation to that). I also checked the edit to cannabis cultivation and the sources I found in a search engine supports the new version (I probably should have added a citation to that as well). We need to remember that the three unsourced edits could very well be three new editors who probably don't know how to properly source an edit. You are absolutely correct about the block policy not being followed (for that matter, the shared IP templates are supposed to remind people "hey, this IP represents thousands of people, don't assume what happened yesterday has anything to do with what happened today," but that goes over so many people's head these days. The problem is convincing other's that there's anything wrong with these blocks. "Oh, these IPs do nothing but vandalize" is their argument. Well? 50% vandalism is not nothing but vandalism. Actually, most of it's more like test edits, which are different from vandalism according to WP:VANDAL, unless we're saying that these twelve year old girls are actively conspiring to harm the project, rather than just curiously editing to see what happens (which, if that's the case, why do so many revert their own nonsense?). Considering test edits, shared IPs produce a LOT less vandalism than people think. PCHS-NJROTC (Messages)Have a blessed day. 12:21, 22 October 2017 (UTC)
I have now lifted the block because of this discussion. However, I will note that typically blocks for schools and institutions are made with cascading lengths. This one has gone from one block to another since 2012, making this their eighth block. When there's an obvious history of abuse, the usual cycle of warnings and reports to AIV tends to be a waste of time and resources. Anyone who frequently patrols recent changes knows this. And, to the original complainer: next time you can come to my talk page to express your concerns. That always works better than a snarky ping. Widr (talk) 13:09, 22 October 2017 (UTC)
@Widr: as a recent changes patrol and a member of the WP:Counter Vandalism Unit, I am very familiar with how blocks are escalated. I am saying that in most cases it is silly and is an issue beyond school IPs or even shared IPs; what are the chances that the same person editing from an IP today is the same person that was editing four or five years ago, especially in a school where students are prone to graduating? Where is the pattern of abuse warranting such a long block? Is Willy On Wheels using it? Grawp? Mmbabies? The previous block expired in September, and there have only been six edits since then. Six edits spread out over the period of about one month, half of which are good faith, does not warrant even a short block on more than 16,000 users, much less a six year block, in my opinion. That would be like blocking cities from editing because three people acted stupidly, because any given /24 range representing any random city's DSL or cable modem customers probably generates the same amount of vandalism. If we, as a community, can't handle a few instances of stupidity, then the concept of an open, user generated encyclopedia is a failure. By the way, the reason I didn't go to your talk page is because I didn't expect anything to be done about the individual block; I wanted to use it as an example of a broader problem (but I do thank you for acting in the situation). PCHS-NJROTC (Messages)Have a blessed day. 18:19, 22 October 2017 (UTC)
This seems really excessive. Is there anyway to reverse this 6 year IP ban? I think you make a really good argument as to why this is not only detrimental to the encyclopedia but actively disenfranchises an entire community. Think about the implications for systemic bias here as well. After reading tyhis, I'm inclined to make a proposal to block IP range bans completely, except for short cooling off periods of a day or so.Egaoblai (talk) 01:39, 21 November 2017 (UTC)

Alt suggestion - smart blocking

There is a problem with collateral damage when blocking IPs, but equally there are problems with not blocking IP vandals. One possible solution that I've been considering for a while is to move to smart blocking - User:WereSpielChequers/IP_and_OS_blocks. Use the IP info to block anyone at the same IP address with the same hardware and software as the vandalism edit. There would still be some collateral damage, especially at any schools where all students get issued the same tablet, and a risk that people would be freer with IP range blocking if they knew there would be less collateral damage. But I think it would be a big step in the right direction, and unlike a few years ago there is now budget to do some IT investments like this. ϢereSpielChequers 16:32, 25 October 2017 (UTC)

This reminds me that I have notes somewhere about a similar system suggestion that'd be like implicit live checkuser, possibly filling a log (restricted to checkusers and admins perhaps), about block-evading suspects matching data hashed/stored in the last 30 days or such (which would include information like IP address, username if any, permanent blocked cookie if any, user-agent and other HTTP query fields, and maybe some page-interaction/coincidence score info; each match could increase a score count, with a certain score considered plausible evasion). It'd make sense for any such experimental system to first fill a log for patrollers instead of automatically blocking, though... Another challenge, if eventually completely automatic, would be to properly configure aspects like the LRU-like database backlog, report log FIFO size, autoblock length, for the best possible performance while still generally allowing legitimate IP editing... —PaleoNeonate – 20:19, 25 October 2017 (UTC)
Good god, no—this (the auto-created deathlist proposal, not WSC's initial suggestion) would at the very best be grossly unethical, and at worst outright illegal. Contrary to what the conspiracy theorists would have you believe, CU data is some of the most closely guarded data to which any functionary has access, and with good reason, since IP data quite often reveals a user's workplace, place of education, etc; a semi-public log cross-correlating editors who have the same employer or who live in the same house would be a disaster waiting to happen. If anything remotely resembling this were ever to go live (a moot point, since Legal would immediately veto it) it would probably be enough to trigger a WikiTravel-style full-scale schism and mass exodus. ‑ Iridescent 22:35, 25 October 2017 (UTC)
If you carefully read my post, I'm also talking about a limited-time cache (no trace need to persist after 30 days for instance) and restricting log report access to those with existing checkuser rights... —PaleoNeonate – 22:38, 25 October 2017 (UTC)
And more details: the servers already have the necessary information, I can also assure you that many corporations have more sophisticated IDS software. Entries would also only need to contain information related to editing (not read page access) and the only relevant information is for users blocked in the last x days, etc. And of course, nothing of that is in the works that I know, I'm merely participating to the discussion and brainstorming possibilities. —PaleoNeonate – 23:01, 25 October 2017 (UTC)
I'm sure many organisations collect the necessary information and have such tools. But my proposal is based around our unusual commitment to privacy. Hence admins would not learn IP information, other that if there were two currently active editors at one IP address, if you blocked the vandal and the goodfaith editor continued you could assume the two editors at that IP address had different hardware or browsers. ϢereSpielChequers 11:14, 26 October 2017 (UTC)
I am a CheckUser on Conservapedia and I never understood the power and sensitivity of CheckUser data (and the hazard of heavy handed admins having access to it) until I had access to it myself. That said, since I've personally been able to identify patterns of trolling with it, I might support this automated flagging system... if the sysops here weren't so heavy handed. We have admins who seriously think activity from a four-year high school that was blocked five years ago is relevant to the actions of students today, some of these admins are CheckUsers, and especially since a good faith editor from an institution with hundreds of the same model of Compaq Evo running Windows 7 and the same version of Mozilla Firefox would be technically indistinguishable from a vandal at the same institution in absence of XFF headers showing the local IP, I don't trust them to make sound choices. In fact, using CheckUser for fishing can open the door to innocent people having their geographic location outed if they are accused of being a sockpuppet because they used an IP publicly known to be involved in sockpuppetry. PCHS-NJROTC (Messages)Have a blessed day. 18:02, 26 October 2017 (UTC)
Another part solution to the problem of out of date IP blocks and messages would be to unblock and blank messages when the whois information changes. That would require an adminbot with access to whois info. but should be fairly simple to harvest who is info on all IP addresses that currently have more than a month of block to come, then every month harvest the whois for the IP blocks that have over a month to run, add new blocks to the database and unblock those where the whois has changed. You'd probably need an small exceptions list for IP vandals who learn to change their Whois info. ϢereSpielChequers 11:14, 26 October 2017 (UTC)
I think device-based blocking is a step in the right direction, but I think this version of it would be of questionable usefulness. This would be useful to stop someone from repeatedly using a particular model of Samsung tablet to vandalize from a wi-fi hotspot in Times Square without affecting users of countless alternative devices, but certain devices, like iPhones, are so popular that blocking them would still cause collateral damage, and this would do nothing to solve the problem, as described above, of collateral damage in a company or institution that uses hundreds or thousands of PCs running the same version of Mozilla Firefox on Windows 10. What would be cool would be to be able to block a specific device, perhaps using cookies, without blocking the whole NAT. This wouldn't be effective at stopping the determined teenager on her period from hopping from PC to PC in the school library (although that might attract adult attention, which would alternatively solve the problem), but it would probably stop the bored call center agent for United Healthcare or CenturyLink from engaging in vandalism without affecting his or her colleagues. PCHS-NJROTC (Messages)Have a blessed day. 18:02, 26 October 2017 (UTC)
Re: WHOIS change, the problem here is that sometimes the WHOIS doesn't change. An IP can safely transfer from a school to a hospital or a prison to a clothing manufacturer while maintaining "Level 3 Communications" (as was the case I described of a hospital getting a former school IP) or "Embarq Corporation" as the responsible organization. PCHS-NJROTC (Messages)Have a blessed day. 18:17, 26 October 2017 (UTC)
Yes, sometimes WHOIS doesn't change when it should, that's why I described it as a partial solution. But that isn't an extra problem - such IP addresses would be unaffected by this. ϢereSpielChequers 11:46, 9 November 2017 (UTC)

Troll lives matter!

Seriously, not all vandals will be so for life. Some get over it when they see we revert them in seconds. Some take a but more time. Fighting trolls doesn't mean we can be aggressive. As the Spanish saying, "being polite does not prevent being bold".— Preceding unsigned comment added by NaBUru38 (talk • contribs) 22:05, 18 November 2017 (UTC)

I agree with you that most probably eventually mature. There of course also are the occasional ideological campaigns. However, "aggressive" anti-vandalism protects the encyclopedia's integrity and hurts noone. We are not advocating to indefinitely prevent vandals to grow up and edit constructively (i.e. non-socking indefinite blocks are usually appealed successfully after a reasonable delay or a new properly behaving account gets created (or new address used) without raising suspicion). The above "smart block" options, if implemented would likely be most effective for short periods (like 30 days). —PaleoNeonate – 05:08, 21 November 2017 (UTC)
When the aggressive anti-vandalism methods involve blocking innocent people, then I think that it hurts a lot of people, beginning with the innocent person, who doesn't get a better understanding of how Wikipedia works, and the readers, who would (statistically likely) benefit from the contributions from that innocent person. WhatamIdoing (talk) 03:18, 1 December 2017 (UTC)

Christmas Theme?

Hello, would it be possible to have a festive thing on the Main Page for December 25th? I'm not proposing it to say 'Merry Christmas' (as it may be fine for Christians, but not in other religions), but what about like a snow effect on top of the page? A simple snow layer that covers the top of pages is what I mean. Example (rather crude and basic, but understandable): ---Snow--- 

                                                                  ('Read, edit source, history, section)

Thoughts on this? AllyGebies (talk) 04:05, 13 November 2017 (UTC)

Please not snowmen and reindeers etc! It's mid-summer in the southern hemisphere. The systemic bias is already bad enough, let's not pile on even more. Roger (Dodger67) (talk) 07:46, 13 November 2017 (UTC)
What the man said.--Elmidae (talk · contribs) 08:17, 13 November 2017 (UTC)
Please not anything; why should one day be singled out for festive treatment? This is a global project not NorthAmericaPedia, and in most of the world Christmas is just another working day; there will likely be something related to the date in DYK and/or OTD and that's enough. Do you want us to deck the Main Page out in Eid Mubarak bunting, Diwali fireworks and Chinese New Year lanterns at the appropriate times of year as well, or give it a red-and-white colour scheme on St George's Day? — Preceding unsigned comment added by Iridescent (talk • contribs)
Actually this is an English speaking project, not global at all! The vast majority of English speakers are in the northern hemisphere, only alienating those in Australia and New Zealand. There are even Wikipedia pages at Christmas and holiday seasonand War on Christmas, doing special things is a great way to resist the same old same old, I like the Diwali fireworks and Chinese New Year lantern ideas. Happy Holidays! Dougmcdonell (talk) 03:35, 15 November 2017 (UTC)
English is a global language and is used in every region at varying levels. Egaoblai (talk) 03:32, 3 December 2017 (UTC)
I think it should also be remembered that English is spoken in South Africa, Botswana, Zimbabwe, Zambia, Namibia, Tanzania and Kenya as well, so its not "only alienating those in Australia and New Zealand" to include winter thematic decorations. Besides, Christmas traditions (and other winter holidays) vary all over the world. This proposal would also involve technical changes and I don't know how difficult those would be to implement. I think Iridescent is right that "there will likely be something related to the date in DYK and/or OTD and that's enough". Heck, even the occasional FA of the day has relevance. Perhaps instead you could devote your time to filling those up with bits of information that can be shown on the main page on the relevant holiday. Maybe even create a small task force devoted to organizing such things. I'm not sure of the whereabouts of the old WikiProjects devoted to ensuring everyone on the Wiki was happy and cheerful, but I'd go there to look for a team. -Indy beetle (talk) 15:13, 18 November 2017 (UTC)
And I would add that there are more people in India who can read some English than in any other country, with the possible exception of the United States (I can't be bothered to look up the figures now because my point stands as we are talking about hundreds of millions). The vast majority of those do not follow Christian traditions. 86.17.222.157 (talk) 19:29, 22 November 2017 (UTC)

During Christmas, I would support adding notable articles, did you know, photos, etc related to Christmas in the main page. Same for other notable dates. --NaBUru38 (talk) 22:10, 18 November 2017 (UTC)

We generally encourage the use of TFAs which are related to the day - examples include Israel on Israeli Independence Day in 2008; Guy Fawkes Night for that day this year; Washington, D.C. for the day of Obama's first inauguration. I also see that Eid al-Fitr was in the DYK section on that day in years 2005, 2006, 2007, 2008, 2009, 2010, 2012, 2013, 2014, 2015 and 2016. So this would appear to be followed at least to some degree. עוד מישהו Od Mishehu 09:06, 21 November 2017 (UTC)
AllyGebies, I believe that some of the other (non-English) Wikipedias and projects change their logos on certain holidays. See c:Category:Christmas Wikipedia logos for a partial list of logos, some of which have been used before. WhatamIdoing (talk) 03:26, 1 December 2017 (UTC)

Wikipedia: Requested articles

Would anybody involved with the above discussion like to clarify how Articles for Creation differs from Wikipedia: Requested articles? Vorbee (talk) 18:49, 5 December 2017 (UTC)

Vorbee Basically RA is a list of presumed notable subjects which need someone to research and write an article on them, while Articles for Creation is a submission handling and notablity/quality control desk. L3X1 (distænt write) 19:15, 5 December 2017 (UTC)

An issue with Special:BookSources

A reader wrote to Wikimedia (OTRS) and the belief that there was some error in Special:BookSources.

While I don't think it is broken, I think I know why they think there's a problem when I agree that it should be addressed.

If you go to the book sources page using the link I provided, the ISBN field will be blank, and the rest of the page below the search box will be empty. If you enter and ISBN, then click on "Search", the page will populate with a lot of links. For those that use this page in that way, I don't think it will occur to them that there is a problem.

However, if you are on some page which happens to have an ISBN and click on it you will be brought to the page with the ISBN filled in and the search already completed. For example, Special:BookSources/1401303714

If you are on that page and click "Search" you won't see anything visibly happening. You might think that the search button isn't working because it doesn't seem to do anything. What you have missed is that the search has already been completed and all of the links are displayed in the lower part of the page.

I think we should do something to make it clearer that the search has been completed and clicking on search isn't the right thing to do.

For example, if you are using the visual editor, and haven't yet made an edit the "save changes" button is in gray. As soon as you make a change, that button will turn blue, indicating that it can be used, and if you actually click on it, it will disappear. That convention guides the reader into knowing the three statuses (Stati?) of the button: 1 not yet available 2 available for action 3 completed

It would be helpful to do something similar. Perhaps a search button should be gray if the ISBN field is empty, turn blue when ISBN is entered, and turned back to gray after it is clicked (I wouldn't follow the convention of removing it as is done with "save changes" as the user might want to enter a different ISBN)

I think the next step is to file something at phabricator but I'd like some feedback from other editors before I take that step.--S Philbrick(Talk) 16:48, 3 December 2017 (UTC)

Note that for the majority of the content other than the button, you have to change Wikipedia:Book sources and do not require to file a phabricator ticket. —TheDJ (talk • contribs) 14:49, 6 December 2017 (UTC)
I think the whole concept of search is broken here btw. It's just a page with an ISBN that matches the ISBN pattern that will show a list of external search engines. —TheDJ (talk • contribs) 14:50, 6 December 2017 (UTC)

Notification system for files on Commons nominated for deletion

A typical concern with uploading files to Commons for use on enwp is that the files may be deleted without the uploader's and/or enwp community's knowledge. So, I'm thinking about building a service that aggregates Commons deletion nominations for files used on enwp. I'm currently considering two formats:

  1. A bot can post to a local noticeboard and ping interested parties (e.g. the original uploaders or editors who have elected to watch a certain file)
  2. A bot can leave talk page notifications on the uploader's talk page and/or affected articles (unsure of how to do this without being spammy for files with many uses)
  3. Other Suggestions?

Is this something that you would find useful? Any thoughts/suggestions are appreciated. Thanks, FASTILY 23:41, 16 November 2017 (UTC)

Ping for @Jo-Jo Eumerus -FASTILY 23:41, 16 November 2017 (UTC)
Er...notifications have been global since the echo system was overhauled in July 2016. If someone posts on your talk page at Commons, which they should do whenever they tag an image for deletion or start a DR, then you should get a notification here . No bot required. Check your preferences if this isn't happening. Preferences -> Notifications -> Cross-wiki notifications. --Majora (talk) 00:45, 17 November 2017 (UTC)
Sure, but how about the cases where: a) files have been transferred to Commons? b) the uploader is inactive but the file is used in an article? These are some of the specific cases that I'm interested in fixing. -FASTILY 06:38, 17 November 2017 (UTC)
Besides, I am not certain that cross-wiki notifications are by default on. Jo-Jo Eumerus (talk, contributions) 16:19, 17 November 2017 (UTC)
I believe that they are. WhatamIdoing (talk) 03:29, 1 December 2017 (UTC)
Those two cases are quite different from each other, but (b) and some of the common cases of (a) would be solveable by a bot that monitored commons and posted to en.wp. A heuristic could be monitoring "page creations of [[Commons:Deletion requests/*]]" in realtime or scanning "pages transcluded on [[Commons:Deletion requests/yyyy/mm/dd]]" at the end of each day. And (b) is easy after that: look for what en.wp pages use the image and post a note to its article-talk page. For (a), if the image description is well-formatted, can look for an en.wp user in the |source= or |author= field. And for files transwikied by certain bots or tools, there is an standard format of upload history that could be checked for an en.wp uploader. DMacks (talk) 21:16, 17 November 2017 (UTC)
...like User:CommonsNotificationBot. @ErrantX: any prognosis on your bot? DMacks (talk) 21:51, 17 November 2017 (UTC)
Its been dead for a bit so I'd have to re-write it, probably, given that it's based on a v. old pywikibot codebase. But yes, that's effectively what that Bot did. It was reasonably successful, in that it alerted to stuff; I am not so sure I have any good examples of people then fixing issues from it. And there was a tendency for certain talk pages to fill up with notices as masses of images were (correctly) removed from Commons. And then there was the influx of people asking me why I was deleting their images ;) I've got the code somewhere if anyone wants it, and technically the bot is still approved.... --Errant (chat!) 08:16, 20 November 2017 (UTC)
Currently part of the wishlist[1] with decent support. If this gets selected and User:Fastily wants to collaborate with Community Tech that would be cool. Doc James (talk · contribs · email) 21:34, 2 December 2017 (UTC)

Huh, I had the same exact idea when editing today and came here to post it. I'm glad people are already talking about/working on it! A bot like the one @DMacks: describes would be very useful, especially for pages with a lot of images. --HighFlyingFish (talk) 10:31, 14 December 2017 (UTC)

Draft Articles Severely Backlogged

I suggest draft articles should not be able to be submitted for publication without any references. I also suggest that all draft articles without any references should be removed from draft articles submitted for publication. These changes will help Wikipedia with the severe backlog. Many of the articles submitted have no references. Some use external links as the only sources for their drafts.InternetFriend (talk) 07:06, 8 December 2017 (UTC)

If you're concerned about your own draft having to wait on the queue, you can simply dispense with the review altogether and simply move it to the article namespace yourself. – Uanfala (talk) 21:10, 8 December 2017 (UTC)
Rejecting a draft with no references does not take much time, so these are not deferring the backlog by much. Graeme Bartlett (talk) 00:49, 9 December 2017 (UTC)
I would advice against Uanfala's opinion and am reviewing your draft.Regards:)Winged Blades Godric 08:23, 9 December 2017 (UTC)
Could not decide about whether this fails BLP1E.Winged Blades Godric 16:14, 9 December 2017 (UTC)
It took a huge argument to get the BLPprod policy that required new BLPs to have references. I think the time might be right to broaden that policy and require another group of new articles to require references. But such a policy change needs a justification, a problem it would solve. It might be better to go for a policy change that one could justify as a logical next step - CORPprod for commercial organisations without an independent reference. I think we could justify that as a pragmatic antispam measure. ϢereSpielChequers 13:01, 9 December 2017 (UTC)
IMO, it would be not helpful by any considerable margin.All companies other than garage-startups manage to spam the article with considerable non-self refs but of near-zero quality esp. post ACTRIAL.To insert a huge bunch of refs (including blatant blogspam, PR Spam et al) in almost any CORP article is insanely simple (see Cunard's contribution to numerous CORP Afds and DRVs on the issue).We have paid-editing-companies that promises to publish a host of PRs, webentries, obscure business journal covg. etc. about your company in lieu of a certain amount and then source the WP artice with those! The field of CORP promotion is awfully bad and if we want to speed up deletion of CORP articles than currently achieved by a combinaion of A7, G11and normal PROD, we need the sysops to be able to properly review the quality of sources and take a decision.Notwithstanding the fact that not many are proficient at that and discussions etc. are parts of the AFD-zone, shall this proposal be ever put before the community, I don't think the community will grant the discretionary authority to sysops to judge the reliability or practical independence of sources (anything other than self-cites) and click the delete button based on such an assesment.Winged Blades Godric 14:43, 9 December 2017 (UTC)
A massive increase in the notability requirements at WP:CORP would help a lot. I've been wondering about a requirement for two sources that each use more than 500 consecutive words to describe the company. It might help clarify the notion of WP:SIGCOV in some people's minds. There are some other requirements that might help, such as requiring evidence that there was independent attention given over the space of more than X years (two, three, five?). We could also insist that the sources include significant coverage in the nearest regional newspaper (e.g., Los Angeles Times for anything in southern California, San Jose Mercury News for anything in Silicon Valley, etc.), and hope that these newspapers would resist the publicity campaigns.
Or we could just ban (nearly) all non-publicly-traded companies. And their staff. And their products. Because that's the main problem with piecemeal increases in notability standards: if you say "no more unimportant companies", you will get WP:COATRACKs that are nominally about their notable CEO. WhatamIdoing (talk) 00:43, 14 December 2017 (UTC)
  • The suggestion by WereSpielChequers for a CORPprod for commercial organisations without an independent reference, is not without merit. However, the contents of the New Pages Feed have changed dramatically since ACTRIAL, and this issue is no longer prevalent. Ninety-five percent of the junk at NPP has been stopped in its tracks; the major problem now is one of educating the reviewers to recognise artspam and paid editing which for all intents and purposes look like legitimate, well formatted, well referenced articles. The idea of a CORPprod might work on drafts, but only if experience has shown that drafts are generally dumped into AfC and not revisited by their creators for over a week. We need to know if this is a fact, and the percentage of submissions that meert this criterion and which contribute significantly to the backlog.Kudpung กุดผึ้ง (talk) 01:03, 11 December 2017 (UTC)
I don't think it'll really be useful - unless things that are described as trivial in WP:CORPDEPTH are somehow excluded, I'd say a very small fraction of company articles can really have no "independent" sources at all. Galobtter (pingó mió) 08:21, 13 December 2017 (UTC)
Galobtter the issue is not really CORPDEPTH but WP:ORGIND and WP:SPIP. The overwhelming majority of corporate articles at AfD are deleted for having no independent sources under ORGIND. TonyBallioni (talk) 03:36, 14 December 2017 (UTC)
TonyBallioni The main problem is that the line between what is or is not independent is in many cases not clear enough for a CORPprod - most corporation drafts I see at AfC usually have a few articles in newspapers that don't readily identify as press releases, but look to be based mostly off of interviews or press releases. Perhaps there are a lot of articles that get deleted at AfD without even that, but at least at AfC that's what I see. Galobtter (pingó mió) 03:50, 14 December 2017 (UTC)
Which are primary sources and aren't independent. Anyway, I support moving to an objective corporate standard along the lines that I think WhatamIdoing is suggesting. There's some brainstorming currently going on about that at the WT:CORP page currently. TonyBallioni (talk) 03:52, 14 December 2017 (UTC)
I'm not saying it should be kept on that basis. But BLPprod is very clear in that even one link that supports it is enough that it isn't applicable. A CORPprod would have to be similarly clear, or else I don't see how it can done. Galobtter (pingó mió) 03:54, 14 December 2017 (UTC) Godric put it well above - "manage to spam the article with considerable non-self refs but of near-zero quality". Galobtter (pingó mió) 12:01, 14 December 2017 (UTC)

Translation Ideas

How about instead of only extended confirmed users being able to translate, it should be auto confirmed. Imagine all the valuable bilingual wikipedias were turning away because they find they have to have been on wikipedia for 30 days and 500 edits. Also I believe the new translations editor should have categories for people who are skilled in that area. YuriGagrin12 (talk) 02:13, 20 December 2017 (UTC)

Did you read the discussion to which you were linked the last time you proposed this, within the past month? --Izno (talk) 13:16, 20 December 2017 (UTC)
@Izno: Yes I did, I didnt see anyone bring up the point of potential wikipedians we might be losing, also I never talked about catagories in translations. YuriGagrin12 (talk) 18:43, 20 December 2017 (UTC)

Net neutrality protest

In light of today's vote, would anyone be up for a coordinated protest? Maybe one in silicon valley because that's where the tech companies are? I would say like a march or rally. Bardic Wizard (Tell your congressman to vote for net neutrality) 21:56, 14 December 2017 (UTC)

Look, guys, an American who thinks he lives in a functioning democracy! *runs away giggling* (((The Quixotic Potato))) (talk) 22:00, 14 December 2017 (UTC)
@The Quixotic Potato:What did you call me?!?!?</anger></humor> No, I'm serious here. There's been lots of Wikipedian meetups: how about a protest? Bardic Wizard (Tell your congressman to vote for net neutrality) 22:55, 14 December 2017 (UTC)
@Bardic Wizard: I agree completely, we protested for SOPA why not net neutrality, the internet providers could easily restrict pages that criticize it. YuriGagrin12 (talk) 23:17, 14 December 2017 (UTC)
Yeah. Coordinated protests would work, maybe in the next couple weeks? I'm open to ideas. Bardic Wizard (Tell your congressman to vote for net neutrality) 23:25, 14 December 2017 (UTC)
@Bardic Wizard: I thought like shutting the website down for a day like with SOPA because internet providers could just not show pages about net neutrality. YuriGagrin12 (talk) 23:36, 14 December 2017 (UTC)

I like the idea raised at the Proposals Village Pump by User:Ckoerner: have an editathon on net neutrality-related subjects. It highlights Wikipedia's strength, collaborative editing, improves coverage of important topics, and generates publicity without blocking access to Wikipedia's content. isaacl (talk) 00:14, 15 December 2017 (UTC)

That sounds like a good idea, @Isaacl:; maybe this upcoming week (December 17 to December 20th (because people are prepping for Christmas then)). Bardic Wizard (Tell your congressman to vote for net neutrality) 00:36, 15 December 2017 (UTC)
Maybe after Christmas, but before the new FCC ruling goes into effect in January (17-20th is really soon IMO). SpartaN (talk) 02:30, 15 December 2017 (UTC)
Mmm, yeah. 27th maybe? — Preceding unsigned comment added by Bardic Wizard (talk • contribs) 03:06, 15 December 2017 (UTC)
  • We are doing everything we can to make sure Wikipedia and her sister projects reach as many people as possible. This includes partnerships with ISPs to be included in all package levels. Additionally, we have incredible support from launching and running the zero rated Wikipedia Zero initiative from users. In many places where Wikipedia Zero operates Internet access is expensive, generally costing in PPP$ 50% of an equivalent US plan. (ITU 2015)
    We are looking forward to bringing Wikipedia to more people in the coming years. Cheers, — Dispenser 07:40, 15 December 2017 (UTC)
The big difference is that SOPA was a plausible threat to Wikipedia's existence, whereas "net neutrality" is merely a domestic US issue. Roger (Dodger67) (talk) 14:14, 23 December 2017 (UTC)
Why would locale matter, though? If it were in Canada or South Africa it's still not good. SpartaN (talk) 19:02, 23 December 2017 (UTC)
"Locale" per se does not matter, whether it is in Benin or Belize is of no significance, the point is that it is a purely domestic issue in only one country, and it is not a threat to Wikipedia's existence, like SOPA could have been. In any case, in several places Wikipedia actually benefits from a lack of net neutrality, right now I'm editing at zero cost on my phone, Wikipedia is the only website that my network provides without charging their usual high rate for data use. Roger (Dodger67) (talk) 22:41, 23 December 2017 (UTC)

Apology ("if applicable")

Thanks for your patience if this is in the wrong place. [1]

Background

I fixed a red link today, and then after that I was "reading up on" red links, and I made a second edit, to add a "bullet" [list item] to a page that seems to be explaining about why some wikilinks appear RED instead of BLUE.

What my question is

My question is whether or not it is POSSIBLE to use the "What Links Here" tool (of MediaWiki) ... on a "section name" basis, vs. on an "article name" basis.

While doing that second edit (the "adding a bullet" edit) (here's the diff listing for that), I included this question in a comment.

It might help to see that [comment] "question" in context, there, so that you can get a better understanding of how one might be led to ask the question ... and hence, perhaps, a better understanding of what reason[s] there might be, for having (or adding) a certain cool ability or [new?] "feature" in the "What Links Here" tool of MediaWiki. The footnote containing that comment is footnote (or "ref") number "[70]" of this specific version of the article about "MediaWiki".

So ... in case you want to see it in context, you can feel free to go to that diff listing and search for a question-mark character "?" (or ... search for the more specific [comment] character string "<!-- is that POSSIBLE? -->", there.)

That footnote (number "[70]") includes an example of a situation in which that (current, or maybe proposed future) "feature" in the "What Links Here" tool, could be useful /slash necessary.

So ... the clearest explanation of what the question is, ... can probably be found by just remembering that the question [character string] goes right in the middle of the parenthetical phrase

(but, if appropriate, on a "section name" basis,<!-- is that POSSIBLE? --> as opposed to on an "article name" basis)

... while reading footnote number "[70]" of this specific version of the article about "MediaWiki".

Any advice? or comments? --Mike Schwartz (talk) 20:25, 19 December 2017 (UTC)

References

  1. ^ (Like, maybe this should have been on the "Technical" tab? instead of on the "Idea Lab" tab?) (or maybe this should have been posted at "Tea Room" instead of "Village Pump"?) (or maybe this is totally on the wrong wiki, and should have been posted somewhere on the "MediaWiki" web site [wiki], instead of [in the "Wikipedia" name space] on the "English Wikipedia" web site?)
No, it's not possible. MediaWiki doesn't really track sections internally beyond a basic counting of them when rendering the TOC and doing section-level editing. There's no concept of them in the database. FACE WITH TEARS OF JOY [u+1F602] 03:36, 21 December 2017 (UTC)
I wish you could isolate the links that only connect via navigation templates. Sometimes it would be helpful to know when articles are linked by prose, or just templates. ---Another Believer (Talk) 03:49, 21 December 2017 (UTC)
For red link fixing there's Wikipedia:WikiProject Red Link Recovery. The tools are currently broken. — Dispenser 05:25, 24 December 2017 (UTC)

Wikidata request for comment on the ideal data import proccess

Dear all

We are currently running a discussion on Wikidata about what the ideal data import process looks like. We want to get the thoughts of people who work on different Wikimedia projects who have different needs and knowledge of different kinds of data to make it our roadmap as inclusive as possible, please take a look.

Many thanks

John Cummings (talk) 01:29, 25 December 2017 (UTC)

Changes to top icons

I have a proposed change to the images that the top icons show. Instead of showing this image for administrators, this image for pending changes reviewers, this image for template editors, etc…, what if there was a gold-colored key for administrators, a white/silver-colored key for pending changes reviews, a blue key for extended-confirmed editors, etc…? (The colors come from the colors of the respective protection lock icons.) They would be much easier to discern from each other at 20px size than a bunch of variations all of the Wikipedia logo.2601:2C1:C280:3EE0:28D0:B79C:E846:C47A (talk) 20:12, 26 December 2017 (UTC)

They're called top icons. L3X1 (distænt write) 22:18, 26 December 2017 (UTC)
And their addition to talk pages is entirely voluntary. Although adding a system-generated category to admin talk pages is not a half-bad idea. It would cut down on the "are you an admin?" questions and impersonation. --NeilN talk to me 22:27, 26 December 2017 (UTC)
My suggestion is about changing the top icons, not making them mandatory.2601:2C1:C280:3EE0:E4DE:19E1:23D8:57C8 (talk) 22:54, 26 December 2017 (UTC)

Suggestions for reducing the AFC backlog

Now there are nearly 2700 AFC submissions pending for review. The backlog level is now "Extremely backlogged". To reduce the backlog, I have some suggestions:

1. Review old submissions first. The backlog level depends on the age of the oldest submissions(When there are very old submissions, it depends on the number of very old submissions), so that reviewers should review old submissions first. This can also reduce the average time waiting for review.

2. Give a warn to unsourced and blank drafts when somebody tries to submit it. Many AFC submissions have no references, or use external links for references. A few of them are blank. Such drafts cannot be accepted. It's easy to decline them, but it takes reviewers' time, and non-reviewers cannot help to decline them. So when a user is trying to submit a unsourced or blank draft, you can warn them that the draft is not sourced(or the draft is blank) on the page of submitting.

3. Upgrade auto declining system. This is the most difficult way, but it is very useful. Some drafts are very clearly non-acceptable, for example, unsourced ones, blank ones and test editing. They can be automatically declined. This can also save reviewers' time to let them review more drafts. If you can't upgrade it, this can also be helped by some non-reviewers.

4. Find a way to reduce new submissions. If possible you can find a way to reduce new submissions to contain the growth of backlog.

5. Encourage users who meets the reviewer standards to join the reviewers. This can increase the reviewing speed a lot. But you have to avoid the falling of the quality of reviewing.

What's more, reviewers who have enough time should work harder to reduce the backlog. I believe that the backlog level can fall a lot someday(even reach the level "Normal") Thanks. ~Omega68537(talk)Omega68537 14:34, 22 December 2017 (UTC)

Find a way to reduce new submissions I think one would be to encourage people to submit to mainspace directly once they are autoconfirmed if they are confident. Maybe send them a message. Galobtter (pingó mió) 14:49, 22 December 2017 (UTC)
6. Run a backlog drive. It is what we are doing at NPP in January. The auto decline system (#2) should not include unsourced drafts (though preventing completely blank submissions makes sense). Many newbies have no idea how to format a reference, moreover some obviously notable topics should be able to be accepted even if no references are in the article. If someone does a search and reliable sources explode onto the screen, just chuck {{sources exist}} on it and publish it to main. This is one of the biggest ways that AfC's standards are much more strict than NPP, AfD, and Wikipedia in general. Guidelines demand that sources for notability WP:NEXIST, AfC seems to demand that these sources are in the article and formatted properly. — Insertcleverphrasehere (or here) 18:48, 22 December 2017 (UTC)

@Insertcleverphrasehere: Hello. Yes, many newbies cannot add references. But most drafts without references are not acceptable, so these drafts should not be submitted. Secondly, I saw that the number of AFC submissions has been reduced to 2500, but the number of very old submissions has been increased to 700+. I've said "Review old submissions first". But many reviewers didn't do so, so that the number of old submissions has been increased. ~Omega68537(talk)Omega68537 14:40, 26 December 2017 (UTC)

@Omega68537, if a new user is unable to figure out how to add a reference, how are they meant to submit their draft? What about a submission that has references, but no links or inline citations? I'd support having a warning for having no references, but there are so many problems with an outright prohibition. It's BITEY and it just isn't workable. — Insertcleverphrasehere (or here) 17:45, 26 December 2017 (UTC)
A backlog drive has been discussed and the community appears to be receptive. Reviewing oldest submissions first is most fair but reviewers are WP:VOLUNTEERS and some prefer to go for the easy reviews sitting towards the beginning of the queue. The other proposals listed above are also going after the easy reviews and so I think implementing any of these will just have the effect of sending these reviewers to easy work elsewhere and will not help much with the current backlog of more substantial reviews. ~Kvng (talk) 16:50, 26 December 2017 (UTC)

@Insertcleverphrasehere: Yes, you are right. For newbies, we should follow WP:DBN. When a newbie is submitting an unsourced draft, it's not suitable to block this. It's better to give them a warn, and remind them to read WP:REFB to learn adding references. But blank drafts should be blocked from submitting. ~Omega68537(talk)Omega68537 13:05, 27 December 2017 (UTC)

Does Wikipedia need an article that provides for some standardization of BLP articles?

Recently, I've been editing BLP articles (mostly adding cites, correcting grammar and occasionally adding new material). I've noticed that there appears to be no standardization of the sections in these articles. If you look at featured articles, the issue seems pervasive, but perhaps I'm being too anal. I searched the MOS for guidance but didn't find any. I wonder if there would be some value in an article that described how the sections of a BLP article should look? For example, if the LP's early life is important, a section titled ==Early life== should be included in the article. If the LP's career is important, a section titled ==Career== should appear, and it should be placed after the early life section. References should always be at the end. Notes directly before preferences, etc. I think it would be helpful to editors like me to have some guidance in the recommended structure and positioning of the elements of an article. Obviously, there will always be exceptions, and that should be pointed out, but when many articles follow no format at all, it's confusing trying to figure out how to write an article. I'm working on my first draft proposal for an article, and I'm not certain if the article elements are ordered correctly, or even if there is a correct order. Txantimedia (talk) 01:30, 8 December 2017 (UTC)

Txantimedia MOS:ORDER advises on the overall ordering of article components. As regards the content, MOS:BIO goes into a lot of detail about the lead paragraph, and for the rest recommends normally sticking to chronological order. Hope this helps: Noyster (talk), 10:35, 9 December 2017 (UTC)
I have read both of those. They are helpful, as far as they go. But the Body section isn't clearly defined, except that things should generally be kept in chronological order. I'm suggesting that an article explaining the body more fully and suggesting titles for the sections would be helpful to new editors. Some of the others aren't entirely clear. For example, what is publications? Is it books? Newspaper articles? Journal articles? And how many should be listed? How do you chose which ones? I think these are all things that editors struggle with, and some guidance would be useful. Txantimedia (talk) 16:57, 9 December 2017 (UTC)
I always find it strange to encounter a biography that contains a ==Biography== section heading. (I guess we're meant to believe that the rest of the page isn't part of the biography?) WhatamIdoing (talk) 00:33, 14 December 2017 (UTC)
I routinely remove "Biography" headings and "upgrade" the subheadings under it to L2. I usually do this when accepting an AFC submission. Roger (Dodger67) (talk) 14:09, 23 December 2017 (UTC)
Other than basic layout parameters, it is difficult to standardize all possible structural elements because BLPs vary so much; one on a football player currently active will be very different from a retired ballet dancer, for example. A business leader's article will need a different structure from that of an artist. The GA and FA standards are useful for BLPs and a good guideline for all articles. Montanabw(talk) 01:28, 31 December 2017 (UTC)

Have you looked at Wikipedia: Biographies of Living Persons?Vorbee (talk) 16:34, 6 January 2018 (UTC)

How to help address a reasonable request

Wikimedia was contacted regarding a statement in Mike Furrey. The statement asserts that in 2011 the subject was one of a number of former players suing the NFL.

The statement is supported by two published reliable sources.

There are two complications. One relates to how his name came to be included in the lawsuit but I don't think that's worth pursuing — I only mention it for completeness. The main complication is that Mike Furrey (and/or his legal representative) arranged to remove his name from the lawsuit.

Not surprisingly, while this issue is important to the subject, it didn't prompt the two publications to issue a follow-up story updating the record.

I have provided what I believe is our official advice; namely that information that is supported by a published reliable source and is editorially relevant can only be removed if there is a subsequent publication summarizing the updated situation.

While it seems likely that either or both publications would issue a follow-up story when the lawsuit is resolved, either identifying a settlement or a win for either side, it is hardly surprising that neither publication would be moved to write a story about the removal of one name from the potential plaintiffs. We can equally appreciate that Wikipedia is one of the most widely read websites, and it is perfectly understandable that the subject would not be happy to see the statement about him which is not currently true in the article and would like to know how to correct the record.

I understand that our official advice is we need to see a retraction or correction from the publications, but the subject has no leverage to insist that they write such an article.

Does anyone have thoughts on other options?

One option that occurred to me is that while concussions in the NFL are a big deal, as witnessed by the long and extensively footnoted article: Concussions in American football the inclusion of the entry in the article about a particular player, especially one who is no longer part of the lawsuit is not relevant to the article about the player.

It may also be relevant, that the above-mentioned article does not mention Furry.--S Philbrick(Talk) 20:31, 5 January 2018 (UTC)

Provided that WP:V can be satisfied
1) In the absence of any other secondary reportage, if the court document is available and clear in its wording, then use that as the source (and tag with bettersource?) for a short sentence. Balance of Harm trumping Secondary and all that
2) A bureaucratic alternative would be for him to publish a statement on his official website or via one a publication's letter column, and word things as being stated by him (No. Just no).
3) I think the 2011 para should stay, but it doesn't have to. A consensus editorial decision could be made that the case as it stands is unimportant to his Bio, and remove it ~Hydronium~Hydroxide~(Talk)~ 21:25, 5 January 2018 (UTC)
With the disclaimer than I'm not your wikipolicy posterchild, I think in this case the obvious thing to do is simply to remove the mention of the lawsuit altogether (provided we have a way of verifying that the subject is no longer part of it). Just because something has references doesn't mean it should stay in an article: it's routine practice to remove sourced statements if there's reasonable grounds to question their reliability or ongoing relevance. – Uanfala (talk) 22:07, 5 January 2018 (UTC)
Would the use of a court document not violate WP:BLPPRIMARY? -- Emir of Wikipedia (talk) 16:51, 6 January 2018 (UTC)
Primary sources normally shouldn't be used to establish if a fact should be included in an article but can be used as a citation for a fact. The passage to which you refer is warning against using court documents for assertions about someone, but it this case, the removal of someone's name from a lawsuit is a purely factual matter, with no burden of proof required. I believe if the lawsuit is deemed sufficiently significant to warrant inclusion in the article, then by extension the removal of the subject's name from the lawsuit is also significant and should be mentioned. isaacl (talk) 18:56, 6 January 2018 (UTC)
Thanks for the suggestions, I will look into the options.--S Philbrick(Talk) 20:03, 6 January 2018 (UTC)
You might also consider whether this is a case where WP:Editorial discretion applies. The sources here look pretty solid (two long news articles, including analytical statements about why Furrey's alleged participation is significant). However, if something is source-able, but we have a solid reason to believe that it's misleading, then editors are allowed to omit it or to copyedit to make it less misleading.
(Also, it's weird to have a lawsuit about football be listed under the section heading ==Outside of football==.) WhatamIdoing (talk) 21:28, 13 January 2018 (UTC)

MONOTYPICFAUNA initial guideline change proposal

Hello, I wrote initial proposal sensu Wikipedia:Policies and guidelines#Good practice for proposals within WP:PROPOSAL at Wikipedia talk:WikiProject Tree of Life#Guideline change proposal based on previous discussion Wikipedia talk:WikiProject Tree of Life#Monotypic genera. So I am writing here also request for early-stage feedback. I would like also improve a proposal in response received from outside editors and so on everything within the procedural policies. Maybe I did misundertood to User:Peter coxhead when he wrote the word "consensus" in this phase, but I think he is not doing fair. --Snek01 (talk) 15:52, 14 January 2018 (UTC)

Since there has already been extensive discussion at Wikipedia talk:WikiProject Tree of Life#Monotypic genera, I think it would be better to respond there, so as to keep all the material together. Peter coxhead (talk) 17:41, 14 January 2018 (UTC)

Idea for a protection bot with sysop rights

Has anyone ever thought of making a bot that can reinstate old protection levels after an administrator has to place a tougher protection for a shorter duration than the original protection level? I seem to keep running into this issue at RFPP, and the idea has been rolling around in my head for a few weeks now. If there are any relevant past discussions I'd love to review them, if anyone can point me in the right direction. — Coffee // have a ☕️ // beans // 08:10, 16 January 2018 (UTC)

There's Phab:T41038 for the proper, mediawiki, solution to this. There's also this previous discussion. I have a vague memory that a bot did start doing this, but I can't find anything more than those two links right now. Sam Walton (talk) 12:05, 16 January 2018 (UTC)

Changes to article creation

I haven't put anything forward before and I'm not that knowledgeable on the technical side, so I'm looking for advice to help shape my idea into a solid proposal. I work on New Page Patrol and spend a lot of my time contacting editors asking them to add their source(s). This takes up a huge amount of my time, and will be the same for others.

My idea is that when an editor clicks to save an article to the mainspace, it comes up with a message saying 'Please add your sources' or something similar, with a good link to a simple how-to guide so newbies are not put off. I'm essentially thinking of how it is when you fill in a form online but don't add in your phone number or something else it deems essential. It could then either just not save until they're added or have an option for clicking that no sources will be added. An exception will need to be made for disambiguation pages and redirects.

The advantages are it would hopefully reduce the crazy backlog at CAT:UNREF - a backlog of over 11 years and more than 200,000 articles - and would certainly stop it increasing. It would make New Page Patrollers faster and more efficient, helping bring down their backlog, which currently means many articles are being indexed by search engines before anyone's looked them over, because we can't get to them all in the 90 day limit. It would also fit in with the idea of improving quality rather than just aiming for quantity, now we're several years down the road with this project. It would also make the importance of WP:BURDEN and WP:V clear.

Only potential disadvantage I can think of would be that it could put people off creating articles if it wasn't made clear and simple.

Any comments? Boleyn (talk) 14:48, 28 December 2017 (UTC)

Garbage in, garbage out. If you force an interaction where some value is required, and the interface fails to complete the action without it, the most common reaction will be to fill the field with any value, usually garbage. This is basic common knowledge in interaction design.
It's OK to provide a warning and guidance to educate editors who didn't know better, but the Save action should work the second time even if this References field remains empty. A backlog where unreferenced articles are easy to find is much better than one where well-refrenced articles are mixed with those using garbage references, without any way to distinguish between them. Diego (talk) 15:10, 28 December 2017 (UTC)
Very interesting point I hadn't thought of. Boleyn (talk) 15:44, 28 December 2017 (UTC)
I support this idea. The messages shown to the editor who tries to save an unreferenced article need to include:
  • If this is an article about a living person and has no references it will be deleted (see WP:BLPROD)
  • Any other article with no references is likely to be deleted if it fails to show the WP:NOTABILITY of the topic.
In view of Diego's comment above, perhaps we need to allow unreferenced articles to be saved but add a new CSD criterion for newly-reviewed unreferenced articles which have been in the encylopedia for 24 hours (to allow creating editor time to finish their initial burst of editing). Any items whose refs are found to be obvious garbage could be also deleted under this criterion.
PamD 17:03, 28 December 2017 (UTC)
  • Concurring with Diego. From my experience of curating content in my subject areas (not NP patrolling, but dealing with well-established content in articles), the biggest problem is not lack of sources (after all, unsourced text clearly signals its own unsourced-ness), but sources that do not adequately support the text. The little blue superscripted numbers are there, lending credibility to the content and ensuring its survival for years, but when you check the sources you see that things don't add up. And it's not obvious garbage that can be easily caught: these are legitimate and relevant sources, but just ones that the contributor has found, say, on a google books search without ever actually consulting them. If we started preventing users from creating articles unless they have given sources, this problem will get exacerbated. Also, this is not technically feasible as there's no way the software can tell if a given text contains sources or not. – Uanfala (talk) 18:09, 28 December 2017 (UTC)
​Yeah... we get this problem at AfC, where the reviewer declines for non enough reliable sources, then the submitter adds a dozen shitty ones. Sometimes, a couple of the dozen are reasonably good, and would be fine if they were used alone, but then it is not so easy to pull the needles from the haystack. — Insertcleverphrasehere (or here) 18:28, 28 December 2017 (UTC)
  • Concur with Diego and Uanfala. Quality can't be enforced with any kind of mechanized check list. A lack of sources is obvious, but ensuring good sources requires some critical thinking. That takes long-term training of editors and establishment of shared (institutional) standards and expectations. As it is, a lack of sources may be the best indication of where someone needs to work with the editor. ~ J. Johnson (JJ) (talk) 22:02, 28 December 2017 (UTC)
  • I beg to differ on the 'inability to capture a lacking' take: there are not a thousand citation templates out there, and it would take a minimum of text analysis (if not server-side, then client side (.js) of (to-be-)submitted text to detect the presence (or no) of one of those templates. Even if there is only one present, that means that the contributor 'gets it', and getting submissions to that level would already be a major headache relief. TP ✎ ✓ 10:44, 29 December 2017 (UTC)
    • The citation templates (and for that matter, the ref tags) are among several ways of formatting a citation. Citations that don't use them are difficult to detect without unreasonably (for this purpose) sophisticated AI, and there's no way we can persuade the community to force the use of the templates on all citations. – Uanfala (talk) 13:10, 29 December 2017 (UTC)
Yes: citations without templates are still permitted, though I wonder if that could be changed. One way might be to have a template that does nothing but enclose a manually formatted full-citation, thereby identifying it as such. I don't know if that would be acceptable to the no-template crowd. If that could be required we might at least flag articles lacking citations. But (getting back to the present discussion) I would not condition article creation on that, for the various reasons that have been raised here. ~ J. Johnson (JJ) (talk) 22:47, 29 December 2017 (UTC)
@J. Johnson and Uanfala: This problem is not limited just to the technical aspects. Lets say a new editor creates an article (probably an A7) without any sources. The newly implemented system tells him: "the article must have at least one source". There are high chances that this editor will add "www.google.com" or even wikipedia as a source. I often come around such sources. I have also seen such sources being used in notable articles, with most of the times enwiki being used as a source in WP:NGEO articles. Like in a town's article "Pathri is a taluka in the district of Parbhani.<ref>https://en.wikipedia.org/wiki/Parbhani district</ref>". The editor think this can be done as the article of the district includes Pathri in it under administrative devisions. If this is deployed we might even see websites like "cuziknowit", "commonsense", "general knowledge" and so on. —usernamekiran(talk) 12:01, 30 December 2017 (UTC)

A reasonable idea and good thinking, but Diego hits the nail right on the head. Kudpung กุดผึ้ง (talk) 11:56, 31 December 2017 (UTC)

1 A proposal at WT:CSD for the speedy deletion of unsourced articles has failed many times. I will recapitulate the reasons in more detail later, but basically it is usually very easy to add references later. We do not even require it for BLPs, but allow a 7 day period for other people to source them. My experience with bLPPRODis that I can in fact source about 3/4 of them if I think it worth the trouble (I no longer do this routinely--there are other priorities) . The only reason for requiring it for BLPs was the fear of there being articles prejudicial to living people on no basis at all, or complete hoaxes. I opposed it at the time,and subsequent experience has I think shown that there was no real danger. I've never seen a fundamentally negative BLP get as far as s BLPPROD, because there are quicker ways of removing them& we use them. .
2 The original principle of WP was not that people write articles and submit them, but that we work together in writing articles . I still hold to that--this is a cooperative enterprise. The importance of WP is not primarily that it's an encyclopedia but that it'san example of what people can do by cooperative effort.
3 I almost never use templates for references except to match a pattern. The point of referencing is to add references. Formatting them is secondary. This is true for everything else in WP, and it can apply here to. Requiring any particular template or format will be counterproductive--it will discourage people from adding references. (In fact, I never use templates at WP for anything--those procedures that require them, I do not engage it. I consider templates to be dehumanizing--they're designed for input into bureaucratic systems. WP is not , or at least is not supposed to be, a bureaucracy, either in procedure or especially in writing articles. I came to WP because it was not a bureaucracy. DGG ( talk ) 00:30, 6 January 2018 (UTC)

This sounds like a really good idea in theory. I also agree with Diego, and others who say enforcing this will be impractical. How about instead of doing it after the fact, make a notice before the fact. Maybe any IP-created pages, and every editors' first AfC should have a notice, (about deletion) as per PamD, at creation rather than save time. Maybe even a quick note as to what constitutes "original research", as many new editors don't seem to have a clue about that either. The guide pages are a tremendous help... if you can find them. Angryredplanet (talk) 06:45, 17 January 2018 (UTC)

There are many many links in Wikipedia that are in the form  : http://geonames.usgs.gov/pls/gnispublic/f?p=154:3:3029707333234350::NO:3:P3_FID

For some reason, these seem to go bad over time. The recommended link is: http://geonames.usgs.gov/apex/f?p=gnispq:3:::NO::P3_FID:nnnnnnn [1]

I'm not sure if it is a mechanical change or whether there are more variables.

This seems like a script that might be good for a beginner to write.

Bodysurfinyon (talk) 03:54, 8 January 2018 (UTC)

References

  1. ^ https://geonames.usgs.gov/apex/f?p=gnispq:10
@Bodysurfinyon: You should make a WP:Bot requests. --Izno (talk) 17:49, 18 January 2018 (UTC)

The status of AFC backlog

AfC submissions
Random submission
~6 weeks
1,095 pending submissions
Purge to update

Now the number of AFC submissions has been reduced to less than 2000, but the number of very old submissions is still above 600. The backlog level is still "Extremely backlogged". However, most of the "Very old" submissions are difficult to review, for example, BLPs.

Thiss seem to be in a deadloc. How can we solve this problem? --Omega68537 ([[User talk:Omega68537|talk}}) 13:28, 12 January 2018 (UTC)

@Omega68537: There was a recent discussion, now archived at Wikipedia:Village pump (proposals)/Archive 144#Three Strikes Rule for AfC submissions and reviews. It looks like it may need a concluding statement, Insertcleverphrasehere. If it is not listed, maybe an WP:ANRFC listing would be appropriate. --Izno (talk) 17:53, 18 January 2018 (UTC)

Template idea

Hello! I am somewhat new to the village pump, so I apologize if this belongs in the proposals section, Wikipedia already has this, or it is unnecessary, but I have an idea for a template (if this is added, the template will appear below): {{Namespacelink}}. For example: if you entered {{Namespacelink|Wikipedia:Example}}, it would return this: Example. I would create it myself, but I do not know how I would alter {{{1}}} to not display the namespace on the display link title. Cortex128 (talk) 21:23, 27 January 2018 (UTC)

@Cortex128: The template could be made with [[{{{1}}}|{{PAGENAME:{{{1}}}}}]] where {{PAGENAME}} is a magic word in MediaWiki. But MediaWiki already has a similar feature as what you want: Help:Pipe trick. [[Wikipedia:Example|]] (note the pipe) becomes [[Wikipedia:Example|Example]] when you save it. It only works on save and not in templates, and it can make other transformations on the displayed text, but I don't think there is much use for the suggested template. We don't have such a template as far as I know. PrimeHunter (talk) 22:38, 27 January 2018 (UTC)

Hey guys. You already have thousands of experts covering so much information and validating it. why don't you add links to verified videos? I think it will make learning things via Wikipedia so much better! (as a first step you can just allow pointing out from Wikipedia to youtube videos. or any other big company that holds such a vast amount of knowledge about so many things). The current state is that people read on Wikipedia and then go search for a video to visualize what they just read about. you already have the professional validating your content, why not ask them to add validated and relevant videos. I think it will be a huge gain for both you and the sites that will cooperate with you. — Preceding unsigned comment added by 212.179.28.34 (talk) 17:08, 9 January 2018 (UTC)

Anyone can already upload relevant videos to Wikipedia provided there aren't copyright restrictions, or link to them if there are. Jakob (talk) 18:32, 9 January 2018 (UTC)
I think OP could mean why are an articles not in a video format. The closet thing we have is spoken articles as mentioned at Wikipedia:Spoken articles. --Emir of Wikipedia (talk) 20:09, 9 January 2018 (UTC)
I think that the OP is probably asking why so few ==External links== sections contain links to (relevant/educational) videos on YouTube or similar sites. WhatamIdoing (talk) 21:29, 13 January 2018 (UTC)

Wikipedia:Video links has a lot of details on this question. But it would be nice if there were a way to better integrate free video content. Maybe this is an idea to ponder in the grand scheme of Wikpedia and its sister projects. djr13 (talk) 12:03, 21 January 2018 (UTC)

It's very easy to add videos to articles. The problem is that videos are much more difficult to produce and to edit collaboratively than text. --NaBUru38 (talk) 19:34, 31 January 2018 (UTC)

New kind of page protection: Full Pending Changes

A new kind of page protection which is a combination of full protection and pending changes protection - Only admins can have their edits automatically accepted and view un-accepted edits, for articles that could have lots of improvement from normal users (so extended-confirmed would not be useful), but get a lot of vandalism from autoconfirmed users. [Username Needed] 11:35, 18 January 2018 (UTC) (date is inaccurate due to forgetting to sign

  • PCR comment So you're saying that the vandalism comes from editors between AC and EC? I don't quite understand why 30/500 protection wouldn't work. Autoconfirmed users shouldn't be "vandalising' unless they are playing a long game or something. Who would accept these edits? The already quite busy admin corp? Thanks, L3X1 Become a New Page Patroller! (distænt write) 15:07, 18 January 2018 (UTC)
    • I've heard stories of vandals (especially POV-pushers) doing that in the past. — Preceding unsigned comment added by Username Needed (talk • contribs) 10:18, 19 January 2018 (UTC)
      • POV Pushers and vandals rarely overlap (you comment almost implied you that that POV pushing was a form of vandalism, it isn't). In the last ten years I can think of two editors who turned to vandalism after they'd committed over 500 edits. Both were first blocked for other reasons. If established editors, those who meet EC criteria, turning to vandalism was a real thing I'd like to see some examples. ϢereSpielChequers 19:08, 21 January 2018 (UTC)
        • I thought that POV-pushing was a form of vandalism, but even if it isn't it is still sometimes brought up at RFPP as a reason for page protection. [Username Needed] 11:23, 22 January 2018 (UTC)
          • You'd think so, right? They both make articles worse, but we draw a distinction between the two based on their perceived motivation. A vandal is someone who is actually trying to make the article worse. A POV pusher is someone who is trying to make the article better (according to their own notion of what constitutes "better"). WhatamIdoing (talk) 07:00, 23 January 2018 (UTC)

The autoconfirmed permission is very easy to get. It's not a big barrier to controversial edits. --NaBUru38 (talk) 19:36, 31 January 2018 (UTC)

  • This is not a lot different from pending changes level 2, which was highly controversial over the years that it was proposed, and has been officially deprecated as of about a year ago. Ivanvector (Talk/Edits) 19:53, 31 January 2018 (UTC)
  • @Username Needed: As User:Ivanvector says it is very like PC2 which has indeed been deprecated [2] even though shortly before a majority had approved allowing EC reviewers to be PC2 reviewers [3], close to what you are talking about. The majority was deemed an "insufficient consensus". The main arguments against PC seem to be worries about large backlogs of pending changes, and that pre-emptive protection contradicts WP core values, an argument which irritates me because anyone can still edit, the edits are just not immediately visible. Article quality is presumably not a core value. The main problem I see is that reviewers are rarely likely to be knowledgeable about the topics they review, and so will often be unable to recognise mischievous edits. A PCR reviewer in the above PC2 change discussion, User:Wugapodes, makes that point [4]. It applies to admins as well as reviewers, and answers User:L3X1's point about who would accept these edits, the poor reviewer who can't be blamed for not recognising vandalism of the non-juvenile kind.
One answer, to both backlogs and knowledge, is to give users who do understand the topics PC2 reviewer rights for their topics, as Wugapodes suggests. On my userpage I briefly discuss a way to do this. But it wont happen. The disruptive other party mentioned there is the example User:WereSpielChequers requested of a vandal with EC rights, partly as a consequence of taking a long time to find the review button, and then because admins would not block the guy. That user was bad-faith from the start but for 20 months admins would/could not recognise that. --BalCoder (talk) 16:31, 5 February 2018 (UTC)
Without wanting to gravedance, that person was blocked for offences ranging from editwarring to non neutral editing. But not for vandalism. Back to my comments "POV Pushers and vandals rarely overlap" and "If established editors, those who meet EC criteria, turning to vandalism was a real thing I'd like to see some examples." Examples means plural, and examples of vandals not POV pushers. I don't dispute that we are less efficient at handling POV warriors than vandals, but I do stand by my observation that POV warriors and vandals rarely overlap and that vandals rarely get EC status. Two of the reasons why are of course our ongoing and deepening admin shortage, and that often the admins we have who know about a particular area are too involved to block POV editors in the very areas they are expert in. ϢereSpielChequers 17:20, 5 February 2018 (UTC)
@WereSpielChequers: vandals not POV pushers. I was using user:WhatamIdoing's definition of vandalism, according to which the said editor is the personification of vandalism. That no admin would/could recognise the vandalism is rather the point of my userpage, and now you deny it too. How long an SPI archive does someone need to accumulate [5] before you acknowledge he is a vandal? And he is at it again (Special:Diff/823968976), less than 24 hours after the article emerged from 3 months protection. I asked for that protection to protect a new user who was reversing some of the "vandal's" mayhem (User:Rhys Goldstein), even though he is pushing a new electoral system, and I disagree with all his changes. That is a POV pusher. He is editing in good faith, the other guy most certainly was/is not.
admins ... too involved to block POV editors in the very areas they are expert in: Anything being done to address that? User:Wugapodes suggested giving PC to one editor. A little impractical I suspect, but that would be better than nothing, which is what electoral system articles have at the moment. Another reason is the reluctance of watchers to step in to disputes. The PR article has ca.180 watchers, none of whom offered me help during my 6-month struggle. Curious. It wasn't because my changes were outlandish, because after the main changes someone thought it worth raising the classification (Special:Diff/656157934). Some load would be taken off admins if users were more involved. --BalCoder (talk) 10:59, 6 February 2018 (UTC)
The solution to fewer admins is to appoint more admins, the community as a whole is broadly stable, we should have more potential admins coming through to replace those who go. As for whether that specific account is a vandal or a POV pusher, I'll admit to going by the block log rather than trawling through the edits, but the specific topic is not one that I edit and those are complex edits. The blocks I saw were not marked as for vandalism. If you think the lapse from protection is unfortunate then Wikipedia:Requests for page protection may be an option. As for watchlisters, 160 is a lot, but on an old page most watchlisters will be long long gone. A request on the talkpage of the relevant wikiproject might attract more contemporary watchlisters. At some point we are going to need to move from measuring watchlisters to measuring currently active watchlisters, but the difficulty there is how to do it without creating a way for vandals to identify unwatched pages...... ϢereSpielChequers 20:14, 6 February 2018 (UTC)

Nominating for deletion? OK, but if kept, then improve it

[A half-baked idea I'd like to throw in here to test the waters before I go any further.]

Thinking about a recently closed WP:ANI thread that ended in an indefinite topic ban, it occurred to me that we might add a recommendation of the following nature to WP:AFD, supplementing the exhortations of WP:BEFORE.

If the article is kept    [Shortcut: WP:AFTER]
Sometimes an article is nominated for deletion because of a lack of notability, but in the AfD discussion new sources come to light of sufficient weight to establish notability. In such a case, the nominator withdraws the nomination or else the discussion is closed with the outcome Keep. The nominator should then consider it a moral obligation to improve the article in a suitable way, making use of the newly found sources.

--Lambiam 14:03, 1 February 2018 (UTC)

There seems to be a misconception here that when an article is kept at AfD, the nominator has in some way incurred a debt or made a mistake that they need to atone for. It's not the nominator's obligation; it's everyone's job. Ideally the nominator will be as interested in getting a functional article out of this as those who find previously unconsidered sources, but there is no way we can saddle them with any "obligation" in this regard. - Something along the lines of "Editors are encouraged to make use of these new sources to improve the article" might be more suitable. --Elmidae (talk · contribs) 14:38, 1 February 2018 (UTC)
I agree. New page patrolling and nominating articles for deletion are already an involved process (and a necessity), it should not be discouraged by additional responsibilities. —PaleoNeonate – 18:21, 1 February 2018 (UTC)
Wikipedia is not compulsory, although I do appreciate the spirit of the proposal. Ivanvector (Talk/Edits) 19:11, 1 February 2018 (UTC)
Nicely put. The proposal is basically WP:SEP in a nutshell. Regards SoWhy 21:19, 6 February 2018 (UTC)

new idea

hi i want listen to article in wikipedia i have a idea example i go to nintendo article please add listen button top of article i choice listen button and listen the article or download file for listen article later add function for media wiki for record the article with a screen reader when choice listen button — Preceding unsigned comment added by 37.254.147.0 (talk) 17:01, 6 February 2018 (UTC)

There is Wikipedia:Spoken articles, but that requires Wikipedia contributors to create audio recordings of articles, and so the number of articles is limited. Chris857 (talk) 17:39, 6 February 2018 (UTC)

Terminal based viewer for Wikipedia, based on Manpages

I'm not entirely sure that this belongs here, but I'm not sure where-else to put it to get feedback from the Wikipedia community itself. I had the idea to create a simple Wikipedia viewer for use in *nix terminals, making use of the MediaWiki API to fetch data and convert it to TROFF files (the format used by manpages), so that the interface would remain familiar to users of manpages. As such, I'd like input from the community, as well as advice in regards to libraries already existing to access the Wikipedia API.

If this isn't the right place, tell me where I could put it, and I'll move it. Many Thanks — Preceding unsigned comment added by MicroTransactions (talk • contribs) 01:16, 4 February 2018 (UTC)

Like m:Telnet gateway? Anomie⚔ 19:38, 4 February 2018 (UTC)
No, not really, I'll include a screenshot of what I want it to look like (example was converted by hand) Example MicroTransactions (talk) 02:02, 9 February 2018 (UTC)

New user warning templates

A kind of new user warning template that I thought I would submit here to see what other editors think of it and how to improve it before making or proposing it.

The "uw-bulk" series - for people attempting to add unrelated or barely related content in order to stop an article being a stub

uw-bulk1

Information icon Hello, I'm Example. I wanted to let you know that one or more of your recent contributions appear to exist only to increase the article size. Wikipedia is not an indiscriminate collection of information and so edits should not be made to increase the size of articles. If you have any questions, you can ask for assistance at the Help Desk. Thanks.

uw-bulk2

Information icon Please refrain from adding unrelated content to Wikipedia articles to "Bulk up" articles. . This is considered vandalism will be reverted. Repeated vandalism can result in the loss of editing privileges. Thank you.

uw-bulk3

Warning icon Please stop. If you continue to add unrelated content to articles, you may be blocked from editing.

uw-bulk4

Stop icon You may be blocked from editing without further warning the next time you add unrelated content to articles..

[Username Needed] 10:54, 9 February 2018 (UTC)

...is that really a frequent, categorizable problem? --Elmidae (talk · contribs) 11:10, 9 February 2018 (UTC)

Five Award

We have the four award that we all know and love, so I suggest we create a Five Award. This would recognize editors that, as well as achieving the four award, brought their article through the process for WP:TFA successfully. Concept logo:
I think it would be nice recognition for editors who got to the main page, while leaving the Four Award as a goal for the mere mortals. Thoughts? ∰Bellezzasolo✡ Discuss 18:31, 6 February 2018 (UTC)

The four award already require FA status, so what do you want next? That the user then gets it deleted? Or gets it featured on 10 other wikis? TFA is not much more, and does not really improve much to do with the article. Graeme Bartlett (talk) 01:37, 12 February 2018 (UTC)

Method to tell Categories for use in userspace vs. elsewhere.

IMO, there should be a way of a user (even if some sort of technical way) of differentiating between those categories not appropriate for userspace (like Category:Presidents of the United States) vs. those appropriate for userspace Category:American Wikipedians vs. those that are appropriate for both Category:Articles containing Russian-language text. This is to help detecting WP:USERNOCAT, but could also be used for predetection of that.Naraht (talk) 19:49, 11 February 2018 (UTC)

{{Wikipedia user category}} seems reasonable. --Izno (talk) 00:03, 12 February 2018 (UTC)
Do you mean {{User category}}?Naraht (talk) 00:09, 12 February 2018 (UTC)
I figured it existed. It's a start for user categories. Not sure how best (or if we really should) try to take care of mixed categories. --Izno (talk) 01:07, 12 February 2018 (UTC)
Could also be a subcategory of Category:Wikipedians but perhaps there are other acceptable categories. Graeme Bartlett (talk) 01:30, 12 February 2018 (UTC)

Time to call time on the Articles For Creation

Fundamentally, Wikipedia is about the wisdom of the crowd (providing such wisdom is sourced). Wiki's in essense are community-collaborated sites, But I surely can't be the only one who sees that the AFC process goes against these fundamentals; Instead of pages being created and edited collaboratively, new editors (who have been led to believe that AFC is the only way to submit a new page) have their creations scrutinised at the whim of one, maybe two editors through a process that is hidden to the rest of the Wiki. this is clearly not how Wikipedia is supposed to run.

If this was a case of mere spam and joke page prevention, then it might be understandable, but it seems that AFC reviewers are actually taking it upon themselves to assess articles by quality as if they were old media editors. One account tells of a page declined for "too many citations", only for the next submission of the same article to be declined for "too little citations".

We already have New page patrolling and Articles for Deletion, both of which are much more transparent than AFC. And yet for new users to the Wiki, AFC, which is by far the strictest of any of these three, is actually the first wall they face. If anything, the AFC wall should come after the NPP and AFD, not before.

What is a well-meaning attempt to help newcomers, has actually morphed into it's opposite. I've even seen pages on AFC being nominated for deletion, when all it took was a few hours googling to find notability and create a page that was worthy. AFC essentially is putting new articles at the whim of one editor, rather than a community consensus, which is what Wikipedia is supposed to be. Not only does it contradict the principle of Wiki-magic, but it is untransparent about it. We regularly see people at AFD helping out pages, this does not happen at AFC. Does anyone really think that given a transparent choice, new editors would rather submit their articles to one editor rather than a community at AFD?

As has been reported, since 2005, Wikipedia's editor numbers have been declining, and even going down. it may or may not be a coincidence that this is when AFC started.

I think a proposal is in order to either scrap AFC altogether or reduce the acceptance guidelines to basic notabiltiy and verifiability and stop editors from acting as quality gatekeepers which is something that can be cleaned up in mainspace by the community, as it is meant to be. Egaoblai (talk) 03:28, 3 December 2017 (UTC)

  • I definitely agree with your points. But I think that some form of the AfC process will still be needed as a way for new editors to specifically choose to request the community to evaluate the inclusion-worthiness of their article. – Uanfala (talk) 11:44, 3 December 2017 (UTC)
So I guess my reasoning here, is that AFD is already the way in which the community evaluates the inclusion process. My problem with AFC, is that it's not the community evaluating, it's one editor most of the time, which puts articles at the whim of one, rather than what wiki should be which is the community.Egaoblai (talk) 04:37, 4 December 2017 (UTC)
  • The basic acceptability criteria for AfC is already whether or not it meets notability. If it is reasonable to suspect that the article will be a keep if brought to AfD then the reviewer should accept it. Obviously for BLPs there is a second layer or scrutiny but beyond that, GNG (and the other notability guidelines) is what reviewers should be going for. If you find people who aren't doing that bring it up to them.
    As for scrapping it, absolutely 100% no. AfC was created after the restriction of article creation to just logged in accounts. Now with ACTRIAL where exactly do you think people are going to go? If you think we don't have enough editors now wait until there isn't any alternative to mainspace creation. --Majora (talk) 01:03, 4 December 2017 (UTC)
    • no, AfC was created in response to the original ACTRIAL being reject by user:Jorm - "do not fix". those editors who insist on no ip article creations, responded to that rejection, with an arcane bitey process that is a ban in effect, if not by consensus rule. the fact that people will not help you in your bitey process, does not mean there is a lack of editors to help in a not bitey process. and the anti-ip non-AGF "not everyone can edit" attitude never dies does it? 98.163.68.171 (talk) 17:33, 5 December 2017 (UTC)
      • " anti-ip non-AGF "not everyone can edit" attitude never dies." SImple numbers, if we let IPs make pages willy nilly we would need to "call in reinforcement from the Illinois National Guard". I work primarily in coutner vandalism and have plenty of AGF for IPs. That is why I don't have a dumb "This user wants to stamp out IPs and make everyone log-in" userbox on my userpage. IPs and then non-auto-confirmed users were restricted for a good reason. Some of which is germane to the discussion on whether or not to kill off AFC. L3X1 (distænt write) 18:15, 5 December 2017 (UTC)
      • For the record, AfC was around long before Jorm vetoed ACTRIAL. Julià Reig Ribó was an article I accepted as a part of AfC in 2007. AfC was originally created to allow IPs to create articles. Also, for the record since I've said this off-wiki plenty of times, in my opinion AfC submissions were of a much higher quality when they were mainly IPs. Along with Kudpung I was probably the driving force behind the implementation of ACTRIAL this time around, and I certainly do not have an anti-IP point of view: I hold the belief that IP editors probably do significantly less vandalism than registered but non-autoconfirmed users and I have threatened to block users for edit warring with IPs. Hell, I even have a userbox on my user page supporting IP editing. ACTRIAL has nothing to do with IP users, who have not been allowed to create articles in over a decade. It was designed to increase the quality of articles by limiting the number of creations that simply weren't appropriate for Wikipedia. TonyBallioni (talk) 05:42, 7 December 2017 (UTC)
        • Tony, ACTRIAL wasn't designed to change article quality. It was designed to "examine the effects of disabling article creation for non-autoconfirmed newly registered editors". It is entirely possible that the net result is no change in article quality, or worse article quality. For example, we might learn that the "new" accounts most likely to deal with these restrictions are paid editors. Several editors will no doubt recall the multiple reports at WP:AN, ANI and COIN about paid editing farms shifting to using autoconfirmed accounts shortly in the weeks before ACTRIAL began (e.g., here). If ACTRIAL disproportionately discourages innocent volunteers, then the better, less spammy articles will be lost (the volunteer will not bother creating it) or hidden in draftspace (and then quietly deleted next year), but the paid editors will continue as they are now. From the comments in this discussion, it sounds like we're also learning that reducing the backlog at NPP means shifting it elsewhere, which is also not exactly an improvement to either article quality or to volunteer efforts. WhatamIdoing (talk) 00:06, 14 December 2017 (UTC)
          • That is the purpose of the research, but the driving factor behind why the community wanted it in the first place was because articles created by new accounts were crap. I'm well aware of the paid gaming of it, but it is actually very easy to spot, and if anything ACTRIAL has made its detection easier than it was in the past. TonyBallioni (talk) 00:09, 14 December 2017 (UTC)
  • If you are concerned about TPTB of AfC, why not go to WT:WPAFC to discuss the process? Also, I see that you duplicated "Draft:Geological Society of Sri Lanka" into Geological Society of Sri Lanka, which was rejected three times (or four if counting first time rejected as duplicate). I disagree with the idea to scrap the AFC; AFC is needed for now, despite its flaws. Look at Draft:Bill Fink (see history and other discussions related to it); I even requested deletion of Draft:Edward Leung Yiu-ming because I figured it's too much of a risk after several rejections. --George Ho (talk) 02:16, 4 December 2017 (UTC)
    • Here's the problem, Draft:Geological Society of Sri Lanka was sitting in AFC, being constantly rejected, and in fact up for deletion as a draft. I stumbled upon it by pure chance, as I was going on a wiki-wander and saw that it was up for miscellaneous deletion. If it hadn't been submitted to that I would have never have found it. I adopted the page and very quickly found plenty of notability proving articles in English language media, about this organisation that has been holding high profile conferences for 30+ years, publishes a peer reviewed journal and works with the government on Geological issues. And that organisation was up for draft deletion! What's clear to me at least is that many articles on AFC either rejected, abandoned in frustration or deleted, when if that same article had been submitted to AFD, it would have easily passed, or at the very least saved by an editor.
      I shudder to think how many articles are currently shelved on AFC that would benefit from community input rather than one or two AFC editors rejected them. We've all seen countless submissions on AFD that have a balance of Keep and Delete votes. AFC basically puts articles down to the luck of the draw, rather than a community consensus. If people support the notion that Wikipedia is a community-written Wiki, then the current state of AFC does not match that and must be changed.Egaoblai (talk) 04:37, 4 December 2017 (UTC)
  • Support AfC doesn't work well, just like the Incubator and Nupedia didn't work. I am regularly involved with new content -- either creating it myself or helping others get started at outreach events like editathons. I avoid AfC completely because it's so slow -- it can take weeks for a contribution to be reviewed. I don't get the impression that it adds any value because its focus is too negative -- it's all about finding reasons to say no. If a topic is worthless then let the NPP despatch it with a speedy deletion. If a topic has merit then it should be in mainspace where anyone and everyone can find it. Andrew D. (talk) 08:12, 4 December 2017 (UTC)
  • Oppose Interesting how the support for proposals to kill off the horrible useless evil AFC mostly come from people who have never done any work there, or maybe they tried it once years ago... Yes there are some bad reviews, however reviewers who are consistently bad are removed. Some of the comments here demonstrate abysmal ignorance of AFC's workflow. Perhaps a better way can be found to reduce incompetent or erroneous reviews and the workflow can probably be improved too. What some folks here are losing sight of is the essential difference between NPP and AFC. AFC is fundamentally a mechanism to actually assist newbies to write an acceptable article, NPP's only mechanism is to summarily kill off anything that does not meet the standard. At AFC the draft writer is told; "We cannot accept this draft for this reason, here is a guideline on how to fix the problem. If you need further assistance the help page is here". At NPP the only message they get is; "This is crap. Kill it!". A basic problem with AFC is that some submitters arrive there with the idea that reviewing is an adversarial process, like a court trial, and thus they are already inclined to reject the review. Those who come with a collaborative mindset have a far better experience. Roger (Dodger67) (talk) 10:47, 4 December 2017 (UTC)
  • Support If an article is good it will stand on it's own. If it is bad it will either be deleted or improved based on the nature of it's problems. SpartaN (talk) 18:07, 4 December 2017 (UTC)
  • Comment-Except AFD and mainspeace (as is the point of wikipedia) is far better a collaborative space for wikipedians to better articles. I gave the example above of how an organisation was about to have their draft page deleted, when all it took was a quick google search to prove their high notability. The problem with AFC is that its rarely collaborative, because it's normally one editor against a submitter. We also have issues of admins threatening to revoke privileges for other admins if they "let in" borderline articles. This surely cannot go ahead. Consider this example:
    • a page on mainspace is mostly good but has a few problems, such as a few paragraphs written in a NPOV style. The community either corrects this via the talk page or project pages or if that doesn't happen...
    • the page is nominated for Deletion. The community recognise the page is worthy and either edit the offending paragraphs away.
    • Alternatively the page is submitted to AFC before mainspace. The gods roll a dice and the submitter is given a reviewer who rejects the article completly based on the NPOV paragraphs. The hapless submitter desperately tries to make changes, but then is told a second time that their isn't enough references by another reviewer. All the submitter wants to do is to get the page onto mainspace so it can be collaboratively edited by the community, but now the reviewers at AFC are demanding that he/she turn out a page that is not only notable and verifiable but is of high quality too!. Frustrated, she gives up and thus Wikipedia loses another potential editor.
    • I'm not saying this happens all the time, but even once is too much.Egaoblai (talk) 11:54, 4 December 2017 (UTC)
  • Some options are for complainants are to go in and review some pages. They could even go through the g13 candidates and rescue a few. When I go to delete these expired drafts, there is probably about 10% worthy of mainspace. I would also like a simpler way to accept a declined page, but we can always click on the move link and then cleanup. The final option is to review the reviewers who decline, or otherwise. Then talk to them or discuss at suitable venues. Even today I accepted an article that someone declined an article because it used primary research sources (not actually a real decline reason), when actually several of those sources were reviews. Graeme Bartlett (talk) 12:29, 4 December 2017 (UTC)
  • AfC reviewers need to be reminded that their job is to check for notability and verifiability only. If it is spammy or 'messy' it should only be declined if the problem is severe. Everything else should happen on the NPP side of things. I also see WAY too many articles that would pass NPP end up being declined at AfC because they are messy, formatted a little wrongly, or because the reviewer can't be bothered to do a 2 minute google search for the topic to check if it is notable independent of the sources in the draft (something we are required to do at NPP before taking it to AfD, etc.). Some of this stems from the opinion that AfC is a place to 'help out newbies'. this may have been the original intent, but it has failed spectacularly at this. I think it is time to recognise AfC for what it is: a gatekeeper for basic quality assurance. New Page Patrol fills a similar role, but not the same one. NPP has to be reactive, which puts a lot more pressure on reviewers to argue for deletion. This might be more 'collaborative' but it is also much more time consuming. A first pass by AfC for people who really have no idea what they are doing (i.e. new editors) stops attack pages, blatantly spammy stuff, etc from even being submitted by new users in the first place (most don't bother if they know it won't make it to mainspace without review).
    TL;DR: AFC need to simplify their workflow to just CSDable stuff, notability and verifiability. — Insertcleverphrasehere (or here) 17:54, 4 December 2017 (UTC)
  • WT:AFC has been notified of this thread. Primefac (talk) 15:24, 5 December 2017 (UTC)
  • And, Egaoblai, I shall expect that in future, when you undertake such massive actions, you have the basic courtesy of notifying involved projects et al in a seperate sub-section rather than sneaking them in...Winged Blades Godric 15:32, 5 December 2017 (UTC)
  • No. Just... no. And... before folks go criticizing a process and suggesting it be eliminated, it's probably beneficial to... get literally any experiences whatsoever in the process you're criticizing. GMGtalk 15:39, 5 December 2017 (UTC)
  • Echo GMG.As I once noted during NPR discussions, the most uninformed comments come from the least-experienced folks.And, I don't believe that someone with a net of 325 edits under the belt is an ideal user to reflect the community- a word that he/she frequently seeks to invoke/insert in his/her arguments over a lot of spheres at a lot many venues.I also see that there have been some attempts at metaphorization and hyperboles as a weapon of choice but most of them are typical BS like rolling a dice! Also, some folks apparently prefer that greeted with a deletion template is far more conducive to attracting editors than a decline at AfC and temds to think that AfDs almost always result in keeps!Winged Blades Godric 15:50, 5 December 2017 (UTC)
  • Weak neutral I've never found AFC particularly useful; in practice I have found many interactions I have observed between people who work there and the new editors who use it to be curt, bitey, and not at all helpful in directing new users towards improving their editing skills or in understanding Wikipedia's arcane rules, which is what it SHOULD be. I suppose if someone is finding it useful, that's fine. It's reason for existance, however, the reason it was created, was to improve the article creation process for new users, so their creations were not merely deleted outright. I'm not sure its all that successful in that direction. --Jayron32 15:53, 5 December 2017 (UTC)
  • Oppose. With no AfC I guess the suggestion includes to let everybody including IP's create articles directly. New page patrol may be handling the current load in reasonable time but would get a lot more to do if every IP could create an article in seconds. New articles are hidden from Google with noindex for 90 days but I'm not sure all complete junk creations would get a review in that time. And our own search function indexes all articles right away, and wikilinks to new articles also work. Many crap pages would be created by IP's clicking existing red links or quickly adding links to them. If there is concern about AfC reviewers having power to judge a page alone (a power admins already have to speedy delete articles but AfC reviewers may not be admins), then we could consider a system where AfC reviewers can request AfD-like community input on borderline cases. But it would be a waste of time to require community discussion for all pages. A lot of them are complete crap. There is a reason we have different processes CSD, prod, and AfD for mainspace articles. PrimeHunter (talk) 16:34, 5 December 2017 (UTC)
  • Oppose A couple of bad review(s|ers) does not mean we need to scrap AFC altogether. It's worth stating that AfC reviewers could sometimes be more helpful, but I assure you the vast majority are a lot more understanding and provide a gentler learning curve when compared to what a new editor would face when their article is dragged to AfD.. -- There'sNoTime (to explain) 16:35, 5 December 2017 (UTC)
  • Oppose note that a vote on the future of AfC was recently held and I fail to see how the arguments for deletion are any more advanced then they were in April. AfC is an important way for newcomers, those most likely to be deterred if their articles are tag bombed or immediately nominated for deletion to have a softer way they can seek feedback. Sure- some reviewers are bitey but still less so than if their article was immediately speedied. AfC offers good sound advice to those who reach out, and saying that some reviewers are unhelpful is not a damning indictment of the whole system. jcc (tea and biscuits) 17:42, 5 December 2017 (UTC)
  • Oppose I was originally going to sit this out, but as defacto head of the project I think I'm obligated to say something. Godric made a comment on a different talk page (in a related discussion) about how this proposal (and in particular some hyperbolic examples) fall within the Nirvana fallacy. Sure, we'd love to get the backlog down to a week (or maybe two). Sure, we'd love to be able to work one-on-one with every single editor who graces our doorstep. Sure, we'd love it if every reviewer was perfect and never made a mistake and could magically (and instantly!) tell if the subject is notable just by looking at two sentences and an IMDb reference. But that's not going to happen.
    • First point of contention (going off the example I linked above) - "new users don't get any feedback": we have a ton of resources for new users to ask questions. There's the IRC help line, the AFC Help Desk, the Help Desk itself, the Teahouse - all of which are linked on the decline notices. There are also of course the reviewers themselves. We had 55 reviewers do more than 10 reviews in the last month, and every single one of them answers questions on their talk page when a new user asks. Often there will be jaguars who will also comment on the situation, and people willing to contact WikiProjects to get more input (I personally have done all of the above multiple times in the last few weeks). Sure, they don't get access to every Wikipedian, but I've noticed over the years that the ones who ask questions are the most likely users to actually get their drafts approved, and the ones who refuse to listen to the advice given to them end up with a draft at MFD or themselves blocked for violating our TOS. Coincidence? I think not.
    • Second point of contention, per TNT's comment preceding mine: just because we have a handful of bad review(s|ers) does not mean the process is bad. I removed someone from the project two days ago because multiple people expressed concern about their reviewing capabilities. This is how feedback is supposed to work - you let people know there are issues and they get fixed. If someone sees a bad decline, tell someone (or just move it to the article space). If you see a bad acceptance, kick it back to draft. If someone is seeing a systemic issue with a reviewer (or the process itself), we need to know. There's no point in shutting down the factory simply because a light bulb needs replacing; I don't think we should go through the "shut AFC down" rigmarole every time someone screws up a review. We know there are issues (big and small), but hand-waving and (dare I say it) blowing hot air will not solve things.
      Could AFC be improved? Absolutely! There are things I see regularly that need discussing (or are discussed) which lead to a better understanding of how we should be handling the Project and dealing with new users. In the past that wasn't so great, but we've developed a core of really fantastic reviewers who are interested in collaborating and are willing to throw out crazy ideas to see what works. Our backlog has jumped mainly due to ACTRIAL, but I hope that in the next month or so (after the glut of student-project-garbage dies down) we'll be able to start cutting into that and getting it back to more manageable levels.
      I genuinely, honestly, truthfully want to hear constructive feedback on how we can improve the process, because if it's a good suggestion I'll spend less time writing diatribes like this and more time reviewing drafts. If you don't want to post it at WT:AFC or WT:AFCP, post it on my talk page or shoot me an email. We might not always agree, but I will do my best to be amenable to the suggestions. There are some things that are near-impossible to correct (how do we get more reviewers, or get the existing ones reviewing more? No one knows) but even small tweaks can be a net positive.
      Also, for anyone interested, I have been keeping detailed statistics of the review process for quite a while, and I'm happy to discuss them (in a separate venue). Primefac (talk) 17:51, 5 December 2017 (UTC)
  • Comment - There has been scope creep at AfC. It started out as a more friendly place for new editors to submit their first article. It has now become a gauntlet. It now differs from NPP in that nips at new users straight away instead of taking a huge chomp at some random point months after submission. There is a strong pushback at NPP and AfC against low-quality submissions. The Wikipedia that Uanfala supposes in proposing to abolish AfC is not the Wikipedia that currently exists (at least not from a new articles perspective). I'm neutral about abolishing AfC but either way this goes, the community is going to continue to reject partially developed new material. ~Kvng (talk) 18:08, 5 December 2017 (UTC)

Break 1

  • Oppose. I have never used AFC and never will. I know how to write an article to fit policy. But I didn't learn the policies overnight. I spent many months reading and learning from other peoples' work and mistakes what to do and not to do. The nom does not do a good job of explaining why we should abolish AFC. Yeah, if poor editors run it we will get bad results. But AfC is set up to aid the clueless (no offense) new editors who wish to write an article. L3X1 (distænt write) 18:20, 5 December 2017 (UTC)
  • Comment I wish there was a link between AfC and Teahouse (or some other space where you could go for coaching). I might be naive but I think many new editors who wind up at AfC are super motivated to do something that they imagine is a great contribution but know nothing about policies and the basics of what makes a good article. The current AfC process bludgeons them with templates (which point to policies, incomprehensible if you are new) and encourage them to ask questions on the AfC reviewers talk page (YMMV and also I don't think new editors even understand what that means). I think it we walked through this process with an actual new editor we would get some insights into the pitfalls (a big, new task I understand, but I'm a huge fan of user studies). I do appreciate that this could be a useful service and obvious more volunteers are needed for this type of work since the workload seems like it is pretty crushing at the moment. I think we should reimagine AfC as a force for possible good where new editors are encouraged to do better work, not chased off. Right now it seems like a place of "no". Merrilee (talk) 21:32, 5 December 2017 (UTC)
Agree. From what I have heard, AfC needs improving not removal. L3X1 (distænt write) 22:10, 5 December 2017 (UTC)
The AFC helper script has a default option to invite authors to the teahouse so the requested link already existed. AFC is structurally sound. I just think some reviewers have strayed a bit (perhaps due to pressure of a mounting backlog) and are behaving more like NPP patrollers than teahouse helpers. ~Kvng (talk) 18:47, 6 December 2017 (UTC)
  • support AfC is failing - 2 months for a review is too long, new editors cant be expected to wait that long and most dont. The "reviews" arent helpful when they finally occur because rather encourage a contributor they just throw a lot of technical terms generally as abbreviations at them and walk away. "NPP is backlogged at 13k", AfC at 2500 and teahouse says they should be sending people there and there is the technical pending changes options. What I see is divided resources doing the same task in different ways, saying just give us more contributors isnt a solution when the process is itself driving new contributors away. The first step is too look at what aspects are working, AfC working aspects are those which are already being done by NPP & Teahouse which makes AfC redundant. Gnangarra 23:57, 5 December 2017 (UTC)
User:Gnangarra If you think two months is too long, the place to fix that is here. And given that you don't appear to have ever made a single edit to the Teahouse, for convenience that's here. GMGtalk 00:41, 6 December 2017 (UTC)
I don't see what the Teahouse has to do with this, its an alternative/new editor Help Desk, not the AFC complain desk, right? L3X1 (distænt write) 01:55, 6 December 2017 (UTC)
I don't have the faintest of ideas about how AFC, pending changes and Teahouse--the trio of them can be seemed by someone to be doing the same task!Winged Blades Godric 03:45, 6 December 2017 (UTC)
Ngatti-ngatti-ngatti if you truly think I dont have the faintest idea about AfC and successfully creating community building projects then nows your chance to correct it. Gnangarra 06:08, 6 December 2017 (UTC)
And you need to look carefully at what I wrote....I wrote I don't have....Don't confuse pronouns and then misplace words in my mouth.Cheers!Winged Blades Godric 06:15, 6 December 2017 (UTC)
Sure. I'll bite (no pun intended). I definitely suspect that you don't understand how AfC works. Saying that AfC throws acronyms in user's faces and walks away is a pretty clear way of saying you haven't used the helper script either at all, or for long enough that you don't remember how it works, and pretty certainly that you haven't frequented the AfC helpdesk (or the teahouse, or the help desk), to answer any questions, or answered any questions at your talk page from AfC contributors for whom a link to your talk page is always provided, or for that matter responding at the IRC help channel, for which a link is too always provided. These are things that our regular AfC contributors actually do and it's part of the reason the entire process is so time consuming.
Pointing to NPP, backlogged as it is at three or four times the magnitude of AfC, as the solution that works, and why we don't need AfC, flatly makes no sense. It certainly doesn't reach the level of depth of addressing time-consuming borderline judgement calls that hamstring both projects, and the lack of volunteers that both projects suffer from.
Saying that the teahouse replaces AfC is just silly, not least of which because the teahouse is one of around a half dozen helping forums, is a general purpose forum for new users, and there already exists a specific help forum for AfC. Saying that pending changes somehow helps to replace AfC makes about as much sense as saying rollback does. Both are anti-vandalism tools and have basically nothing whatsoever to do with the creation of new articles.
So to recap, as I said above, if you want to criticize a project, or call for its elimination, it helps to have literally any experience whatsoever contributing to that project. GMGtalk 12:08, 6 December 2017 (UTC)
I feel that the brilliant comment/perspective that AfC ≈ Pending changes ought to be rewarded suitably.But sadly anything in the likes of WP:COMMENT OF THE MONTH is a red-link.Winged Blades Godric 16:18, 6 December 2017 (UTC)
  • Comment Where is the mechanism for the community to disagree or dispute AFC calls? I thought about going to "help" but the time stamp seems overly complicated and I'm not sure if it's only meant for the writer rather than concerned bystanders like myself. The current system pits the submitter against the reviewer, but what about people who wish to object? I was just looking through the teahouse and found a plea from an new submitter (actually there are many in the same boat) who has created an article with a stack of references to independent publications that are about the subject and is being told by the reviewer that the submission Draft:Anuraag_Saxena doesn't pass because:
"This submission does not appear to be written in the formal tone expected of an encyclopedia article. Entries should be written from a neutral point of view, and should refer to a range of independent, reliable, published sources. Please rewrite your submission in a more encyclopedic format. Please make sure to avoid peacock terms that promote the subject."
This is ludicrous and the reviewer seems to be treating AFC as if it was some kind of classroom for producing perfect articles! Is there really a rule for FC that articles must be in the right tone or completely NPOV? These things can be dealt with by the Wiki community. I am grateful to the above reviewers who commented that they pass articles on AFC for notability and verifiability, but it's clear that others aren't doing this. Tagging Majora Graeme_Bartlett Winged_Blades_of_Godric, as they commented earlier about this issue in AFC. Egaoblai (talk) 12:56, 6 December 2017 (UTC)
Ok. Well. Looking at the teahouse currently, I'm seeing three threads dealing with declined AfC drafts. There's this thread where the article was apparently such blatant advertising that it was speedily deleted WP:G11. There's this thread by a fairly obvious WP:COI user who has been given a username block, and related to Draft:Shen Wai International School, which I have now nominated for speedy deletion as WP:G12 because it was directly copied and pasted from the official website. Then there's this thread, which was already asked and answered at the AfC helpdesk, related to Draft:Amitagarwal3000, which consists of three youtube links, a track listing, and it probably blatantly advertorial besides.
Regarding Draft:Anuraag Saxena, the user did ask at the teahouse, and was given very detailed advice on how to improve the draft, which they have been actively working on since. In other words, exactly how the process is supposed to work.
To answer your question, yes, there is a requirement that articles be appropriate in tone, which can be found at Wikipedia:WikiProject Articles for creation/Reviewing instructions. GMGtalk 13:31, 6 December 2017 (UTC)
The rules for AfC, Egaoblai, can be found here Wikipedia:WikiProject Articles for creation/Reviewing instructions#Main task. They do indeed say that the only thing people should be looking at is whether or not it is reasonable to believe that it would survive AfD. Again, BLPs have an extra layer of scrutiny because they have to but if people are going far beyond that then you should bring it up to them or ask for additional assistance from someone else. --Majora (talk) 02:49, 7 December 2017 (UTC)
Hi Majora thanks for the response, however, GreenMeansGo says that tone is a requirement, which would seem to contradict the idea that survival of AFD is the "only thing". Personally I think the survive AFd rule is the best one, as it means that pages of poor quality but which are notable can be worked on by the community.
As for "people going too far" is there a mechanism for this when it comes to rejected drafts, a public mechanism apart from using their talk page? Egaoblai (talk) 02:58, 7 December 2017 (UTC)
Well tone does matter to the point that if it is speedable under G11 then it certainly wouldn't survive AfD. In that regards, yes, tone does matter a great deal and a lot of AfC submissions are by COI editors who can't tell the difference between an advertisement and an encyclopedia article. There are a few avenues for assistance. You can ask at the project's help desk. You can ask at the normal help desk. You can even ask at the help channel on IRC. Obviously I would ask the reviewer first. But if you aren't getting anywhere with them and you truly believe that there was a mistake in reviewing there are alternative avenues. --Majora (talk) 03:02, 7 December 2017 (UTC)
Being eligible for G11 is not the criteria listed at the instructions. The criteria listed at the instructions is that the article be written from a neutral point of view. GMGtalk 10:59, 7 December 2017 (UTC)
The main criteria is and always has been whether or not it would survive AfD. If you brought an otherwise good article to AfD for NPOV issues you'd be shot down so quickly due to a WP:BEFORE violation. It even says right on that page, The argument "non-neutral point of view" (violates WP:NPOV) is often used, but often such articles can be salvaged, so this is not a very strong reason for deletion either. If you are rejecting things simply because of NPOV that does not rise to the level of advertising then you are not doing your job at AfC. Simple fact. --Majora (talk) 00:44, 9 December 2017 (UTC)
Thanks for the response. It seems like those requirements are part of the reason for the problems then. Egaoblai (talk) 13:40, 6 December 2017 (UTC)
Unfortunately, those requirement are necessary, because a very large portion of the drafts that get submitted to AfC are from editors with conflicts of interest, and many are written in a way where they would need to be mostly or entirely rewritten to comply with our policies on neutrality and promotionalism. There are already 21,000 published articles that have been tagged as promotional, and have yet to be fixed, in a backlog going back almost ten years. That's exactly why AfC does not accept these types of articles on the ground that the community can fix them, because the community is already struggling to fix the ones we already have. GMGtalk 13:50, 6 December 2017 (UTC)
On a practical note, if you see a declined submission that shouldn't have been declined, then you can simply move it into the mainspace, remove the AfC fluff, and then inform the creator that it has been accepted. There's no need to try establishing consensus with previous reviewers. – Uanfala (talk) 13:51, 6 December 2017 (UTC)
If any AFC reviewer had moved Anurag Saxena to main-space, that would have been most likely the end of his journey as a reviewer.And if such blunders are repeated by any non-AFC user using the move-tool followed by manual cleanups, I could fairly forecast a topic ban from moving other's drafts etc. to mainspace.And, if you aren't arguing for the sake of arguing, that is an outright G11 candidate.Also, since from our prev. Comments, you managed to think, that we three would accept it, I would assume that you don't have any idea about what CSDable stuff means.Winged Blades Godric 17:08, 6 December 2017 (UTC)
I believe there are adequate checks on reviewer behavior. If an author wants to challenge a decline, he may resubmit the draft and it is AFC policy for a different reviewer to look at it the second time. We have other reviewers monitoring abandoned drafts looking for ones that may have been declined inappropriately. In my opinion, it would be better if promising drafts got to mainspace earlier but many reviewers are disinclined to approve lower quality drafts either because their own standards are higher than the AFC minimum or because they fear reprisals from other reviewers with higher standards. ~Kvng (talk) 18:56, 6 December 2017 (UTC)
Seems like a great idea to monitor abandoned drafts (is there any tool to find these?), although it's bittersweet as it doesn't solve the problem of editor retention and why people are abandoning those drafts. Egaoblai (talk) 01:33, 7 December 2017 (UTC)
@Egaoblai: We have Category:AfC_postponed_G13 ~Kvng (talk) 19:41, 7 December 2017 (UTC)
  • I recently found this research report: "Accept, decline, postpone: How newcomer productivity is reduced in English Wikipedia by pre-publication review" http://jodischneider.com/pubs/opensym2014.pdf and It makes for interesting reading if anyone hasn't read it yet. Essentially they identify some of the same problems people in this discussion have made about AFC; it's not collaborative, it chases away newcomers, etc and has some recommendations for newcomers. Since I started this conversation, I'm inclined not to support removing AFC as it's clear that many benefit from it and a lot of reviewers are doing great work, but I do think it's clear that it needs an overhaul.Egaoblai (talk) 08:10, 9 December 2017 (UTC)
  • Suggestion: Instead of reviewing the article once a lot of editor time has been spent on it, what about a two-phase process for AFC that could help serve as a mentoring process and a softer gate for good faith editors (teach them how and why to fish edit and all that)... and provide an easier job for reviewers, particularly in the case of conflicted editors (a few sentences with a few references can be easier to assess than a very weak long article with citation overkill)?
  1. The editor writes a dotpoint statement of claims against standards of notability, along with sources that support each claim. This is assessed against WP:GNG, WP:SNG, WP:RS, etc.
  2. Once claims and sources are solid, the editor turns this into at an acceptable stub (ideally with formatting, content expansion, references, cats, stubsorts, wikiprojects, ...) that avoids the need for further edits at NPP, and/or is provided with alternative options/guidance along the lines of WP:ATD.
Ultimately, if an editor at AFC really wants their article moved to mainspace despite deficiencies (eg: through repeated resubmission) despite assessment that it doesn't meet WP:CCS/W:N/WP:V, then (after having warned them) perhaps just do so but immediately initiate deletion unless there's a clear violation. ~Hydronium~Hydroxide~(Talk)~ 10:17, 9 December 2017 (UTC)
@Graeme Bartlett: Thats already being done, especially with the rule about translations. The whole reason some people want to be a wikipedias is to contribute their bilingual knowledge only to be turned off by the fact you must have 500 edits and have to be an extended confirmed user of 30 days. YuriGagrin12 (talk) 14:58, 10 December 2017 (UTC)
  • AfC is slow, bitey, very non-welcoming for the newcomer. I see it a lot with drafts sent to MfD (admittedly biased to the bad side), and with real-world acquaintances who came to the project with enthusiasm and were met with ... nothing. For the newcomers, AfC is a separate space of seclusion, and the reviews are pedagogy. Newcomers include professional mature people, and they are treated like children. It's not beyond fixing, and good stuff comes out of it, although I am not sure of the numbers. WP:ACTRIAL is great at stopping people with absolutely no idea from creating new (unwatched, orphan) pages, it should cover draftspace as well. Newcomers should get involved with existing pages, alongside editing editor, before jumping into writing their first page on their pet topic, at least for 10 edits and four days. It is very rare that a new topic, with no mention already existing in mainspace to be improved, needs to be written right now. Current affairs topics may be an exception, but experienced editors will create the new page within minutes. Wikipedia's principles ("Wikipedia is free content that anyone can use, edit, and distribute"; & WP:SOP #2 "Newcomers are always to be welcomed"; #3 "You can edit this page right now" is a core guiding check on everything that we do. We must respect this principle as sacred") do not imply that newcomers (< 10 edits, < 4 days) need to be able to create new articles. --SmokeyJoe (talk) 22:27, 10 December 2017 (UTC)
  • OK. I have an idea: encourage and make it easy for new users to add wikiproject templates to draft talk pages. At the moment, people in this conversation are generally taking issue with two things: 1) the few editors that are not doing a good job reviewing, and 2) the lack of 'collaboration' on AfC drafts. The first one is unavoidable to some extent, but can be addressed by reviewers talking to others if they think they have made a dodgy call. However, my proposal can largely help to deal with the second one. We need to make it easy for newbies to add wikiprojects to drafts so that users from those wikiprojects can view and help out with those draft articles. The submission template notice should prompt users to add wikiprojects to get more eyes on their drafts, and also have a box that you can type in that autofills wikiprojects and a big button that says "Add Wikiproject" (similar to how AFCH and the Rater tool do it). Adding wikiprojects via this box should add the relevant template to the talk page (rated as draft class), which will give a heads up to various wikiprojects that there are draft articles in their topic area that need review. The technical issue of how to modify the {{sumbit}} template is up to somebody more skilled than I, but if I get some support for this idea, I'll ask over at VPT. — Insertcleverphrasehere (or here) 00:19, 11 December 2017 (UTC)

Break 2

  • Oppose - for now. Very legitimate arguments from SmokeyJoe (although some professional mature people do behave like children - my talk page is full of them). I, for one, can think of several reasons why Wikipedia would be better off without AfC. However, ACTRIAL when Scott, Blade, and I first campaigned for it many years ago, was centred around the very fact that those who are not autoconfirmed would be forced through the Wizard and AfC and hence still have an opportunity to create an article - of sorts. This was the only way we could get consensus for it in the face of a nevertheless strong ideological contingent who religiously believe that Wikipedia was created so that every troll and spammer can tinker with it - a mantra based view that is so erroneously supported by, for example, relatively new user Force Radical who has as yet very little experience in these matters (I hasten to add however, whose initiatives in other areas are most welcome).
    Despite the amount of new content that comes through AfC, I have yet to be convinced that the number of approved new pages contains strictly necessary encyclopedic articles. Most of those drafts could be processed by a better performing NPP/NPR which is less personal, less bitey, and could be better if the reviewers would use the messaging feature that we provided them with in the Curation Toolbar, which could also easily have all the features of the AfC Helper Script added to it.
    To have a blanket ban on all non autoconfirmed creations to include drafts is of course therefore highly desirable, but it would need some very powerful and convincing arguments for it, and a backlog at AfC is not one of them.
    On a final note, this thread has been begun by the OP, another relatively new user (152 mainspace edits) ostensibly on the basis of their failure to understand our notability guidelines as illustrated at this AfD, and their draft that was declined here. Anyone wishing to discuss AfC vs NPP is recommended to see the dedicated project at WP:NPPAFC. Kudpung กุดผึ้ง (talk) 00:44, 11 December 2017 (UTC)
    • Hah! Absolutely do mature professionals sometimes behave childishly, and when they do, they are far more obstinate and persistent than any child. --SmokeyJoe (talk) 01:30, 11 December 2017 (UTC)
      • Hi Kudpung กุดผึ้ง thank you for your comments. You are right to say that there are some legitimate arguments here and I will do my best to summarise them. In retrospect, it was a mistake to advocate for dissolution of AFC of the bat, as it's clear that many feel it's useful and I have, due to a few recent experiences, over estimated the amount of poor reviewers. it's clear that a lot of people are giving time to work on the project and they should not be swept under the rug. On the other hand, I think my relative newness here can be an asset, as I can provide an insight into the mind of new editors. Firstly, it's really difficult to search for help on how to make a new article here, there seems to be a million pages, and often you find a page that you think might be the answer, but instead it turns out to be a meta page about the subject. Another thing is that the AFC process is offically an option, but the majority of new users working on drafts would never realise this, thinking it is mandatory. I think that not every new editor wants to make a perfect page from the outset; some are exciting about the prospect of working with others, but the AFC process can be overly adversarial, and essentially corrals a page in a single users domain. I've been doing a little bit of help in AFC with some new articles that are noteworthy but poorly written, for example, Draft:Saubhagya_Scheme, but the vast majority of rejected drafts languish and then are quietly deleted through g13 (sometimes indiscriminately). AFC is clearly needed for a lot of submissions, but there's a lot of good faith editors who have made a page that would never get deleted by AFD that are being held up in purgatory. I would love to help discusson WP:NPPAFC and have been looking through it recently. As for Draft:Aung Soe Min, That was quite a while ago and my first attempt at editing. Since then, I've read a bit more and as you can see have created around 4/5 new pages that have been reviewed. I hope you won't hold that first attempt against me!
        I'd be interested to know if there was a way that users could view recently declined submissions to AFC, that way users who wanted to help drafters could look through declined drafts to see if there was anything that they could help with (a personal area of expertise for example). Is there a page for this or a bot? Thank you for your comments.Egaoblai (talk) 05:22, 11 December 2017 (UTC)
        • Just a couple of points , Egaoblai: It is absolutely not difficult to find help and advice - the Wikipedia is awash with it. It might be more accurate if you were to say there is in fact too much of it. I do think however that the welcome template (without the thanks for the edits) should be automatically placed on the talk page of every newly registered user - but I digress. Admins are highly experienced editors, they rarely do anything indiscriminate; I have deleted hundreds of G13 and almost without exception they were all from people who breezed by, dumped something totally substandard and/or inappropriate on us and then cleared of with no intention of returning- we are not here to repair things thrown at us through our shop window by passers by, and very often the best thing we can do is throw it back. There is no proof that I know of, that suggests the majority of new users working on drafts think AfC is mandatory; there's nothing that tells them they must but if they do, then we have tacitly achieved what must surely be the best result Kudpung กุดผึ้ง (talk) 23:50, 11 December 2017 (UTC)
          • Kudpung กุดผึ้ง thanks again. I definitely think that quite a lot of users do think AFC is mandatory, especially when they have made a new account, that means they must go through the article wizard. This is from my own experience and other people I know (primary research for sure). I don't know what the split is, but looking through deletions and rejections there is roughly three groups of people 1) Those who don't read any guidelines and just write totally inappropriate drafts. 2) Those who write about notable stuff, but haven't really understood how to make a page. 3)those who have read about guidelines and have written about notable stuff, but for small reasons their draft isn't being passed. (4) those who pass. I think we need to focus on 2 and 3 and find a way to bring them into the fold more, like cross linking drafts to wikiprojects for instance, or letting no.3 editors know they can submit directly to mainspace (and potentially face AFD rather than AFC if they will).Egaoblai (talk) 00:19, 12 December 2017 (UTC)
            • Your characterisations of the 4 groups are probably not without merit. I would need to see some firm statidstics to support your conclusions, as I think you probably haven't been working in these areas long enough (e.g. hundreds or even thousands of reviews) to gather any substantial empirical evidence. I'm not saying you're wrong, but the longer you stay on Wikipedia, the sooner you'll notice that our community has a hunger for stats and generally refuses to do anything without them. Again, as I said above: There is no proof that I know of, that suggests the majority of new users working on drafts think AfC is mandatory; there's nothing that tells them they must, but if they do, then we have tacitly achieved what must surely be the best result. Kudpung กุดผึ้ง (talk) 02:05, 12 December 2017 (UTC)
              • I've heard, from more than one new editor, that they believed AFC was mandatory, or very close to mandatory, including editors from other wikis, who ought to know better.
                Egaoblai, you might be interested in some of the old discussions on this same question, such as this one. Even editors who have made tens of thousands of edits have wondered exactly what you're asking here. WhatamIdoing (talk) 00:31, 14 December 2017 (UTC)
    • Yeah I was going to comment on that. AfC is part of why people were fine with ACTRIAL. Galobtter (pingó mió) 08:13, 13 December 2017 (UTC)
      • I think more than a backlog at AfC, discouraging people by making them wait/ having their drafts 9/10 times declined is the real problem, and I think raising the bar for submitting drafts but keeping AfC as a help area for potential article could be useful, as it would prevent the discouragement of people who create a draft as their first edit. But then again, some people really want to create an article, and being able to create a draft could prevent discouragement.... Galobtter (pingó mió) 08:25, 13 December 2017 (UTC)
  • Oppose -- AFC works just fine; it could use more volunteers though. K.e.coffman (talk) 04:02, 12 December 2017 (UTC)
  • oppose per K.e.coffman. It helps keep the speedily deletable out of the main space. The trouble is we need more reviewers to bring the viable articles into the main space. -- Dlohcierekim (talk) 21:54, 12 December 2017 (UTC)
  • Oppose I have many concerns with AfC and find that the current culture of the project is something that I do not find enjoyable to work in at all: it treats the good faith new editors poorly because of bad formatting or because they want to write on notable topics that occurred over a century ago. Instead the users who are most likely to actually get help are the very users we want most to get rid of: the spammers. They are motivated to ask questions of the AfC reviewers and interact with them, and because of this are the ones who get the most assistance from us. These are both serious issues that AfC needs to address, but they are not a reason to get rid of the project at this point. TonyBallioni (talk) 00:16, 14 December 2017 (UTC)
  • Support Afc really takes to long for articles to be created. How about we just move it into the Article space as long as your a registered auto-confirmed user. There are just too many errors at this point, but we could do something like the articles for review are automatically moved onto the article space and Afc decides 2 weeks later to keep it or not. Also why is the translations restricted to extended confirmed users, I want to contribute but can't. YuriGagrin12 (talk) 23:15, 14 December 2017 (UTC)

Fixing AfC

So, given the issues acknowledged above, and others, how can AfC be improved? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:38, 14 December 2017 (UTC)

*Tumbleweed*. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:13, 20 December 2017 (UTC)
see the discussion below here Pigsonthewing — Preceding unsigned comment added by Egaoblai (talk • contribs) 23:41, 21 December 2017 (UTC)
I moved that discussion into this section. But I'm not seeing much in the way of viable proposals for fixing AfC. I think part of the problem might stem from new reviewers being told that "the best AfC reviewers only accept 1 in 50 articles". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:23, 27 December 2017 (UTC)

AFC discussion summaries and moving forward

Thank you everyone who participated in the discussion, I have done my best to summarise, please let me know if I have missed something out. We can see there were a number of recurring themese

1. AFC reviewers being too strict

Majora identified that GNG and notability guidelines should be the target for reviewers, Insertcleverphrasehere also commented that “AfC reviewers need to be reminded that their job is to check for notability and verifiability only.” They also wrote that they see a huge number of articles declined at AFC that would pass NPP, and AFC reviewers are declining stuff for formatting reasons or are not thoroughly checking for notability and are asuming something isn't notable without checking. A simplified workflow is suggested. Kvng also says that there has been scope creep at AFC from some reviewers. Drewmutt commented that some reviewers were rejected things for “reference errors” or “too short”, things that were easy to fix and not necessarily reasons to decline. Graeme Bartlett also wondered if AFC was too strict now, noting that articles that would have been accepted in the past would not be today. Galobtter noted that some reviewers in AFC had called for relaxed rules.

Egaoblai and WhatamIdoing noted that many new editors believed AFC to be mandatory, even though it is an option. The article wizard makes no clear mention of the optional status of AFC

However there was a disagreement on interpretation of the rules: GMG suggested that issues such as tone and NPOV were relevant to AFC and as such, reviewers should not accept articles that had issues with these factors, however Majora commented that the main factor for accepting AFC drafts is whether it passes a “AFD test”, and issues such as npov or tone were not required to be accepted as part of the reviewing process. Other users commented that they did review at AFC according to basic principles but commented that other users might not. Hydronium Hydroxide suggested that editors make a statement of claims to notability, etc before writing the article.

WhatamIdoing mentioned that rejecting an article could lead to being hidden in draftspace, to be “quietly deleted” later on, referring to g13 CSD. Graeme Bartlett mentions the G13 too, noting that around 10% of the draft articles waiting to be deleted are worthy of mainspace.

2. AFC unwelcoming and BITEY

Andrew_Davidson, who is involved in editathons, says the AFC system is slow and too negative: “It’s about finding reasons to say no”. Suggests letting NPP deal with bad articles. SpartaN also echoed these comments, about letting articles stand on their own. Jayron32 also said they found the reviewers there bitey and “not at all helpful” to new users. There'sNoTime opposed abolishing AFC, but noted that the reviewers could be more helpful. Kvng suggests the AFc has become like a gauntlet rather than a friendly place. Merrilee said that the AFC process and the insider Wikipedia lingo and policies could appear overwhelming to new users who were eager to contribute and new users were “chased off”. Gnangarra voiced similar opinions on the reviewing system, stating that it isn’t helpful. SmokeyJoe also commented that AFC is slow and bitey and that from personal experience, new users with enthusiasm were being turned away Galobtter also noted that the backlog might be discouraging people too. TonyBallioni comments that good faith editors who choose more obscure but notable topics are treated poorly by the review process. Egaoblai noted that AFC didn’t encourage collaboration, which was a principle of Wikipedia. SmokeyJoe said that AFC was a “space of seclusion”.

3. AFC useful as a quality filter

TonyBallioni said that the reason for ACTRRIAL is because articles from new users aren’t good. Insertcleverphrasehere suggests the true role of AFC is or should be a gatekeeper for basic quality to prevent obvious spam, etc. L3X1 also says AFC is to help those who need it. Uanfala said that AFC should remain for at least users that want their article to be evaluated. Dodger67 pointed out that AFC helps people create articles and givers them suggestions to improve. Jcc and Primefac also said that reviewers on AFC offer good advice and that there are only a few problematic reviewers, not a structural fault with the system. Primefac also says that problematic reviewers should be notified or reported. Winged_Blades_of_Godric suggests that AFC is less bitey than AFD and it’s deletion template. JCC expressed similar thoughts, asserting that tag bombing on new articles would be more deterring for newcomers. PrimeHunter notes that if AFC was abolished than there would be a glut of poor articles. They suggest a system of community review if reviewers are concerned about reviewers at AFC being solely responsible. Dlohcierekim notes that AC keeps a lot of speedily deleteable articles out of mainspace. Kudpung also notes that there is a high number of poor quality articles that are abandoned and need to be cleaned. Primefac notes that there is a lot of places for new editors to find help on Wikipedia and if they ask for advice, they will usually find themselves succeeding.

Some suggestions made

YuriGagrin12 suggests articles for review are automatically moved into mainspace and AFC decided whether to keep them or not.

Hydronium Hydroxide suggested that editors make a statement of claims to notability, etc before writing the article,

Insertcleverphrasehere here suggested making it easier for reviewers to add wikiprojects templates to drafts. Which would help with the lack of collaboration issue.

Summarizing

A tentative summary of the discussion might conclude that AFC is a needed place for new editors to get help and for quality control. However, a proportion of new editors who are attempting to contribute notable articles in good faith are being turned off by reviewing from some editors that is overly strict and unhelpful.

Regarding the second point, the implications are serious when we consider that both potentially great articles (for example a short article that passes AFC and then is later worked on by the community) and great contributors may be put off wikipedia by the process.

Moving forward, Please comment with your suggestions for improving this process, either by adding new rules/guidelines, or by removing existing ones.Egaoblai (talk) 08:35, 18 December 2017 (UTC)

  • I thing AFC talk-page would be the optimum venue for these conversations.Winged BladesGodric 15:39, 18 December 2017 (UTC)
    • The AFC page has already been notified, so in the interests of getting as many people discussing as possible, this seems the best place at the moment. We could move there later if some proposals take off.Egaoblai (talk) 17:20, 18 December 2017 (UTC)
  • How about the creation of a non-binding notice board where one could get second opinions from other editors abotu whether someone is notable? Basically have the AFD before the article is written. Call it WP:DeletionInsuranceNoticeBoard or something. L3X1 (distænt write) 17:40, 18 December 2017 (UTC)
    • I built a rough one at User:L3X1/WP:NoteBoard L3X1 (distænt write) 18:01, 18 December 2017 (UTC)
      • Any solution that involves multiplying the labor intensiveness that AfC already suffers many fold, it unlikely to be a successful solution. GMGtalk 18:10, 18 December 2017 (UTC)
        • I know throwing warm bodies is not the best solution, but it happens already at AFD. Dozens of editors are willing to (unless they are just there to plump their AFD log and look good at RFA) show up to discuss sourcing and notability issues, so why not do authors a favor and save the labor and grief spent writing an article on a borderline notable subject? If the research and time spent could be used in advance to help new editors and each other wouldn't it be a benefit. Regarding the MOS issues, I know that as I am willing to do TNT nukings (which actually takes some skill) I wouldn't mind doing minor fixes on a few articles. (not as much as the Guild of Copy Editors do, not like that) As for the bureaucracy element, that is why I suggest it be nonbinding. The author is under obligation to follow the advice presented, and in return, the now forewarned noticeboard stalkers would be under no obligation to not nominate the article for deletion. As for the Teahouse being the place to ask, I have done it once or twice, have never seen anyone else do it in all seriousness (though I am not dedicated teahouse host nor am I omniscient) and I kinda get the feeling that 20 or 30 notability queries daily would be considered disruptive and would clog it up. L3X1 (distænt write) 19:56, 18 December 2017 (UTC)
          • The teahouse often has a response time measured in seconds, and rarely measured in hours. Throwing warm bodies into the process has to happen eventually. ACTRIAL largely shifted the burden to AfC, and there's nowhere else I can see off hand to shift the burden further. At some point, if we want comprehensive review of content before it hits mainspace, especially as it concerns very new editors and editors with conflicts of interest, you're going need people to uphold that standard. Just because no one has any bright ideas to actually increase the number of people reviewing, doesn't mean doing so isn't the obvious solution. We have less than 200 people reviewing, and nearly by definition, these are the types of editors who are also going to be involved in a whole slew of other maintenance tasks, and not limited only to reviewing drafts. Obviously folks are open to areas for improvement, but I don't hold out hope that there's some low hanging magic bullet so far overlooked that's going to be suddenly revealed. GMGtalk 20:15, 18 December 2017 (UTC)
            • ACTRIAL hasn't shifted the burden to AfC. 80% of submissions by new users used to be deleted, most of these are simply not being submitted, as new users now know that their advert/trolling submissions won't make it to mainspace immediately, which removes any impetus to submit them at all. Look at the historical backlog data for AfC, and you will see a saw tooth pattern of raising backlog followed by steep drops driven by a few dedicated editors. The rate at which the backlog is raising is not any higher than other times before ACTRIAL (in fact in the month after ACTRIAL began their backlog was steady). Rather, it is because there has not been any large push to reduce the backlog as there has been by a few very dedicated editors in the past (for example in April and July). There was one push in November, but it doesn't seem to have done enough to last more than a few weeks. Perhaps it is simply time to bring back backlog drives? We are doing one over at NPP in January, which I hope will allow us to finally reduce our backlog back down to a manageable level below the index point. — Insertcleverphrasehere (or here) 00:25, 19 December 2017 (UTC)
              • Just a note that that tool has historically been completely broken due to a technical limitation on counting articles in very large categories (T18036). For that reason you should not use it for historical context as it is very inaccurate. It has since been fixed. --Majora (talk) 00:29, 19 December 2017 (UTC)
                When did this switchover happen? I can put a vertical line in the graph and a note.
                Actually, I have an idea - I can just count the rows in WP:AFC/S for historical data. I think that might improve the accuracy. Enterprisey (talk!) 04:56, 22 December 2017 (UTC)
                @Enterprisey: The bug still exists in the category counting. The WMF probably isn't going to fix it anytime soon as it is quite low on their to-do list. I thought you changed it over to count the individual categories. That is what the standard AfC backlog box uses now. Primefac and I let you know about the issue with your tool on IRC in November and I remember you saying that you fixed the issue. Perhaps I missed something? --Majora (talk) 03:55, 23 December 2017 (UTC)
    • This is just duplicating the other places someone can ask e.g. the Teahouse and the AfC help desk. jcc (tea and biscuits) 18:31, 18 December 2017 (UTC)
    • I think this in the right area of thinking, (making AFC more of a collab then simply editor against reviewer). But it would also add another layer of bureaucracy. Regarding Teahouse and AFC help, one thing I've noticed is that many editors come asking for definitive answers: "What do I need to add to pass the review?" "If I add this, will it pass?" and never get a clear answer. I think if people on those help pages could be encouraged to say "if you add X and Y, then I'll accept it for you, no need to resubmit" rather than saying "go to WP:GNG and read that and resubmit" it could make things smoother and more community focused. I've seen this happen a few times.Egaoblai (talk) 19:09, 18 December 2017 (UTC)
    • L3X1, there was Wikipedia:Notability/Noticeboard, which was declared "inactive" due to very low participation there. George Ho (talk) 23:33, 18 December 2017 (UTC)
  • (edit conflict)Personally, at some point, we're unfortunately going to have to say no, and stop accepting new submissions. This is now not at that point, but if we end up near 5000, we might have to consider that. Also, as we cannot decline for these sorts of things, newbies need to be better informed about important MOS matters, such as references after punctuation and section headers need to be in goddamn sentence case. !dave 19:13, 18 December 2017 (UTC)
  • The main problem is with the decline rationale that AFCH has as default. Many of these should be changed and would then change the way that AFCH is used. This would, in turn, change the way that articles are reviewed. The whole "not yet shown to meet" the notability guideline is ambiguous, and encourages reviewers to decline without looking for sources themselves. At NPP we are required to look for sources ourselves (not nessessarily required to add them, but to make sure that they exist). The "submission is improperly sourced" decline option is the worst thing about AFCH and possibly the cause of most of the trouble we are seeing here. It is sufficiently vague as to result in it being used for declining drafts based on badly formatted references and other issues such as having references, but not inline citations. — Insertcleverphrasehere (or here) 20:24, 18 December 2017 (UTC)
    • So what would you recommend as a policy/guideline to change this? Guidance that reviewers should accept articles that they can see are notable, even if the article hasn't reached that stage yet? Like you say, they are under no obligation to do more work, but can add a comment saying "searched and seems notable. accepted" Maybe cross post to a wikiproject after the accept? Another option would be to simplify the reviewer criteria to "would this pass AFD?" and nothing else (in fact some claim that this is already the policy, but others disagree, as I noted above)
    • As you mentioned reveiwers ascertaining notability, Insertcleverphrasehere I wonder what you would think about AFC reviewers having the option to approve articles but severly edit the bad stuff out or even stubify the article. Perhaps they can even do this now. This is line with WP:AFD which states that "If an article on a notable topic severely fails the verifiability or neutral point of view policies, it may be reduced to a stub..." and would satisfy both the editor who sees the page created, the reviewers who don't want to approve poor quality articles of notable subejcts, and the community who would get to work on the page. Egaoblai (talk) 21:17, 18 December 2017 (UTC)
      • I agree with all of this. We could make a tag that says something along the lines of "An editor has performed a search that has indicated that sources for notability exist but have not yet been added to the article". This would be added, then the article could be published immediately. — Insertcleverphrasehere (or here) 23:04, 18 December 2017 (UTC)
        • Something like this template: {{sources exist}} perhaps? — Insertcleverphrasehere (or here) 20:24, 19 December 2017 (UTC)
          • Yes I think accepting but adding a template is a good compromise for those users who don't like to be seen as accepting what they see as poor content. I think reviewers can be scared of being punished for accepting an article that isn't GA standard, and thus the backlog, this way would mean that 'yes, i know it's not good, but let's put it in mainspace and have the community work on it rather than telling the original editor they must make it perfect before it's accepted. From the other side, if the article really isn't great, then reviewers could also make more use of the 'promising articles' template, which would mean they could reject it, but it wouldn't get forgotten and deleted.Egaoblai (talk) 07:03, 20 December 2017 (UTC)
  • I think sourcing and notability lines should be more simple and short. Also as mentioned before I think if we keep Afc then the articles should be moved into the article space automatically. However there would be sourcing filters and vandalism filters, also to submit an article you should be an auto-confirmed user, I propose the same with translations(auto-confirmed users can publish translations and they'll be reviewed). Also this will help major recent events that have to wait 2 months for article creation. Also I agree that Afc reviewers are usually unwelcoming and sometimes don't take enough time to see that the article might be notable. YuriGagrin12 (talk) 22:19, 18 December 2017 (UTC)
    • Your proposal seems to abolish AfC and just chuck everything into NPP. This would mean that we would have to abandon ACTRIAL, because new users have to have some venue to suggest/submit new articles. This is a terrible idea. The whole point of ACTRIAL is that trolls and advert pushers are deterred from submitting obvious garbage because they know that their submission will undergo content review (it doesn't go to AfC instead, it just isn't submitted at all). Remove this step, and suddenly NPP is inundated with 300+ pages of garbage that is almost immediately deleted and just serves to waste valuable reviewer time. With ACTRIAL's help we are finally fighting our backlog back down from a ridiculously high number, and we at NPP can't support your proposal. — Insertcleverphrasehere (or here) 23:04, 18 December 2017 (UTC)
      • @Insertcleverphrasehere: Im not trying to abolish Afc, I probably didn't explain this clearly enough but before articles are submitted for review and into the main article space they would undergo vandalism and sourcing checks. These checks could be done by a computer by algorithms developed by showing it examples of good articles and bad articles, good sources and bad sources. If the computer checks it off it would be moved into the article space and reviewed by human later. Also for new users it could just be the same. YuriGagrin12 (talk) 02:00, 19 December 2017 (UTC)
  • A good hard look at the AFC reviewing instructions (including the flowchart) may be productive if we can simplify or streamline the process. However it does not address the issue of reviewers who are not actually complying with the AFC standards (e.g. I have seen several "ilc" declines on draft submissions that are not subject to WP:MINREF). Unfortunately I believe we're failing to cope with a recent influx of eager but insufficiently experienced AFC reviewers. Roger (Dodger67) (talk) 12:13, 19 December 2017 (UTC)
  • Another HUGE problem is with articles like this one. We have a record producer who seems like he is borderline notable, but nearly all of the refs are absolute garbage in terms of notability (but cited to trivial facts). It is difficult to tell that there are at least two reasonably good refs buried in amongst the chaff [6] [7]. So it gets declined over and over, wasting reviewer time every time. Even worse is with submissions that just are not notable, because they get resubmitted over and over without ever going away: with NPP at least when an article is reviewed it doesn't just get resubmitted immediately into the backlog, erasing the review work that was just done (well sometimes it does, but it isn't as systemic of a problem given that we have CSD G4). Does AfC have a recourse to discuss and delete (or keep/accept) AfC submissions that keep getting resubmitted? Yes: MfD, it just isn't used consistently.
  • Potential solution to all our problems: Perhaps we could have a limit of 3 re-submissions (or some other number) and then it goes straight to MfD as a candidate for either deletion of the draft, or else cleanup and accepting (it won't be allowed to go back into draft space, it either gets deleted, or sent to main space to go into the NPP queue). That way we would solve the issue of non-notable drafts being resubmitted constantly and using up all the reviewer time, and we would also solve the issue of reviewers not reviewing properly, as these sources would be identified during a discussion at MfD, and then the article would be sent to main space where it belongs (with cleanup if necessary). TL;DR: Essentially use MfD as an AfD for all drafts with 3 or more declines (on the third decline), as a way to stop these articles gumming up the works. This would also mean that AfC reviewers would have to be especially careful in reviewing the third(?) review, as they would also be submitting the article to MfD if they still didn't think that it was appropriate. — Insertcleverphrasehere (or here) 22:58, 19 December 2017 (UTC)
  • The impression I get is that AfC is just being too picky about things that frankly don't matter that much. A basic article getting created is fine if it means that people (or, just as likely, robots) will come along and fix the minor problems. I don't see any reason why the threshold for article creation should be any higher than "would this survive a deletion debate" and it seems the reviewers at AfC are being more stringent than that; certainly this thread on Twitter would appear to see a similar problem. Would it not be simpler just to reduce the amount by which we incentivise articles from going through the AfC process, if it struggles with volume and with finding experienced editors. I'm sure it's very frustrating for the editors involved in AfC to have a bunch of us non-AfC people complaining about their hard, well-intentioned efforts, but if increasing the workforce isn't a simple solution, decreasing the workload is more-easily manageable, no? — OwenBlacker (talk) 22:01, 22 December 2017 (UTC)
    • I agree; it seems that the AfC criteria are being applied far, far too strictly. Take, for example, the "Quick-fail criterion" regarding advertising, that says "If the submission is a blatant advertisement decline the submission as such." To my mind "blatant adverting" means things like "Acme washing powder washed whiter than all others, buy some today", yet we see articles describing companies or products, in neutral terms, failed for "reading like an advertisement". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:36, 27 December 2017 (UTC)
  • I recently stumbled upon the past activity of one former AfC reviewer. Within a short space of time they had reviewed a large number of drafts, at an average rate of one review per minute. A total of eight drafts were accepted, over 700 were declined, with rationales that often didn't make sense. The majority of the declined drafts I've seen so far were mainspace ready. This user then stopped reviewing because of differences with the AfC community. Judging from their talk page archives, their departure from the project ironically had nothing to do with their appalling decline rate being noticed (it wasn't), but was apparently precipitated by one AfC regular badgering them into tagging drafts for speedy deletion instead of simply declining. This hearkens back to the observations made above to the effect that at least some in the pool of reviewers have "standards" that are out of touch with those of the wider community. But there's something else as well: unlike NPP, AfC has an inherent bias against accepting. Accepting a submission entails some work – choosing an appropriate mainspace title, formatting the text, categorising, project-tagging etc. – whereas declining usually takes a single click. Some reviewers, in their enthusiasm for cutting down the backlog (or out of whatever motivation that drives people to make rapid-fire edits), then have a very strong incentive for declining rather than accepting. – Uanfala (talk) 15:06, 27 December 2017 (UTC)
This is a good find, but it remains the case that unless editors like you who know the ropes so to speak, actually go actively looking for this, these kind of problematic behaviours goes on unnoticed, and who knows how many articles have been lost at g13 and how many users have left the project in frustration. Egaoblai (talk) 16:25, 31 December 2017 (UTC)

Some examples

It might be useful to have some examples of recent declines, so that we can discuss whether they criteria are being applied correctly:

  1. Old revision of Draft:Nancy Wilson (basketball coach) - "The content of this submission includes material that does not meet Wikipedia's minimum standard for inline citations. Please cite your sources using footnotes"
  2. Old revision of Draft:Margaret Jeans - "This submission is not adequately supported by reliable sources"
  3. Old revision of Draft:New_Celeste - "This submission does not appear to be written in the formal tone expected of an encyclopedia article" (with bonus "When a reviewer has left you a specific comment on some aspects of the draft and you blatantly ignore them and resubmit your draft, it's difficult to view that as anything but disruptive.")
  4. Old revision of Draft:Created_In_Scotland_(reality_TV_show) - "This submission's references do not adequately show the subject's notability"
  5. Old revision of Draft:George_Washington_Ragan - tone
  6. Old revision of Draft:Dr._Edwin_F._Klotz - tone; with "most of the sources... are obituaries" (?!?) and "too many words like 'american traditionalist' and 'secular progressive'"
  7. Old revision of Draft:Chris_Turner_(drummer) - notability
  8. Old revision of Draft:Bagnan_High_School - notability (previously rejected three times as "more like an advertisement"; first submitted May 2016)
  9. Old revision of Draft:Charles_Falzon - "This submission appears to read more like an advertisement than an entry in an encyclopedia"
  10. Old revision of Draft:Christ_Episcopal_School - "more like an advertisement"
  11. Old revision of Draft:Leyla_Martinez - (as Draft:Criminal Justice Reform Advocate) "more like an advertisement"
  12. Old revision of Draft:Curtin_Univesity_Dubai - "The content of this submission includes material that does not meet Wikipedia's minimum standard for inline citations" (with an edit summary claiming "Submission is a BLP that does not meet minimum inline citation requirements")
  13. Old revision of Draft:Catherine M. Stanton - "more like an advertisement" - note also [8], which apparently went unanswered.
  14. Old revision of Draft:MARMOK-A-5 - "improperly sourced"
  15. Old revision of Draft:Invoke_Malaysia - notability
  16. Old revision of Draft:Mood_Lighting - notability (sources include Journal of Environmental Psychology, Science Direct, PLOS One, Neuroscience Letters)

(numbered for ease of discussion; more may follow) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:46, 27 December 2017 (UTC)

Added #13. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:26, 31 December 2017 (UTC)
Added #14 - #16. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:55, 1 January 2018 (UTC)
1 and 12 are good examples of the invalid ILC declines I've mentioned elsewhere in this discussion. Reviewers who make too many such obvious mistakes should be stopped. Roger (Dodger67) (talk) 15:39, 27 December 2017 (UTC)
2 is a valid decline, though the decline message could have been edited to not only refer to "reliable" sources, but should explain BLP1E. Roger (Dodger67) (talk) 15:48, 27 December 2017 (UTC)
There is no way for people to provide oversight, that's why I support the current proposal in Village pump proposals to send these drafts articles to XFD then at least they get a community look before being rejected in draft purgatory and finally quietly deleted under g13.Egaoblai (talk) 12:26, 30 December 2017 (UTC)
Number 12 is a good example of something that would NEVER get deleted at AFD, which is the rule for AFC reviewing.Egaoblai (talk) 12:28, 30 December 2017 (UTC)
It may not get deleted, however it should be redirected/merged to Curtin_University#Dubai_Campus, because there isn't a need for a seperate article. Galobtter (pingó mió) 07:15, 31 December 2017 (UTC)
That was not the reason for declining at AfC; the reason given was "The content of this submission includes material that does not meet Wikipedia's minimum standard for inline citations", and that the article is a BLP. Are those valid reasons for declining this article at AfC? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:09, 31 December 2017 (UTC)
Number 5 looks like a copyvio of https://www.findagrave.com/memorial/44931508#. That url says the text was contributed to findagrave on 1 May 2017; the draft was created on 2 May 2017. It is possible that the original contributor to findagrave is the same user that wrote the draft, but in the absence of an explicit license to use the text on Wikipedia, I'm going to G12 it. As for the tone issues, there are certainly a few sentences that would need to be rewritten were it to be accepted, but the copyright issue takes precedence. /wiae /tlk 01:16, 31 December 2017 (UTC)
Perhaps it is; but the issue here is AfC declines, and that was declined with the justification "This submission does not appear to be written in the formal tone expected of an encyclopedia article". Was that a valid reason bot to publish the article? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:07, 31 December 2017 (UTC)
Fair point. We can still conclude that the reviewing criteria were not applied correctly, because a copyright violation is a quick-fail criterion in reviewing workflow and should always be checked before any tone issues (which as you note was the decline rationale). The draft certainly did have some tone issues but it may just have been easier to fix them than to reject the draft outright. I'd like to hear what others think. /wiae /tlk 11:58, 31 December 2017 (UTC)
tone should never be a reason for declining a draft, unless it's absurdly out of place. These are the things that can and will be fixed by the community in mainspace. The current strict AFC system subverts the entire idea of what a wiki is supposed to be (collaboration) and turned it into a space where enthusiastic new contributors are corralled into an grading system that is not on par with AFD and so unfairly treats new reviewers with a higher standards, expecting them to create high quality articles with little actual editing help. Egaoblai (talk) 11:34, 2 January 2018 (UTC)

SwisterTwister

User:SwisterTwister and four other accounts have just been blocked as sockpuppets/ puppeteer. Given that some of the accounts were used to stack delete !votes, and that TS has been active at AfC, what can be done to review their declines? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:35, 30 December 2017 (UTC)i

this is worrying because I have been looking through some of the old drafts and sister twister pops up a lot for rejecting drafts that are mostly good. I guess the step is to ask people at AFC, an admin perhaps? I'm not aware if there is a user tool to browse drafts that have been reviewed or not.
Also, unlike the AFD discussions that this user was revealed to be a part of there is no way we (regular users at least) can check ST's rejections at AFC if they have been deleted at g13. Another reason why the current system is broken.Egaoblai (talk) 00:16, 31 December 2017 (UTC)
@Egaoblai: Examples of the former would be useful, please. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:50, 31 December 2017 (UTC)
@Pigsonthewing and Egaoblai: You may already be aware of this, but a log of non-G13ed AfC reviews is available here: https://tools.wmflabs.org/apersonbot/afchistory/#user=SwisterTwister. It pulls in over twelve thousand reviews when I run it. /wiae /tlk 01:22, 31 December 2017 (UTC)
Thanks, is there a tool to see all rejected drafts by all users? Egaoblai (talk) 23:23, 31 December 2017 (UTC)
@Egaoblai: Good question. Not sure. I know Primefac has some statistics but I'm not sure whether they would include what you're looking for. I imagine it would be possible to write a SQL query over at Quarry to grab what you're looking for though. /wiae /tlk 01:35, 1 January 2018 (UTC)
  • Primefac has been the admin that is most active at AfC and is aware of most of the contributors there work. If he has been rejecting to many, that is a much easier fix than accepting too many. The draft creator simply has to resubmit and another reviewer will look at it automatically. TonyBallioni (talk) 01:02, 31 December 2017 (UTC)
    • I respectfully disagree to the extent that if a draft or article is deleted, it is discouraging to legitimate new users. Many rejected drafts are simply abandoned. Montanabw(talk) 01:24, 31 December 2017 (UTC)
      • Moreover, reviewers have the tendency to 'pile-on decline', declining a draft if it had not been changed much since the last review, or declining it simply because it had been declined lots of times, even if the draft is otherwise decent. In borderline cases or when unsure, reviewers tend to defer to the judgement of the previous reviewer and decline a draft, whereas a draft that hadn't been reviewed before might stand a better change of being accepted. Darylgolden(talk) Ping when replying 03:33, 31 December 2017 (UTC)
ST may or may not have been declining poorly, but the key problem here is that AFC has no oversight. A committed troll/sockpuppet could easily cause havoc there and unlike AFD, it's not public and there's no way to see what's going until after the fact.Egaoblai (talk) 10:08, 31 December 2017 (UTC)185.230.125.53 (talk) 10:02, 31 December 2017 (UTC)
  • Didnt we just close an ani and an afc talk discussion about the declines, like a few months ago? Then both closed with no effect on drafts. I feel like everytime st is mentioned its for the same thing that was talked about beforehand. Lets move on from how he reviews, and consider how hes helped afc and its backlog. Without him im promise you the backlog would of been like this years ago and triple what it is now today! Trust me, we hear you, but stop eepeating yourself its not a game of telephone. Ⓩⓟⓟⓘⓧ Talk 01:12, 31 December 2017 (UTC)
    • " Lets move on from how he reviews" Let's not. If good-faith, new editors have had their contributions deleted improperly, let's deal with that, and try to retain them as contributors. As for "we hear you", you need to provide evidence of that (by showing ho the issues with AfC that have been raised here and in the above sub-sections are being dealt with), not a mere platitude. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:13, 31 December 2017 (UTC)
    • As I said at a different venue his reasons for block and/or socking has manifested from an entirely different scope or outlook and that too for the last two months or so, out of his editorial stint of over 10 years. And, quality-checking 12800 reviews is just impossible. Winged BladesGodric 11:18, 31 December 2017 (UTC)
      • And as I have noted, the use of socks was specifically in order to cause the improper deletion of valid content - it would be most troubling if members of the AfC community did not regard this as cause for concern. As for the figure of 12800, no-one is suggesting any need to review those that TS passed; and if the problem is, as you claim, recent, the rejections can be reviewed in reverse order. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:40, 31 December 2017 (UTC)
That surely would be more feasible.Winged BladesGodric 14:01, 31 December 2017 (UTC)

Perhaps some AfC regulars might also review the many unanswered requests from AfC contributors, asking for help, in the arcrhives of SwisterTwister's talk page? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:29, 31 December 2017 (UTC)

I don't think they are unanswered. SwisterTwister leaves (or rather left) comments on the drafts themselves instead of on his talk. Galobtter (pingó mió) 11:37, 31 December 2017 (UTC)
There is no response to the question asked in response to example #13, in the section above, on that draft. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:46, 31 December 2017 (UTC)
Andy is right. But I wasn't surprised, not like with some whom we have had to block, such as for example DrStrauss. We weren't aware of the extent of ST's socking (in fact the ST account isn't even the master). What several of us are aware of however, is that in his unsolicited off-Wiki communications with us, he was indeed a curious character. That said, and as I said on ST's talk page, let's move on - we can't put the toothpaste back in the tube, not at this stage. Kudpung กุดผึ้ง (talk) 12:29, 31 December 2017 (UTC)
Speaking of DrStrauss, in their active period earlier this summer they reviewed at an average rate of one draft per minute, accepting a total of 8 drafts, and rejecting over 700. – Uanfala (talk) 15:56, 1 January 2018 (UTC)
If we've lost potential good contributors because of improperly declined drafts then yes, there isn't much that we could do to reverse that. But at least we could do something to prevent the loss of potentially good content. Re-reviewing 12,000 drafts is not feasible within any short period of time, be we could at least make the drafts declined by ST exempt from G13 for the time being. – Uanfala (talk) 18:07, 31 December 2017 (UTC)
Second that proposal. I think this makes things clear that AFC reviewers need some oversight by the larger community and if the current proposal that brings them to AFD doesn't pass then we need another way. I'm not gonna judge ST yet before going through a large number, but what's clear here is that people with agendas can become AFC reviewers and essentially do huge amounts of damage to the project without anyone really realising. We need a system to check this. Egaoblai (talk) 23:23, 31 December 2017 (UTC)

Here's a good example to show how fundamentally AFC isn't working: Bahamas_Leaks This page was sitting in rejected drafts by SisterTwister, rejected on the "this subject is not yet shown to meet notability ground" reasoning. I googled it and found the subject was notable, it being the subject of many articles from different media. So instead of resubmitting, I moved it to mainspace. it wasn't a perfect article. But do you know what happened? in just a few days, people have been adding categories, tidying up, adding links, etc.

It's simply stunning how much adding a article to mainspace can help with improving it. The current AFC system, whether it means to or not, leaves drafts out to dry and die.Egaoblai (talk) 17:35, 2 January 2018 (UTC)

ST and DST aren't the prime examples of model AFC reviewers.Both had their permissions revoked at some time or other.By the way, tone is a very good reason to decline drafts phrased in art-spam.(esp. in corp articles etc).Winged BladesGodric 17:45, 2 January 2018 (UTC)

Re-reviewing

Many editors have pointed out the low quality of reviews and the lack of accountability of reviewers as being a problem for AfC. How about implementing a system to allow for easier checking and re-reviewing of reviews? The idea would be to have the AFCH script create a log of all the reviews an editor makes (rather like Twinkle's CSD log). Other reviewers can then more easily look over and counter-check reviews, allowing problems to be spotted more easily. Something like this. This was already done for backlog drives (back when AfC done them) but it isn't done for regular reviewing currently. Darylgolden(talk) Ping when replying 02:51, 1 January 2018 (UTC)

Therr is already a detailed log at WP:Afcstats.Why do we need another one?Regards:)Winged BladesGodric 04:06, 1 January 2018 (UTC)
One deficiency in that is that it misses the pages that were deleted, as would happen with many declines. Graeme Bartlett (talk) 11:14, 11 January 2018 (UTC)
I can always update the tool so that it keeps the titles of pages that were deleted. Enterprisey (talk!) 18:14, 28 January 2018 (UTC)
That sounds useful for the tool moving ahead. I did some checking of the deleted declines, but everything I checked was suitable for declining. Graeme Bartlett (talk) 04:10, 13 February 2018 (UTC)

Perhaps a solution could be to allow all experienced (extended confirmed?) editors to review articles, without the need to opt in. --NaBUru38 (talk) 19:33, 31 January 2018 (UTC)

Separate password for logging in with limited access

Tracked in Phabricator
Task T153454

Hello. For the past decade, I've constantly seen many editors using legitimate alternate accounts to login, mostly to maintain separate access/password from work computers. I've didn't really bother or paid much attention to the facts or circumstances surrounding such arrangements until now; when I've changed jobs, and I'm not too sure if it's the safest decision to login with my admin-access account on my work computer.

Surely, opening an alternate account popped up in my mind. But looking at the bigger picture, that decentralizes your work and makes it less transparent for others to review the same. And sometimes, having alternate accounts (despite disclosing the same - however discretely) opens doors for abuse, like being able to multiple-vote and whatnot.

Wouldn't it be better if the user account would be able to simply "add an alternative password" in their preferences, and themselves 'tick' what user access will be enabled when logging-in using that particular alternative password?

Thoughts welcome. Yours truly, Rehman 03:45, 13 February 2018 (UTC)

We actually have something like this already @Rehman: - however it doesn't quite to what you are looking for. What we have is Special:BotPasswords, however it does not allow for web-based accessing (only API access). — xaosflux Talk 04:12, 13 February 2018 (UTC)
While searching, it looks like there is already a feature request open for this: phab:T153454. It would need to be a software solution, so the scope would be beyond the English Wikipedia. — xaosflux Talk 04:12, 13 February 2018 (UTC)
The phab link is 100.00% spot on to what I'm trying to say. Thank you for that. I'm very glad to see there's more people wishing that this existed! :-D Rehman 04:16, 13 February 2018 (UTC)

Forking articles

WP:CFORK is disallowed for good reason. But what if.. take for example the Featured Article Castle. The amount of sourcing available on castles is immense. It would be possible to write many very good FAs about Castles comprising different sourcing and prose. Different focus, emphasis, quotes, pictures etc.. But since one castle already exists (that is very good) it is basically a fortress that prevents development of other castles with different architecture. Sure, someone could try to modify the existing castle, but again it's already very good and why change what the community has deemed FA quality - raids on a FA rarely happen. I have no idea what a possible solution might be (and I have no intention of building a new castle) but it seems a lost opportunity that this particular castle will effectively stand as it is for a very long time without a reasonable possibility of starting over from scratch with a new set of editors and ideas. Again, this castle is very strong (FA) and will unlikely be scrapped for decades to come, there is not much room for an editor to build a new castle on Wikipedia. Which isn't to say there is a lack of opportunity for other things to do, but for the castle-focused editor the opportunity to build this one is effectively gone. -- GreenC 17:03, 13 February 2018 (UTC)

@GreenC: I don't understand what problem you are trying to solve. But, if there is an aspect to castles that could be stand alone article, I don't see why that would not be allowed. For example, we have articles on house, and also different types of houses such as Ranch-style house and American Craftsman. RudolfRed (talk) 17:49, 13 February 2018 (UTC)
Ok I tried to explain, but if it's not clear that is my fault. There could be more than 1 FA on Castle, as example, both excellent quality and very different neither better than the other. It's not a "problem" but an observation of a limitation imposed by how Wikipedia works. -- GreenC 18:39, 13 February 2018 (UTC)
Much of what you're saying seems like a natural consequence of our end goal: building an encyclopedia. There should be an end goal for most of the articles within that encyclopedia (though, if you think you can improve an article, don't let the star in the top right stop you). If you have reasonable belief that there is some aspect or another of castles that hasn't been captured already, you should consider writing a subsidiary article or improving one of those that exist (it looks to me that there perhaps should be a construction of castles article, for example). --Izno (talk) 19:51, 13 February 2018 (UTC)
Yeah I think I addressed most of that in my initial post but 'building an encyclopedia' doesn't necessarily have to mean there is only one quality article for a given topic. -- GreenC 00:35, 14 February 2018 (UTC)
I don't see why we would have multiple articles on a single topic unless there is some desire to be The One who made it. If there is an opportunity for improvement, those are welcome, because we all acknowledge that we miss things. I suppose it's possible that we have found some local-maximum goodness of the article with the current article structure and wording through the evolutionary algorithm that is the basis of constructing Wikipedia articles, but we're also not machines and can thus reasonably recognize when we haven't gotten everything that's needed to be said about a castle into the article about castles. My question is a bit utilitarian in response: why spend a lot of time describing it again? What value do you think will be added to Wikipedia if a different person tries to build another castle? And conversely: what value will be lost from Wikipedia? I can think of several items in the latter category. I can think of perhaps one in the former. --Izno (talk) 01:20, 14 February 2018 (UTC)
No loss to Wikipedia if someone(s) choose to build a good article on castles and do nothing else for Wikipedia if that is their interest. We're not here to tell people what they should or shouldn't do. Outside of Wikipedia there are 100s (1000s?) of encyclopedia articles on "castle" which are all somewhat different. They don't merely "describe" castles there is choice of emphasis, sources, prose etc.. read other encyclopedias they can be radically different. But Wikipedia doesn't recognize that there can be more than one approach to the same topic, or at least is not structured to allow for it (except by internal changes, but is unnecessarily destructive to an existing FA). The value add would be a great article on castles that wouldn't have emerged otherwise. It's not really an issue of OWN which incorrectly assumes it would be a single person writing the new article and not a group effort (and is somewhat bad faith misses the point). -- GreenC 07:10, 14 February 2018 (UTC)
The loss to Wikipedia is every other editor's time spent on this new article. To take this out of the theoretical: Wikipedia does not have a sufficient quantity of _X_ kind of person necessary to have multiple articles on the same exact topic. X can be "vandal fighters", it can be "quality reviewers", it can be "POV reviewers", and it's definitely also "content creators"--and I have little reason to believe that enabling second, third, or more articles on one topic would increase our supply. Never mind the concepts in WP:CFORK--that is, creation of multiple articles can (and usually will) result in redundant or conflicting articles. If I had two bits of a software program source that look the same, read the same, and do the same thing, would you leave them be or would you refactor them so that you only have to deal with one of them (see also database normalization)? There are usually a few hundred ways to skin a cat in most things in life, but that doesn't mean we skin a hundred cats (except sometimes machines do--but we are not machines, again). Just about everyone has something better to do. --Izno (talk) 13:49, 14 February 2018 (UTC)
everyone has something better to do - If that were true then there wouldn't be so many Wikipedia competitors. It's human nature, and a healthy development, to remake things. Will some of those things fail? Yes, but some will break new ground. Blocking that development stagnates the project, creates apathy and spawns competitors (though due to the network effect they will have a tough time). There are studies that show editors have left because they believe the important stuff is "done". If someone wants to rewrite castle from scratch, Wikipedia doesn't want them and they can go elsewhere. We've got a FA, thanks but no thanks. This is both bad for innovation and editor retention. -- GreenC 04:06, 15 February 2018 (UTC)
Please don't cherrypick my words. The context of that phrase (which is my entire response) is "there are better things to do than making another high-quality article for everyone involved". I won't be answering here further because at this point, I think it should be clear the kind of reception you would get trying to push this idea further than the idea lab. --Izno (talk) 14:20, 15 February 2018 (UTC)
Well I'm sorry you got upset, that wasn't my intention. If I had quoted it in full it wouldn't have changed the meaning of it, or my response to it. The fundamental idea that people have something better to do misses the point of what I've already repeated at least twice: there is room for more than one high quality encyclopedia article on a topic, evidently - there are 100s or 1000s of them for George Washington for example. However on Wikipedia there isn't room, and that is both a feature and a bug. -- GreenC 17:15, 19 February 2018 (UTC)
  • How about starting an experiment? It will probably be difficult to build a new castle from scratch, but it should be comparatively easier to translate one from a different language wikipedia. – Uanfala (talk) 22:26, 13 February 2018 (UTC)
    • Actually, that sort of stuff already exists: see Quantum mechanics and Introduction to quantum mechanics. – Uanfala (talk) 22:27, 13 February 2018 (UTC)
    • @Uanfala: starting an experiment - you mean sack the castle and build a new one? It's already very good would be destructive... Not sure what the answer is as CFORK is an important concept, but possibly there could be room for multiple FAs on the same topic with a "primary topic" FA in the mainspace and the other's in other namespace. It would require develop in Draft first, reach a good/featured level before moving into the new namespace (call it "fork:" or something). Just brainstorming - an idea thought of right now and not a proposal. -- GreenC 00:35, 14 February 2018 (UTC)

Synchronized User Reading Lists

This idea originated from a feature of the Android Wipipedia app which allows me to save a collection of articles into named reading lists. This feature appears to be absent from the web version. My proposal is to add this feature to the web version, and have it synchronized across mobile apps for logged in users. This is not the 'watch list'.

As I understand it the Watch List is where a user would keep a list of articles they are watching for changes so they can be notified when changes are made.

The Reading List is a list of articles the user is personally interested in, are reading and may want to keep a list of for rereading or referencing later. No notifications would be sent out about articles in any user created Reading Lists. The Reading Lists would be private, for the user only, or could include an option to make a list public.

By synchronizing the Reading Lists, any article the user adds to a reading list or if they create a new list on the mobile app, or the website, is applied account wide so that when they change platforms, their updates are there for them. For example, I find an article I am interested while browsing the website, I add that article to a reading list. Later when I go out and take my mobile device with me, the article is there in my reading list on the mobile device ready for me to call up.

This would only work for users with accounts when logged in to their account. — Preceding unsigned comment added by Krahazik (talk • contribs) 17:31, 28 February 2018 (UTC)

Would it not be easier to create a folder of bookmarks on your browser? Martin of Sheffield (talk) 19:10, 28 February 2018 (UTC)
That solution is not cross-device friendly (unless you use Firefox on all devices, and cough up an email address to Mozilla [I think that's required]). --Izno (talk) 22:20, 28 February 2018 (UTC)
This has been suggested before, and I vaguely recall there being plans to add something like this, but memory is unclear. --Izno (talk) 22:20, 28 February 2018 (UTC)

Auto archiving

Can not see how Template:Auto archiving notice helps in anyway. It leaves the talk pages often empty, so if I (or any other editor) wants to review previous posted queries before the cut off point, it forces us to search the archive. And forces us to be psychic in order to know what queries and issues we might search for in the archive. Is there anyway we can retire it? --Aspro (talk) 16:10, 22 February 2018 (UTC)

@Aspro: If you're referring to disabling all talk page archiving, this probably isn't possible, since without archiving discussion pages would become difficult to load and then impossible to save due to the maximum page size limit of about 2 MB. That template also doesn't actually do anything, as far as I'm aware, since it's just a notice. The archiving is usually done with User:ClueBot III/ArchiveThis or User:MiszaBot/config. Jc86035 (talk) 18:14, 22 February 2018 (UTC)
Perhaps more to the point, the archiving bots are configurable, and if you don't want empty pages or near-instant archiving, then you can adjust the configuration. Many talk pages keep a minimum of four threads visible, and don't archive anything younger than 180 or 365 days old. Active pages need something faster (sometimes just temporarily), but typical talk pages can be successful with a very slow archiving process. WhatamIdoing (talk) 19:33, 23 February 2018 (UTC)
Yes. The issue here isn't auto-archiving (which is necessary on many talk pages), but the configuration and use of this feature on some pages. Believe me, without auto-archiving, this page would be unusable. עוד מישהו Od Mishehu 07:33, 25 February 2018 (UTC)
@Aspro: I barely edit anymore, but one of my pet projects is to add auto-archiving to articles whose Talk pages have grown larger than necessary. And as pointed out above, it's a matter of tweaking the bot template to leave a couple discussions on the Talk page while the older stuff gets archived. If you're seeing articles where everything gets removed, drop a list on my Talk page and I'll modify them when I get a chance. Or take it as an opportunity to learn the archiving templates, so you can fix them yourself! — The Hand That Feeds You:Bite 15:20, 2 March 2018 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(idea_lab)/Archive_24&oldid=1110538240"