التعديل باستخدام آي بي: تعزيز الخصوصية وتقليل حالات إساءة الاستخدام/ميزة معلومات عنوان الآي بي
|
IP Info
|
هدفنا هو تسهيل وصول الإداريين ومكافحي التخريب والمستخدمين المتمرسين إلى معلومات حول عناوين بروتوكولات الإنترنت.
تعتمد الكثير من مهام سير العمل لمكافحة التخريب على الويكي بشكل كبير على المعلومات التي تكشفها عناوين IP. قد تؤثر هذه المعلومات على طريقة تفاعل المحرر مع مستخدم غير مسجل. في الوقت الحالي، ليس من السهل استرجاع وفهم هذه المعلومات.
هذا المشروع هو خطوة نحو تحسين الدعم على الويكي لفِرَق العمل لمكافحة التخريب. نأمل أن تكون مفيدة للغاية ونحن نمضي قدمًا في مشروع الحسابات المؤقتة.
- ERROR!
When editors want to learn about an IP address, they sometimes need to refer to external, proprietary websites. They often consult more than one website to cross-check the data or to get all the different pieces of information they need to do their work. Often an editor would spend a lot of time and energy looking up the data they want to see. We heard about these issues when we asked users about their workflows.
The idea is to provide this data on the Wikimedia wikis, so that editors wouldn't need to go to external websites. This includes surfacing information like:
- High-level location information about an IP address
- Owner of the IP address
- Whether the IP address is known to be behind a proxy or Tor node
- Whether the IP address is considered malicious by other websites
- ERROR!
اليوم، جرى نشر ميزة معلومات IP لجميع مواقع الويكي كميزة تجريبية.
بعد تشغيلنا الأولي على testwiki، تلقينا قدرًا كبيرًا من التعليقات. سألخص الملاحظات الرئيسة أدناه:
- كانت أكبر وأهم الملاحظات تتعلق بجودة بيانات MaxMind. جودة بيانات MaxMind، خاصة حول بيانات الوكيل proxy data، ليست رائعة. لقد تواصلنا مع Maxmind حول هذا الأمر ونتحدث أيضًا بنشاط مع Spur للحصول على موجز بياناتهم. بمجرد أن نتمكن من الحصول على موجز بيانات Spur، سنكون قادرين على دمجها في الميزة وإظهار المعلومات من مصادر بيانات متعددة.
- سمعنا أن الواجهة غير واضحة حول ما هي المعلومات المتوفرة وغير المتوفرة. نحن نعمل على تحسين العناوين وتقديم إرشادات أفضل حول المعلومات المعروضة.
- لقد سمعنا طلبًا حول توسيع الأداة لتشمل معلومات عالمية وتضمين أيضًا معلومات حول عناوين IP التي لم تقم بأي تعديلات على موقع wiki المحدد. سنبحث أكثر في كلا هذين الطلبين. لقد قمنا ببعض التحقيق الأولي لإظهار المعلومات العالمية.
نود أن نسمع المزيد من التعليقات حول الميزة. لا تتردد في ترك تعليقات أثناء استخدامك لهذه الميزة. ستساعد ملاحظاتك في تحسين الأداة.
Previous updates
| ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
 جرى الآن نشر ميزة معلومات IP على testwiki كميزة تجريبية. تتمثل الخطة في تشغيل الاختبار الأولي على testwiki حتى منتصف أبريل، وبعد ذلك، إذا لم نكتشف أي مشكلات رئيسة، فستكون الميزة متاحة في جميع المشاريع. فيما يلي بعض الأشياء الأساسية التي يجب ملاحظتها أثناء تجربة الأداة. يسار|600x600px المعلومات الأساسية مقابل المعلومات المتقدمة' There are two levels of access to IP information. Users with Autoconfirmed will be able to access the Basic information. Users with advanced privileges (admin, sysop, bureaucrat, checkuser) will be able to access the Advanced information. Advanced information includes City, State, ISP, Organization + Basic. Everything else displayed in the above screenshot will be available in Basic. If you want to try the advanced information mode on testwiki, please request for temporary admin privileges on the discussion page. Access In order to activate IP Info the user will need to agree to a disclaimer stating that this information is being accessed for anti-vandalism purposes only. Once activated, the user will be able to access both the IP Info popup (on log, history and recent changes pages) and the IP Info infobox (on contributions page). There will be a log to keep track of how IP information is being accessed. This is purely for Legal purposes. Only WMF Trust & Safety staff will have access to this log for the time being. Popup & Infobox There are two places to access this information: the popup and the infobox. The popup is intended to be a quick way to access specific IP details which can help while patrolling on the recent changes, log or history pages. The full infobox will be available on Special:Contributions. Clicking on the popup will lead to the infobox. Feedback When the tool is available on all projects there will be a link to provide feedback directly through the feature itself. This will allow for structured feedback to be collected in multiple languages. In the meantime, please reach out to us on the talk page and provide feedback. We want to hear from you about:
