Page MenuHomePhabricator

Drop the term "autoconfirmed" from user interface
Open, LowPublicFeature

Description

(Split from bug 43272 comment #13)

Yes I would prefer changing it everywhere where it is used, and it can be
done
as separate thing. We already have similar case for sysop -> Administrator so
it is possible.

The problem is that we don't have a non-jargon term for "autoconfirmed", for the very good reason that all community members are supposed to be autoconfirmed, although some wikis are more restrictive than others and stretch the concept a bit more (too much).
We have some established terms for non-autoconfirmed, though: 'newbie' (also valid in code), [[m:Newly registered user]].

In core:
'group-autoconfirmed' => 'Autoconfirmed users',
'group-autoconfirmed-member' => '{{GENDER:$1|autoconfirmed user}}',
'grouppage-autoconfirmed' => '{{ns:project}}:Autoconfirmed users',
'protect-level-autoconfirmed' => 'Block new and unregistered users',

Note that Wikimedia projects also have a "confirmed" group by default (that can be added by stewards).


Version: unspecified
Severity: enhancement
URL: https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=group-autoconfirmed&namespace=8

Details

Reference
bz43302

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:59 AM
bzimport set Reference to bz43302.
bzimport added a subscriber: Unknown Object (MLST).

Bug 43272 suggested "Established users" as a replacement for Autoconfirmed.

Note that newbie is everyone not autoconfirmed (or with an equivalent access permission), defined as such by core mediawiki (User::isNewbie).

It is also mentioned in:
'group-autoconfirmed.css' => '/* CSS placed here will affect autoconfirmed users only */', # only translate this message to other languages if you have to change it
'group-autoconfirmed.js' => '/* Any JavaScript here will be loaded for autoconfirmed users only */', # only translate this message to other languages if you have to change it

Although those entries are more technical.

It's definitely jargon, and probably somewhat unfriendly to new users. A term like "established" could be better, but we need to make clear that it still has a special technical meaning (not just a subjective view of who is established)

Also, we would need to decide about the confirmed group. Do we distinguish "established" and "autoestablished", or perhaps "manuallyestablished" and "established"?

This is a personal preference but... I find manuallyestablished an ugly word :)

I agree. :) It wasn't meant to be an ideal term, but mainly food for thought.

However, "confirmed" (the current equivalent to "manuallyestablished") isn't used that much in practice, so the term doesn't need to be perfect.

"Confirmed" isn't used much, but perhaps should be used more; in my experience, very few know what it is about. Clearer terms would surely be a good thing.

Perhaps the User Experience team might have some ideas.

More food for thought: automatically accepted, automatically assumed non-newbie, assumed to be not a newbie, having basic experience, out-of-quarantine.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:13 AM
Aklapper removed a subscriber: Purodha.