Wikipedia Edit War Highlighter

WHAT IT DOES

This script analyzes Wikipedia article revision histories to detect potential edit wars. When you visit a Wikipedia article, the script fetches the revision history using Wikipedia's API and looks for patterns of rapid back-and-forth reverts, multiple reverts in a short time period, or unusually high edit frequency. A color-coded badge appears at the top-right corner showing the edit war risk level: Low (green), Moderate (yellow), High (orange), or Critical (red). The badge includes a summary of reverts detected, recent reverts, and rapid edits. A "View History" button opens the article's history page for deeper investigation. The sensitivity can be adjusted in the settings panel to control how aggressively the script flags articles.

WHERE IT RUNS

The script runs on all Wikipedia domains (*.wikipedia.org). It works on article pages (excluding special pages). It supports both desktop and mobile views.

HOW TO USE

After installation, the settings panel appears on the left side of the screen with the gear emoji (⚙️). Open the panel to configure the script:

- The "Show edit war indicator" toggle enables or disables the badge.

- Select a sensitivity level from the dropdown: "Low (fewer alerts)," "Medium (balanced)," or "High (more alerts)."

- Click "Refresh analysis" to manually re-analyze the current article.

- Click "Clear cache" to remove cached analysis data.

The badge appears automatically on Wikipedia articles. Click the ✕ button to hide it for the current session. Click "View History" to open the article's revision history in a new tab.

TECHNICAL SECTION — REAL MECHANISM

The script detects article pages by checking for #firstHeading and excluding special pages. The article title is extracted from #firstHeading. The script fetches up to 100 revisions using Wikipedia's API (action=query&prop=revisions&rvlimit=100). It analyzes each revision's comment, timestamp, size, and user. Reverts are detected by searching comments for keywords like "revert," "rv," "undo," and "rollback," and by detecting large size changes with comments containing "restore." Rapid edits are detected by comparing timestamps of consecutive revisions—if they fall within a configurable time window (based on sensitivity), they count as rapid. The risk score is calculated as reverts*3 + recentReverts*2 + rapidEdits*1, with a bonus for high total edit count. The sensitivity setting adjusts the time window for rapid edits and the score thresholds for each risk level. Results are cached for 10 minutes to avoid repeated API calls. The badge is rendered as a fixed-position div with a glassmorphism style, using style properties and textContent (never innerHTML).

THE PANEL

The settings panel is built with BotGentz's BGPanel component. It is draggable via its header, allowing you to reposition it anywhere on the screen. The panel snaps to the left edge by default but can be moved freely. Click the gear emoji to collapse the panel into a small bubble, and click the bubble to expand it again. The panel remembers its position per page session. Press the Escape key to quickly close or minimize the panel. The panel includes a status flash bar that provides visual feedback when settings are changed or actions are performed. All settings save automatically via GM_setValue.

PLEASE NOTE

This script requires the free BotGentz browser extension to run. It does not function as a standalone Chrome extension and does not use chrome.* APIs. The script uses Wikipedia's public API to fetch revision history. The analysis is heuristic-based and may produce false positives or false negatives—it is a helpful indicator, not a definitive judgment of edit war activity. Wikipedia frequently updates its page structure, which may affect the script's ability to detect article titles. If the badge stops working, please check for updates. The script caches analysis results for 10 minutes to reduce API calls. The script stores only your preferences via GM_setValue. No data is sent externally except for the Wikipedia API request. The script never reads or writes password fields, hidden inputs, or file inputs. All DOM operations use safe methods (style properties, textContent, appendChild) and never use innerHTML.