Jump to content

Talk:Trust and Safety Product/Temporary Accounts

Add topic
From mediawiki.org
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.



Newsletter

Could someone turn the updates into an Special:Newsletter? Aaron Liu (talk) 04:17, 26 July 2024 (UTC)Reply

Yeah, I actually was considering this lately, especially since we'll post a new update today. Great idea @Aaron! SGrabarczuk (WMF) (talk) 16:57, 26 July 2024 (UTC)Antwort
Lucky! I was actually considering it because someone added me to the graphs newsletter. Aaron Liu (talk) 03:09, 27 July 2024 (UTC)Antwort
I did, of course. :D I work with T&SP and the Charts group. The newsletter seems to be working pretty well with the Web projects, so I decided to use it for Charts, too. SGrabarczuk (WMF) (talk) 12:51, 27 July 2024 (UTC)Reply

Alien UI

Congrats on the deployment! The banner on top of the entire page looks to be not an existing Codex design token, and I'd doubt that it fits its style guide that I have not read. I'd remove it and put the username in the normal spot instead, but if the intention was to annoy, fair play I guess, but maybe it should pick a color from the current Codex theme?

I doubt that this is an issue you'd like to fix, but when I was testing the interface in monobook, the top banner didn't appear and there was an ëdit session" portlet link. I clicked on it and got logged out. Did it actually say ëxit session"? I'm too innocent to find out by polluting the database w/ another account. Aaron Liu (talk) 03:15, 27 July 2024 (UTC)Reply

Thanks for testing the feature, @Aaron Liu. My understanding is that the intention for the banner is not to annoy but to draw attention. I will pass the feedback along.
We will look into the issue of the banner not appearing in Monobook. And yes, that was an "exit session" link for temporary account holders. The idea being that if you are on a shared library computer or such, you may want to get rid of your temporary account to avoid incorrect edit attribution. It is one of the features we want to get more feedback about. What do you think?
(so sorry for the delayed response)
-- NKohli (WMF) (talk) 16:38, 14 August 2024 (UTC)Reply

How will access be decided?

The lead paragraph says:

Only those who fight spam, vandalism, harassment and disinformation will have access to IP addresses.

How will that determination be made? My main activity is at en-wiki, and I don't specialize in any of those. However, I do on occasion revert and flag vandalism, place UTP templates following the multilevel warning system at en-wiki, and I sometimes initiate or follow up at en:Wikipedia:Sockpuppet investigations. I have identified a few patterns to look for, and linked up the offenders; example: en:User talk:129.94.8.198#Updated list and followed them up at SPI, but I rarely am the lead investigator. All told, this must represent < 5% of my activity, but it exists. How will you decide if someone like me (or anyone) gets this type of IP access? Mathglot (talk) 22:53, 28 July 2024 (UTC)Reply

Does [1] answer your question? Basically, either you are an admin, checkuser, etc. or you are long-term user, and you agree with the policy. --Matěj Suchánek (talk) 06:24, 29 July 2024 (UTC)Reply
Link to what was archived on Sunday Talk:Trust and Safety Product/Temporary Accounts/2024/June. It was archived because seven weeks went by without the Board responding to the issues raised. Please remember that the bare statement that "a temporary account will be opened for you" is illegal - the editor must be asked whether she wants a temporary account, told about the cookie and what will happen when it is implanted, and given enough information to enable her to give informed consent (or not, as the case may be). Here is a sample notice:

Page 1

I have completed the Wavelength Impact Measurement Part 1 (page 2) and agree to provide feedback upon equipment provided and its benefits via Part 2 (page 9), to help Wavelength understand and promote the effectiveness of its work. I agree to take all reasonable steps to look after any equipment, provide feedback and co-operate with any third parties Wavelength is working with. For the purpose of the General Data Protection Regulation 2018, I agree to the information given to Wavelength being kept by them and shared with Wavelength to allow Wavelength to conduct its work.

Page 2

We need your explicit consent to provide such information about you. You have the right to withdraw your consent at any time, except to the extent that action has already been processed based on your consent.

Page 9

We will store and process personal data you have provided as set out in the Wavelength Privacy Notice available at https://wavelength.org.uk/contact/privacy-cookies-wavelength-website

