Trust and Safety Product/Conturi temporare
|
Conturi temporare
Un nou tip de cont de utilizator care schimbă felul în care se tratează cu datele personale ale utilizatorilor neautentificați
|
Conturile temporare pentru editorii neînregistrați vor fi un nou tip de cont de utilizator. Adresele IP ale editorilor neînregistrați nu vor mai fi vizibile public. Doar cei care combat spamul, vandalismul, hărțuirile și dezinformările vor avea acces la adresele IP.
Actualmente, oricine poat edita wikiurile Wikimedia fără un cont Wikimedia și fără a se autentifica. MediaWiki, software-ul din spatele proiectelor Wikimedia, înregistrează și expune adresa IP în jurnalul lui public dacă cineva editează fără a se autentifica. Oricine caută adresa dumneavoastră IP o găsește.
Proiectele Wikimedia stochează și publică adresele IP cu un motiv bun: ele joacă un rol critic în a proteja wikiurile noastre de vandalism și hărțuiri.
Adresa dumneavoastră IP poate însă să dea informații despre locul de unde editați și poate fi folosită pentru a vă identifica pe dumneavoastră sau dispozitivul dumneavoastră. Aceasta poate fi o chestiune problematică dacă editați dintr-un teritoriu unde wikiurile noastre sunt considerate controversate. Publicarea adresei dumneavoastră IP poate permite altora să vă localizeze.
După modificările din legile și standardele pe tema protejării vieții provate (cum ar fi General Data Protection Regulation și dezbaterile globale pe care le-a declanșat despre viața privată), Echipa legală a Fundației Wikimedia a hotărât să protejeze viața privată a utilizatorilor prin ascunderea IP-urilor față de publicul general. Vom continua însă să acordăm acces la acestea utilizatorilor care au nevoie să le vadă pentru a proteja wikiurile.
Știm că această schimbare va avea impact asupra actualelor workflow-uri anti-abuz. Ne angajăm să dezvoltăm instrumente sau să menținem accesul la instrumente care pot identifica și bloca vandalii, clonele, editorii în conflict de interese și alți actori rău intenționați și după ce IP-urile vor fi mascate.
Pentru toată lumea
Pentru patruleri și funcționari
Pentru dezvoltatori
Timeline
Last edited in .
- Deployment to testwiki –
- Deployment to first pilot wikis – /
- Next deployments –
Actualizări
: Changes to access to temporary account IP addresses, progress on the related tools and features, and preparations for more deployments
- Pilot satisfaction survey – we conducted a survey to check the impact of the pilot deployment and collect feedback on potential improvements. We asked stewards, global sysops, as well as CheckUsers and admins on 11 minor pilot wikis. We were happy to learn that the reported satisfaction was moderate to high, and disruption to workflows was low. Ideas shared there helped us improve the features and design. See the full analysis.
- Changes to access to temporary account IP addresses for users who don't have extended rights
- Manual granting – initially, we chose numerical thresholds to access IP addresses for users who don't have extended rights. We decided this before deploying temporary accounts on any wiki. However, after gathering feedback from our pilot projects we realized that these thresholds were quite low and it was still too easy for bad-faith actors to gain access to temporary account IP addresses. In addition, outside actors who may want to access IP addresses could contact users who have this right in an attempt to obtain this information. Temporary accounts should meaningfully improve editor privacy, so we decided to be more restrictive before we roll this feature out on wikis with large communities. This is why we updated the policy and changed the granting of this group from automatic to manual, done by administrators or stewards upon request. Read the full message we posted on Meta-Wiki and 20 large Wikipedias.
- Technical enforcement – we have decided to technically prevent the assignment of the Temporary account IP viewer group to accounts which do not meet criteria. Stewards will be able to override this limitation. Here's the decision record page. We will also include this on the Limits to configuration changes page.
- Next deployments will happen in June – in autumn 2024, we successfully deployed temporary accounts on small wikis. Since then, users with global rights have started to see how temporary accounts work in practice, and how to handle cross-wiki workflows. Now, we are ready for more deployments, and in the coming weeks, we will be talking with large communities about it. Communities which receive temporary accounts in June will have more opportunities and time to suggest improvements than communities which will receive the change in the last deployment later this year.
- Changes coordinated with the time of new deployments – because the following changes depend on the policy change described above and on one another, we are introducing them shortly before and after the next deployments:
- Access to IP Info on wikis with temporary accounts enabled and Meta-Wiki – users with access to temporary account IP addresses will have full access to IP Info. Those without access to temporary account IP addresses will not be able to use IP Info. In addition, IP Info will no longer be a beta feature and available as a full feature.
- Access to IP info on the remaining wikis – this is not changing – autoconfirmed users will have limited access, users with extended rights like admins will have the full access, and IP Info will remain as a beta feature there until the deployment of temporary accounts.
- Onboarding dialog (T373818) and Autoreveal (T374869) – the features we mentioned in the previous update will also be deployed around the time of the new deployments. The onboarding dialog will be shown to all users with access to temporary account IP addresses, on both wikis where temporary accounts were deployed in 2024 and wikis where the deployments will happen in June.
- Statistics of blocks on pilot wikis – we have collected data on the number of IP and account blocks before and after the pilot deployment. Our results show that while the number of blocks of registered accounts didn't change, most of the remaining blocks (approximately 90%) affected temporary accounts, and only about 10% were IP blocks. This seems to support our hypothesis that most of the logged-out abusive activity may be prevented with account blocks, which reduces collateral damage significantly. After the June deployments, we will be sharing more data.
- Special:MassGlobalBlock – we have built a new special page to allow stewards block multiple accounts and IPs globally. It was requested by stewards in 2016. We took inspiration from an existing gadget. This feature now helps stewards combat abuse from temporary and registered accounts more effectively. (T124607)
- FAQ and documentation refresh – considering all these changes, we have updated the FAQ to include the manual granting of the Temporary account IP address group elaborate on retroactive patrolling. We will be also rewording the part about the motivation for the project. In the coming weeks, we will make more documentation changes.
- Our plans for the next fiscal year – we invite you to read the final draft of the 2025/2026 Annual plan, and specifically the part describing our work: key results WE4.1 (Incident Reporting System), WE4.2 (improvements to anti-abuse tooling), WE4.4 (Temporary Accounts) and WE4.5 (AI risk and opportunity assessment). Share your comments on the talk page until May 31st.
Declarații ale Departamentului legal al Fundației Wikimedia
Hello! We have published a new policy page: Access to temporary account IP addresses. It explains how users can gain access to IP addresses. Later, we will update the section on using IP addresses. In it, we will add information on how and where to access the IP addresses, and what is logged when IP addresses are accessed. There is also a new page with frequently asked questions. Both pages use the term "temporary user accounts". This name comes from the first version of the software (MVP). Soon, we will share more information about it. We welcome your comments on the talk page.