Future There are a couple of potential future feature improvements that we have in mind:
We don’t have a firm timeline for when we will be working on these. We want to ensure the tool is useful in its current state before adding new features. Our top priority is to build a feature that patrollers across different projects use and find helpful. اختتم فريق أدوات مكافحة التحرش مؤخراً عمله على إجراء تغييرات رئيسة على نظام (SecurePoll) والمساعدة في انتخابات مجلس أمناء مؤسسة ويكيميديا 2021. لقد عدنا إلى العمل على معلومات بروتوكول الإنترنت ونأمل أن تشهد هذه الصفحة العديد من التحديثات في المستقبل القريب. منذ أن غادرنا، نرفد لكم التحديثات الكبيرة على هذا المشروع:
يمضي العمل في تطوير ميزة معلومات بروتوكول الإنترنت على قدم وساق. ونستغل هذه الفرصة لإبلاغكم بالذي وصلنا إليه والحصول على رؤيتكم لهذا التوجه.
We conducted user interviews to understand how editors currently patrol IPs. This gave us a rough understanding of the IP patrolling process, information required and tools used. Based on this research we came up with a model of how the task of IP patrolling is usually conducted. After a few rounds of feedback from design, engineers, research and T&S folks here is what we came up with:  As we understand it now, the IP patrolling process usually starts from RecentChanges, an editor’s Watchlist or from a page that the editor knows gets vandalized often. When looking at the edits of such a page the patroller first looks for clear red flags like edit flooding, lack of edit summary, large deletions etc. They then look for more specific on-wiki information like if the IP has a talk page, if it has ever been blocked in the past, its global and local contributions, and in the case of English Wikipedia, if there is a mention of the IP on the LTA page. Based on this initial research they decide if an IP is worth looking into further. If it is, they use external tools to find more information about the IP, like: location, proxy usage and organization that the IP might be linked to. This process is not completely accurate since different databases have different information on the same IP. Oftentimes, based on the location of the IP and the location of the IP tool, the information given might be very different. Finally, based on the information collected they decide which action would be most appropriate. Again, this decision takes into account various factors like the policies of that wiki, the scale of the collateral damage caused by a range block, consistency in editing patterns etc.
Based on feedback from the first round of user interviews, we have settled on the following product approach.
Since the patrollers need on-wiki information about the IP before they decide to investigate it we are going to add a popup that shows block and contribution information. The popup would be accessible by clicking an information icon next to the IP address on pages like RecentChanges, Watchlist and History. If the patroller decides to dig deeper into an IP address by going to their Contributions page, they'll be able to see a collapsible box that shows more IP related information.
By making the IP information so readily available we hope to remove some of the barriers that our non-technical patrollers might be facing in reliably getting this information. At the same time, we hope this streamlines the process for users who are currently relying on external tools. We also recognize that easy access to this information might be putting our anonymous editors at risk, especially because some of the IP information, like location and organization, can easily help in identifying a person. We need to balance the concerns of ease of use and risk to anonymous editors. To do this we plotted the different pieces of IP information on a graph with Risk on the Y axis and Usefulness to patrolling on the X axis:  This exercise wasn't completely scientific and was based on the learnings from research and estimates of the team (please see the questions below if you'd like to contribute). Two possible clusters appeared, the high risk one mostly containing information that could reveal an editor’s location. We are planning to show all on-wiki information to all editors that are auto-confirmed and above. Auto-confirmed and above editors will also have access to IP information that doesn't reveal possibly personal information about anonymous editors. This would include things like proxy and static/dynamic-ness of the IP. Finally, Admins and Checkusers will have access to more IP information like location, organization and domain.
The project is currently under backend development as we are looking into sources to pull IP Information from and what kind of information we should display and to whom. Here's a tentative mockup for the feature. We are currently planning to place the information box containing IP address information on the Contributions page of the IP address. We are also planning to break down the information that's visible to the users based on their permissions. All autoconfirmed users and above would be able to access this. This would mean more sensitive information would be accessible to users with advanced permissions like Admins, Checkusers etc.  As you look at this mockup, I'd invite you to think about the following:
Please leave your thoughts on the talk page. It will be very valuable as we plan our work.
|
- ERROR!
- ERROR!
- Easier patrolling: Patrollers don't need to copy-paste IP addresses to external tools. They also don't need to extract the information. This means lesser manual work.
- Faster patrolling: It saves patrollers' time by giving them the information they need readily in the interface.
- Higher reliability: The Foundation can have contracts with providers of reliable datasets, which are translated and updated regularly. This feature may be more reliable than some websites users were dependent on.
Lower technical barriers: It is useful for new admins and checkusers. Now, they don't need to have a very good understanding of how to extract information from IP addresses.
- ERROR!
Privacy risk: Not everyone is aware of what an IP address string reveals. Many people don't know that unregistered editing leaves a fingerprint which can be used to track them. A lot of registered editors do not know this either. This leads to unintentional privacy for unregistered users (Security through obscurity). Depending on who gets to see the information exposed by this feature, there is a risk of more users seeing the data than before.
Background: how do the communities use IP address information?
Anti-vandalism
See also: Research:Patrolling on Wikipedia/Report
Single-address blocks bar a single IP address from editing. Administrators can also block IP ranges. This is helpful for dynamic IPs or covering a small range often used for vandalism. To assess collateral damage, administrators should check the coverage of ranges they intend to block.
How administrators handle certain IP blocks depends on the type of address. For example, they handle an edit from an IP address coming from a residential area differently to an edit from an IP registered to a government. If an IP address is registered to a school or a university, administrators apply dedicated templates. If the institution was blocked before, they instruct how to contact them. Then, they help the institution get around the block. These templates can also be used pre-emptively. The goal may be to clear up potential confusion at receiving messages not meant for the user. Another goal may be to point to features only available to registered users.
The IP blocking workflow relies on some IP information. This usually is the registered organization, geographic location, and autonomous system number. This information comes from third-party IP information providers, with no standard service. There are different degrees of accuracy and reliability.
IP addresses are also used in AbuseFilter to make very specific blocks. The goal is highlight some abuse without disrupting the experience of regular users.
IP information is also used by CheckUsers. In particular, they use it whe they deal with alternate account abuse (sockpuppeting). Their tools allow access to potentially-identifying information tied to accounts. These usually do not have their IP addresses exposed.
Anonymity and anonymous editing
Researchers have attempted to determine the effects of unregistered editing on the projects. They have focused on links between anonymity and vandalism. In principle, unregistered users make large portions of constructive edits. A 2013 study noted that about 100,000 anonymous editors made roughly a third of the edits counted in that month. A 2016 study showed that unregistered users "contribute substantially to overall productivity".
No project has disallowed all unregistered user edits. But unregistered users are restricted in what types of contributions they can make. For example, they cannot start new articles or upload files on most of our projects. What's more, there is no guarantee that the person behind a given IP address will be the same every time. This makes it difficult for unregistered users to communicate. It also prevents them from joining their wikis' communities.
Research
Researchers sometimes use IP addresses to learn about the editing practices of users in a given geographic area. Researchers generally only use aggregate information from IPs.