How will you ensure the user's informed consent and how will she be able to withdraw her consent? Having withdrawn her consent, how will you convey that information to the thousands of people using her private information? 92.29.249.130 15:10, 31 July 2024 (UTC)Reply

Hi. We are not withholding any more information with this change. Currently IP addresses for unregistered editors are publicly stored in perpetuity. Our goal is to reduce how long this information is stored for how many users have access to it. With this change, IP address access will be limited to a small number of users who need it for patrolling purposes. This information will only be retained for 90 days.
I will assure you that our Legal team has reviewed every aspect of this project thoroughly. NKohli (WMF) (talk) 14:42, 19 August 2024 (UTC)Reply

When this feature will be deployed on non-test wikis?

Hi, I know that the temporary account has been deployed in testwiki in July, which is a half-year delay when it was first announced in September 2023. What is the current timeline on the deployment on non-test wikis? On the announcement on September 2023, it was said that it was planned that the deployment on the first non-test wiki would be on March 2024. Due to the fact that the deployment on test wiki was delayed for half a year, is it expected that we will have this feature in September this year? 132.234.229.50 00:34, 7 August 2024 (UTC)Reply

Hello. There has been a lot of unexpected work on this project that altered our projected timeline.
We are currently chalking out the rollout plan for this work and selecting small, low impact, pilot wikis to deploy to first. It won't be before October at least. We'll update the project page when we have more information to share. Thanks. NKohli (WMF) (talk) 14:59, 14 August 2024 (UTC)Reply

IPv6 implementation?

@SGrabarczuk (WMF): IPv6 is 128 bits, /64 for the network and /64 for the host. For privacy reasons, most operating systems will rotate the /64 host portion of the address every once in a while. Will this each time generate a new temporary account or will these edits be grouped together? Multichill (talk) 16:52, 13 August 2024 (UTC)Reply

@Multichill temp accounts are cookie based, so the temp account is generated on first edit, and will persist so long as the user does not clear cookies. If the user clears cookies or the account expires after 90 days, then on the next logged-out edit, the user will have a new temp account. KHarlan (WMF) (talk) 14:51, 14 August 2024 (UTC)Reply
Please provide the exact wording of the notice which will appear when the editor whose device is cookie-free clicks the edit tab. Will she be warned of the wide range of information which will be collected about her as evidenced by this spreadsheet [2]? 92.29.240.122 19:28, 17 August 2024 (UTC)Antwort
According to the page about temporary accounts, the feature has been enabled on testwiki:, so you can test it there. If you try to edit a page, then you see MediaWiki:Autocreate-edit-warning above the textarea where you type in the wikicode. --Stefan2 (talk) 20:40, 17 August 2024 (UTC)Reply

Special:MyPage

If you go to testwiki:Special:MyPage (or testwiki:Special:MyTalk or testwiki:Special:MyContributions) with no cookies, then you see the user page (or talk page or contributions) for your IP address. Isn't this confusing, if you get a 'real' username as soon as you edit a page?

