The secondary feature is rarely used, complicates the code, and massively complicates the user experience. Yes, it dates from 2006 (?), but it was a bad idea then and it's a bad idea now.
- Mentioned In
- T28883: Allow listing of contributions from new accounts with the api
T114037: Special:Contributions/newbies doesn't show username/usertalk links for Flow items
T179137: Special:Contributions/newbies should go to RC filters to provide more options
T232173: Special:Contributions - update `IP address or username` label type
T231540: Unable to view contributions: Call to undefined method ContribsPager::getContribs()
T231427: [BUG] Internal error "Invalid option newbies" on Special:NewFiles
T135489: Special:Contributions in newbie mode shouldn't use old definition of newbie
T137478: Remove "Show contributions of new accounts only" option from Special:Contributions
T220553: Special:Contributions: Move all but the target selector into an "advanced" selector so users focus on the important bits
T117736: Convert Special:Contributions to OOUI
The proposal to remove the option “Show contributions of new accounts only” from Special:Contributions is not a good idea Special:Contributions&contribs=newbie&target=newbies is the most convenient way to check the edits of new editors and is more convenient to access than Recent Changes. If the functionality is split out into it's own function then fine but removal without replacement is unacceptable.
Can you elaborate in what way Newbie Contribs is more convenient than RC? Do you think it is possible for Recent Changes to become more convenient?
The main reason the Special:Contributions feature is a problem is its performance. It is very slow to load because Contributions (unlike RC) has no time limit. You can go to page 3,000 to find older edits (in theory). The Contributions database is designed for "View history" (for a single page only) and "User contribs" (for a single user only). The Newbies query is an unlimited search for all revisions by many different users, which is hard to optimise. But, we (humans) know that it is unlikely for a new user to have made edits 10 years ago, or to have more than a million edits. But, in theory that is possible because there is no time limit on "newest 1% of users". The database does not know this :)
To make these queries fast, we need to limit it by time (e.g. 30 days), and have a more specific meaning of "new user" (e.g. registered in last N days, with upto N edits).
And... that's exactly what recent changes now does. The Recent changes database is like the Contribs database, but limited to 30 days, with fast replicas optimised for arbitrary searches by any page or user. And the "newcomer" filter in recent changes shows edits by users registered in the last N days with upto N edits. (For en.wikipedia.org, it is currently set to <= 4 days and <= 10 edits).
Well since I made my original comment it appears changes i.e more filters have been made to RC that make it more usable, the filter for page edits for one. Before the RC list was filled with category changes rather than edits to category pages, now these can be filtered out is a plus. If possible problematic edits can be highlighted as is available under SpecContrib via https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rc then I think most of my concerns are gone.
Special:Contributions/newbies will no longer be working. This is because of performance reasons. It showed edits by new accounts. You can see this in the recent changes feed instead.
It's possible to add tags to edits from "new" accounts (with whatever definition you want for "new") using Extension:AbuseFilter. For example, this filter would match all edits made by accounts with fewer than 10 edits and less than 4 days old (i.e. the current autoconfirmed cutoffs for en.WP), allowing a tag to be added to them:
user_age > 0 & ( (int(user_editcount) < 10) | (user_age < 259200) ) & !(action contains "createaccount")
...though note that this comes with no endorsement of being a good idea.