I tried typing ~~~~, {{subst:REVISIONUSER}} and {{REVISIONUSER}} in the edit textarea and clicked on "show changes" and found that the first two show the name of a temporary account (which doesn't exist yet) while the latter shows my IP address. I find this inconsistency confusing. I didn't proceed to click on "publish changes", so I don't know what happens on the saved page. --Stefan2 (talk) 20:40, 17 August 2024 (UTC)Reply

Thanks @Stefan2 for reporting these, I filed task T372722 about the My* pages, and task T372723 about the magic word issue. KHarlan (WMF) (talk) 05:04, 19 August 2024 (UTC)Reply

Memorable names for temporary accounts

Moving from raw IPs to automatically assigned names will make it possible to grant memorable names, too. A name made up of two words and a year would be ideal for me as a page-history watcher.

Google Docs assigns pseudonyms to anonymous commenters in a similar way and it's great. Following Google's approach would mean usernames like "Avid banana 2024", effective at nudging new editors into selecting a name of their own, but perhaps a bit too silly for an encyclopedia.

To encourage serious editing from these accounts, Wikipedia could generate more-serious names, such as "Aristotle's chinchilla 2024" or "Harold Sowell 2024 (pseudonym)".

Reserving usernames that end in a four-digit year or "(pseudonym)" shouldn't be a problem, right? Jruderman (talk) 17:20, 20 August 2024 (UTC)Reply

I don't like it. It could cause issues with CC-BY-SA 4.0, which states that
If You Share the Licensed Material (including in modified form), You must:

retain the following if it is supplied by the Licensor with the Licensed Material:

identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
So if the contributor 'supplies' a name or pseudonym, then you have to attribute the contributor. On the other hand, if no name or pseudonym is supplied, then no attribution has to be given.
If a random pseudonym is chosen by the software, then all becomes unclear: has the contributor supplied a pseudonym or not? If the pseudonym was supplied, then it must be used for attribution, but if it wasn't supplied by the contributor (but by software which did this without the contributor's knowledge) then attributing the pseudonym could mean giving incorrect attribution, which I suspect would be a problem.
If no random pseudonym is chosen, then it seems unambiguous that no pseudonym was supplied and so we avoid the problem. --Stefan2 (talk) 17:45, 20 August 2024 (UTC)Antwort
Interesting. I hadn't considered attribution.
Does the license explicitly allow not attributing contributors who are known only by IP address?
Mid-seriousness names are probably ideal when attribution requirements are taking into account.
Perhaps having a generated pseudonym should be opt-in at the time of publishing the first edit, with a choice of three generated names and one mostly-numeric name. Jruderman (talk) 18:02, 20 August 2024 (UTC)Reply
Temporary account is not the same as a registered account and the main purpose is to hide the IP address. If users want to choose a more serious username, they can create a registered account. SCP-2000 (talk) 18:08, 20 August 2024 (UTC)Antwort
My proposal is more for the benefit of people watching page histories and countering abuse, rather than for the benefit of everyone who edits without creating an account first. Jruderman (talk) 18:11, 20 August 2024 (UTC)Antwort
@Jruderman the idea did cross our mind when we were discussing temporary usernames.
One other challenge (besides what's mentioned above) is translation. IP addresses are currently well understood from the format itself. If we choose to go with something like "Aristotle's chinchilla 2024" it would need to be translated to be legible for other projects (since temporary accounts are global). This is quite difficult to do. So we decided to keep using numbers as they are already used for IPs. NKohli (WMF) (talk) 14:42, 21 August 2024 (UTC)Antwort
Could use automatic memorable names on some language wikis and the numeric fallbacks on others. Jruderman (talk) 17:27, 21 August 2024 (UTC)Antwort
As the username of temporary account is the same and unique across different wikis, it is difficult to use a different username on some wikis. SCP-2000 (talk) 01:26, 22 August 2024 (UTC)Antwort
Is it common for users to be active on different language wikis (not just one language wiki and the metas)? Jruderman (talk) 03:13, 22 August 2024 (UTC)Antwort
I think there are only a few newcomers who would be active on different wikis. However, as it goes against the current system work, it is unlikely to be possible from a technical perspective. SCP-2000 (talk) 04:00, 22 August 2024 (UTC)Antwort
It's probably okay for the first wiki they edit to determine their naming scheme. Jruderman (talk) 04:04, 22 August 2024 (UTC)Reply

When will the user right become available?

Hello,

This FAQ section is marked as outdated. Is there any update about this, and about this user right name?

Best, Jules* (talk) 22:08, 5 September 2024 (UTC)Reply

@SGrabarczuk (WMF). LD (talk) 13:45, 7 September 2024 (UTC)Reply
Hello @Jules* and @LD, thanks for the question. The user right is closely connected with temporary accounts being available on a given wiki, so let me answer this way: we are now checking what wikis could be our first pilots. We are looking at a diverse set of small wikis. Almost certainly, no large wiki (like francophone Wikipedia) will have temporary accounts in the coming months, unless an exception would occur. Later this week or next week, we may have another update. Merci SGrabarczuk (WMF) (talk) 13:18, 9 September 2024 (UTC)Antwort
Thanks for the reply, @SGrabarczuk (WMF)! Best, Jules* (talk) 13:21, 9 September 2024 (UTC)Reply

"Community" blockers

Hi @SGrabarczuk (WMF) & @NKohli (WMF),

Following blockers raised by TSP/Stewards/CU (@Martin Urbanec), I'd like to highlight some key issues for the communities:

There are 3 mains conditions to view IP addresses used by temporary accounts (checkuser-temporary-account):

  • User account is a minimum of 6 months old
  • User account has made a minimum of 300 edits to the local project
  • User account's right can be revoked at any moment.

Linked questions:

  1. What does 'Patrollers and other users' mean, given that the checkuser-temporary-account-log right exists?
    1. Does it mean we can create a new group which only holds the checkuser-temporary-account-log right?
    2. Could it be possible to assign this right to larger groups (e.g., autopatrolled) if another group like no-ipinfo is created to prevent access to checkuser-temporary-account? (see below: 2.1, 2.2)
    3. Could a group hold the checkuser-temporary-account-log right (given to Ombuds) to prevent local misuse?
      • If so, under what scope?
      • Signing ANPDP?
  2. How should the attribution/removal of rights be handled?
    1. Could a right, such as no-checkuser-temporary-account, could be created to block, ban or topic ban a user from using checkuser-temporary-account right? (see above: 1.2)
    2. Should this right only be assigned to revocable groups, meaning it cannot be granted to groups like autopatrolled where the role is permanent? (see above: 1.2)
    3. If the checkuser-temporary-account right can be granted to a group (e.g., fr:WP:Révocateur), should this group be assigned by the stewards, or can it be handled by a local group?
      • If a local group can assign it, is there a preference for who should do so — bureaucrats, admins, or a committee?
      • Under what scopes: solely Access to temporary account IP addresses + local scopes [if not contrary to the previous one], or in addition to other legal/technical constraints? If so, which ones? See below 5.)
  3. Inactivity:
    1. Does inactivity mean that the checkuser-temporary-account right will be disabled, even if it's part of a group, if the user is inactive?
    2. Does it mean the user group (i.g. :fr:WP:Révocateur), which holds the right, must also have its status revoked due to inactivity?
  4. About the right itself:
    1. Can the checkuser-temporary-account right be split into separate rights: checkuser-temporary-account and view-temporary-account?
    2. Could it at least be renamed to view-temporary-account?
    3. Shouldn't the prefix checkuser-* be reserved specifically for CU rights? (As it increases confusion between rights and groups)
  5. What is the role of WMF and TSP in the community wishes aimed at implementing the change?
    1. Can the WMF reject a community wish or proposal? (I think so since there are legal blockers but I'd details)
    2. Can the TSP reject a community wish or proposal? (I think so since there are technical blockers but I'd details)

At this stage, these questions are blockers for communities, as Wikipilots (and others), need more details to correctly implement this change, or at least start to talk about this. LD (talk) 14:58, 7 September 2024 (UTC)Reply

Hey @LD, thanks for the questions. Before we answer most of them, I'd like to make sure we understand the #5. What do you mean by WMF and TSP, and what do you mean by community wishes? Are you asking whether this or any other team at the Foundation would work on tempaccount-related wish submitted via the Community Wishlist process? SGrabarczuk (WMF) (talk) 23:34, 9 September 2024 (UTC)Antwort
@SGrabarczuk (WMF): by "community wishes", LD referred to criterias and process a local community want to use for the right to access IP adresses of temporary accounts (beyond functionaries who already have it). For example: give this access to all users with "révocateur" (rollback) right. Best, Jules* (talk) 11:00, 10 September 2024 (UTC)Antwort
I believe this change will bring a significant transformation in the practices within the communities. I would like them to have a broader perspective on the advantages, disadvantages, technical and legal limitations, as well as the possibilities regarding the upcoming (planned) changes, but also those that might or might not be implemented, regardless of the reasons.
Since communities can partially configure their own wikis, these questions (#5) are not meant to be answered individually and exhaustively but are intended to help guide the communities in shaping their discussions and consultations, and consequently, in formulating their wishes and proposals. For example, as Jules* and I pointed out, it would be useful to know whether a community request (such as a decision or a poll about "révocateur") can be rejected, and if so, what the conditions for rejection are, as well as how the request should be formulated — whether on Phabricator or directed to a specific contact person. LD (talk) 12:27, 10 September 2024 (UTC)Reply