Page MenuHomePhabricator
Feed Advanced Search

Today

AronManning added a comment to T240360: Determine our approach for v1.0 for displaying date and time a comment was made, in a user's local timezone and preferred date format.

Personal views:

  1. I think "Browser-local time" should be a preference for "Time zone" and used only if that's the chosen setting. Could be the default setting, though for new users. Disclosure: I use UTC, not local time (possible bias).
    • Currently there's only a "Fill in from browser" option, that grabs the browser's time offset (that includes the current day-light saving) and stores as a setting. That setting does not follow day-light and timezone changes, therefore it's not really useful.
  2. I often copy the date-time, including timezone to refer to specific comments/diffs or to search for the time in the history. For these usages consistency of the comment timestamps and history timestamp is important, both should follow the wiki preference.
  3. Showing the relative time by default and the absolute time (wiki preference / UTC) on hover is common in messaging software and quite convenient in Flow. However, the tooltip popup solution of reddit is not so convenient imo.
    • It would be a nice feature to have with a setting that enables it (could be enabled by default for new users). Note: I actually don't use it, but I know editors who have some script to do this for talk page comments.
    • The user should be able to easily select and copy the absolute time. If the presentation changes on hover, there should be some padding to allow for the mouse pointer to move past the last character. Currently, in Flow the user has to stop moving the mouse precisely after the last (first) character.
  4. Communicating using UTC in global communities is common. There should be an option to show the time in UTC zone on hover, regardless of the wiki preference and whether relative time is shown by default.
Thu, Dec 12, 12:07 PM · VisualEditor (Current work), Editing Design, Editing-team, OWC2020
AronManning added a comment to T218626: [Epic] Partial block rollout.

Will this be rolled out on en.wiki without an RfC or if the RfC closes opposed?

Thu, Dec 12, 6:34 AM · Epic, MediaWiki-User-management, User-notice, Wikimedia-Site-requests, Anti-Harassment

Yesterday

AronManning added a comment to T160233: Enable administrators to update block logs.

@DannyS712 I've looked at the patch set. Please correct me if I'm wrong: as I see you've implemented the "make comment-only entries in block logs" proposal, that adds a new entry without modifying previous entries, thus only the user's visible block reason is changed. I don't see any changes to the block log (Special:Log/block) in the patchset, therefore the previous log entries (and the annotation entries) are all visible there, unmodified.

Wed, Dec 11, 12:57 AM · Anti-Harassment, Core Platform Team Workboards (Clinic Duty Team), Patch-For-Review, User-DannyS712, MediaWiki-Logging, MediaWiki-User-management, Community-Wishlist-Survey-2016

Tue, Dec 10

AronManning added a comment to T218626: [Epic] Partial block rollout.

I don't get why the Wikimedia Foundation doesn't just implement this by default, what would we truly lose if partial blocks were implemented? Admins aren’t forced to use them when they don't want to, “giving the community a choice” just means that they (we) could prevent something that's a net benefit to it.
In fact, policies are written around the technical capabilities and limitations of the MediaWiki software, not vice versa. There is literally not a single reason why a piece of software that doesn't limit anything possible today but only expand it should not just be enabled by default, if partial blocks had the potential to damage the workflow of the community I could understand that it would require prior discussion, but this is unnecessary bureaucracy.

Tue, Dec 10, 10:09 PM · Epic, MediaWiki-User-management, User-notice, Wikimedia-Site-requests, Anti-Harassment
AronManning moved T240313: Partial Block UI: Pop-up editor for long lists of pages from Backlog to User blocking on the MediaWiki-User-management board.
Tue, Dec 10, 6:10 AM · MediaWiki-User-management
AronManning created T240313: Partial Block UI: Pop-up editor for long lists of pages.
Tue, Dec 10, 6:07 AM · MediaWiki-User-management
AronManning updated the task description for T119795: Add new user block option "can edit Wikipedia:Appealing_a_block" .
Tue, Dec 10, 5:54 AM · MediaWiki-General
AronManning updated the task description for T27400: Software should allow admins to give specific users permission to edit specific pages through blocks (whitelist).
Tue, Dec 10, 5:52 AM · MediaWiki-User-management
AronManning updated the task description for T240311: Partial Block UI: White-list of pages allowed to edit for site-wide blocks.
Tue, Dec 10, 5:51 AM · MediaWiki-User-management
AronManning updated the task description for T240311: Partial Block UI: White-list of pages allowed to edit for site-wide blocks.
Tue, Dec 10, 5:50 AM · MediaWiki-User-management
AronManning updated the task description for T27400: Software should allow admins to give specific users permission to edit specific pages through blocks (whitelist).
Tue, Dec 10, 5:49 AM · MediaWiki-User-management
AronManning added a subtask for T204903: Epic ⚡️ unprioritized Partial Blocks features: T240311: Partial Block UI: White-list of pages allowed to edit for site-wide blocks.
Tue, Dec 10, 5:44 AM · Anti-Harassment
AronManning added a parent task for T240311: Partial Block UI: White-list of pages allowed to edit for site-wide blocks: T204903: Epic ⚡️ unprioritized Partial Blocks features.
Tue, Dec 10, 5:44 AM · MediaWiki-User-management
AronManning created T240311: Partial Block UI: White-list of pages allowed to edit for site-wide blocks.
Tue, Dec 10, 5:43 AM · MediaWiki-User-management
AronManning added a subtask for T204903: Epic ⚡️ unprioritized Partial Blocks features: T240310: Partial Block UI: List articles recently edited by the user.
Tue, Dec 10, 5:38 AM · Anti-Harassment
AronManning added a parent task for T240310: Partial Block UI: List articles recently edited by the user: T204903: Epic ⚡️ unprioritized Partial Blocks features.
Tue, Dec 10, 5:38 AM · MediaWiki-User-management
AronManning created T240310: Partial Block UI: List articles recently edited by the user.
Tue, Dec 10, 5:37 AM · MediaWiki-User-management
AronManning updated the task description for T194697: Multiblocks — Allow for multiple, simultaneously blocks with different expiration dates..
Tue, Dec 10, 5:21 AM · MediaWiki-User-management

Fri, Dec 6

AronManning added a comment to T239680: CU 2.0: Persist the form state.

Sorry, I'm confused, let me try and clarify for my own mental image; why would going from "submit" and into any of the "sub" details ("compare" vs details, etc) be another check?

The "Submit" button brings up the "Preliminary check" tab. As I understand the purpose of that is to not run the actual check (thus no cu log entry created). The first query is run when the "Compare" or "Timeline" tab is opened. I think the UI workflow is a bit confusing, as there is no big button that actually runs the check, or I am misunderstanding the proposed workflow.

Fri, Dec 6, 2:42 PM · Patch-For-Review, CheckUser, Anti-Harassment (The Letter Song)
AronManning added a comment to T239680: CU 2.0: Persist the form state.

CU log entries and CU investigations have a 1-1 relation. Calling it a "log" is arbitrary, reflecting the original use-case. Maybe calling it "CU investigations" in the DB would be more appropriate while calling it "CU log" on the UI.
I see only one limiting factor with the current cu_log table: cul_user is an N-1 relation, that cannot accommodate for multiple users checked in one investigation. That will require a new table (schema change).

Naive question: Is it a problem if we add multiple rows per the same investigation to this log?
Technically, it seems to me that this is more or less what is already done, isn't it? If an investigation about a certain IP reveals multiple users, that then require
individual "attention" by the checker, they'll review each (relevant) username, yet the investigation itself is for a single purpose.

I used the wrong word "investigation", I meant "check". An investigation might require more checks. I'm editing that comment to fix this.

Fri, Dec 6, 5:13 AM · Patch-For-Review, CheckUser, Anti-Harassment (The Letter Song)
AronManning added a comment to T239680: CU 2.0: Persist the form state.

To authorize a subsequent request (sorting/paging), checking the existence of a CU log entry (with the CU user, check timestamp, target users) should be necessary and sufficient.

Well that's an interesting idea... feels like a bit of an "abuse" of a log (i.e. I think an application should function even if logging is unavailable)... but certainly not unprecedented.

Fri, Dec 6, 4:23 AM · Patch-For-Review, CheckUser, Anti-Harassment (The Letter Song)
AronManning added a comment to T239680: CU 2.0: Persist the form state.

I'm going to explore tokenizing/signing the request. It looks like we are already using a JWT library in production so I can't imagine why it would be an issue to reuse that.

Fri, Dec 6, 2:49 AM · Patch-For-Review, CheckUser, Anti-Harassment (The Letter Song)

Wed, Dec 4

AronManning added a comment to T237300: CU 2.0: Sorting in the Compare tab.

A few thoughts on the implementation:

Wed, Dec 4, 9:34 PM · Anti-Harassment (The Letter Song), CheckUser
AronManning added a comment to T239680: CU 2.0: Persist the form state.

Persistence across tabs -- PHP sessions are stored per browser (not tab) so they persist across tabs. Is that okay?

Wed, Dec 4, 9:07 PM · Patch-For-Review, CheckUser, Anti-Harassment (The Letter Song)

Mon, Dec 2

AronManning added a comment to T238714: CU 2.0: Fetch information to be displayed in Compare tab.

Where do unregistered edits on that IP fall? is that part of the 10 edits from 3 other users or do we want to exclude those?

I assumed the IP would be one of the users, though I suppose it depends on how you interpret the word "user."

Mon, Dec 2, 5:15 PM · Patch-For-Review, Anti-Harassment (The Letter Song), CheckUser

Thu, Nov 21

AronManning added a comment to T175587: Add a user-agent parser to CheckUser.

To parse
WikipediaApp/2.7.50296-r-2019-09-25 (Android 5.0.2; Phone) Google Play
add to
https://github.com/WhichBrowser/Parser-PHP/blob/master/data/applications-others.php
Constants\BrowserType::APP_EDITOR => [
To parse version with date:

[ 'name' => 'Wikipedia',            'id'    => 'wikipedia',   'regexp' =>'/WikipediaApp\/([0-9.r\-]*)/u' ],

without date:

[ 'name' => 'Wikipedia',            'id'    => 'wikipedia',   'regexp' =>'/WikipediaApp\/([0-9.]*)/u' ],

only date:

[ 'name' => 'Wikipedia',            'id'    => 'wikipedia',   'regexp' =>'/WikipediaApp\/[0-9.]*-(r[0-9\-]*)/u' ],

(not tested)

Thu, Nov 21, 9:03 PM · Anti-Harassment, CheckUser
AronManning added a comment to T175587: Add a user-agent parser to CheckUser.

As a non-wm CU my order of evidence strength is (decreasing):

  1. obviously fabricated UA (uncommon, only trolls do that), 2) same UA 3) browser version increased (update) 4) same device and OS, different browser 5) different UA

The strength of the CU match adds up with the strength of the IP match:

  1. same IP in a short timeframe or static IP 2) same subnet, if there aren't many users from the subnet/ISP 3) if accounts use IPs from random countries, that's unlikely to be due to travel 4) IPs reported as proxy/vpn
Thu, Nov 21, 4:19 PM · Anti-Harassment, CheckUser
AronManning added a comment to T237034: CheckUser 2.0: Input form.

@JJMC89 Yes, requiring a link to the cause is unnecessary for private/small wikis. Thanks for mentioning this.
It only matters on wikimedia wikis, where there are strong guarantees of privacy.
@Niharika It can be enabled with a flag in the configuration.

Thu, Nov 21, 3:42 AM · MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser

Wed, Nov 20

AronManning added a comment to T175587: Add a user-agent parser to CheckUser.

The full UA can be displayed as a mouseover popup of the "Browser" field (title="<UA>") and also copied to the clipboard for further analysis when the field is clicked.
Whenever pattern-matching the UA fails the "Browser" column can display "Unknown", or the first ca. 20 characters of the UA with a different color. The user will mouseover to see the actual UA.
This might become tedious if there are more, that failed parsing, eg. more than 3. In that case (or in all cases) an extra column can be shown with all the full UA strings.
This column will likely overflow the screen and require horizontal scrolling.

Wed, Nov 20, 12:46 AM · Anti-Harassment, CheckUser
AronManning added a comment to T237034: CheckUser 2.0: Input form.

@Niharika the field is short for a textual description and a link. Either a longer 2-line textfield or 2 fields would be enough.
In any case, the comments should instruct to paste the link to the cause and form validation should check its presence.
The check is a bit simpler with a separate field, but it is less busy with one longer field.

Wed, Nov 20, 12:19 AM · MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser

Mon, Nov 18

AronManning added a comment to T237034: CheckUser 2.0: Input form.

The cause of doing CU is often an SPI or a user request or suspicious edit. In any case, the reason should link to this cause and the form should require this link for the reason.
Would a separate field for the link be better or a two-line reason field?
With two separate fields I think it would be cleaner:

Mon, Nov 18, 8:28 PM · MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser

Sat, Nov 16

AronManning added a comment to T213451: Review Special:Block design once partial blocks are more fully implemented.

3 suggested improvements to the partial blocking UI:

Sat, Nov 16, 11:26 AM · Anti-Harassment, MediaWiki-User-management

Nov 8 2019

AronManning added a comment to T236981: CheckUser 2.0: Create a new Special page in CheckUser for the redesigned version.

Imo CheckUserTest or CheckUserDev or CheckUserAlpha. I assume when it goes to production (new version enabled in config) it will replace the current CheckUser and this in-development name will be dropped.

Nov 8 2019, 4:06 PM · Patch-For-Review, MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser

Nov 7 2019

AronManning added a comment to T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses.

Besides subnet (whois) and geolocation, presenting Proxy/VPN data would be useful for CU. Example: https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/86.187.160.157
This data is no more reliable than Geoloc data, yet it is a good clue for determining the likelihood of a proxy user.

Nov 7 2019, 9:16 AM · User-Daimona, Patch-For-Review, User-Huji, MediaWiki-extension-requests, Stewards-and-global-tools, MediaWiki-extensions-LoginNotify, CheckUser
AronManning added a subtask for T237593: [Epic] CheckUser 2.0: Compare: T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.
Nov 7 2019, 9:09 AM · Epic, Anti-Harassment, CheckUser
AronManning removed a subtask for T237595: [Epic] CheckUser 2.0: Timeline: T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.
Nov 7 2019, 9:09 AM · Epic, Anti-Harassment, CheckUser
AronManning edited parent tasks for T234980: Implement an option to highlight non-standard user-agent strings in CheckUser, added: T237593: [Epic] CheckUser 2.0: Compare; removed: T237595: [Epic] CheckUser 2.0: Timeline.
Nov 7 2019, 9:09 AM · CheckUser
AronManning added a comment to T237595: [Epic] CheckUser 2.0: Timeline.

^^^^ For description.

Nov 7 2019, 9:07 AM · Epic, Anti-Harassment, CheckUser
AronManning updated subscribers of T237593: [Epic] CheckUser 2.0: Compare.
Nov 7 2019, 8:45 AM · Epic, Anti-Harassment, CheckUser
AronManning added a comment to T237593: [Epic] CheckUser 2.0: Compare.

A more substantive task.
Add 3 columns: Subnet (name and ip range of the subnetwork), Geolocation (closest city, generally), Proxy/VPN (reported/detected proxies)
This would greatly increase the efficiency of recognizing IPs from around the world (VPN users), dynamic ips on the same subnet, open proxies/free VPNs, etc.

Nov 7 2019, 8:29 AM · Epic, Anti-Harassment, CheckUser
AronManning added a comment to T237593: [Epic] CheckUser 2.0: Compare.

@Niharika ^^^^ for Description.

Nov 7 2019, 8:01 AM · Epic, Anti-Harassment, CheckUser
AronManning added a comment to T236981: CheckUser 2.0: Create a new Special page in CheckUser for the redesigned version.

There is a new blank/hello-world special page created by the CheckUser extension, titled CheckUser 2.0 behind a feature flag

Nov 7 2019, 7:30 AM · Patch-For-Review, MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser
AronManning added a comment to T237486: Organize tasks related to the overhaul of CheckUser.

@Niharika that's perfect. I've re-parented the leftover tasks in the tree above. Only the subtasks of T132892 (CheckUser UI revamp), the Orphans and the Old/stale tasks remain to be reviewed and anything I might have missed in the backlog. There were a few tasks that weren't obvious, so I'll run through the list once more and maybe you might be aware of a task I wasn't.

Nov 7 2019, 6:59 AM · CheckUser
AronManning removed a subtask for T132892: CheckUser UI revamp: T94735: Rewrite Special:CheckUser using server side templates.
Nov 7 2019, 6:55 AM · Design, Stewards-and-global-tools, CheckUser
AronManning edited parent tasks for T94735: Rewrite Special:CheckUser using server side templates, added: T236225: [Epic] CheckUser 2.0 Improvements ; removed: T132892: CheckUser UI revamp.
Nov 7 2019, 6:55 AM · Epic, Stewards-and-global-tools, CheckUser
AronManning added a subtask for T236225: [Epic] CheckUser 2.0 Improvements : T94735: Rewrite Special:CheckUser using server side templates.
Nov 7 2019, 6:55 AM · Epic, Anti-Harassment, CheckUser
AronManning removed a subtask for T139810: RFC: Overhaul the CheckUser extension: T146837: Add ability to search by user agent from CheckUser interface.
Nov 7 2019, 6:50 AM · Goal, Epic, User-notice, WMF-Legal, Trust-and-Safety, Stewards-and-global-tools, CheckUser
AronManning added a subtask for T237034: CheckUser 2.0: Input form: T146837: Add ability to search by user agent from CheckUser interface.
Nov 7 2019, 6:50 AM · MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser
AronManning edited parent tasks for T146837: Add ability to search by user agent from CheckUser interface, added: T237034: CheckUser 2.0: Input form; removed: T139810: RFC: Overhaul the CheckUser extension.
Nov 7 2019, 6:50 AM · Stewards-and-global-tools, CheckUser
AronManning added a subtask for T237034: CheckUser 2.0: Input form: T122296: Allow checking by last 64 bits of an IPv6 address.
Nov 7 2019, 6:49 AM · MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser
AronManning added a parent task for T122296: Allow checking by last 64 bits of an IPv6 address: T237034: CheckUser 2.0: Input form.
Nov 7 2019, 6:49 AM · IPv6, Stewards-and-global-tools, CheckUser
AronManning added a subtask for T237593: [Epic] CheckUser 2.0: Compare: T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses.
Nov 7 2019, 6:49 AM · Epic, Anti-Harassment, CheckUser
AronManning added a parent task for T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses: T237593: [Epic] CheckUser 2.0: Compare.
Nov 7 2019, 6:49 AM · User-Daimona, Patch-For-Review, User-Huji, MediaWiki-extension-requests, Stewards-and-global-tools, MediaWiki-extensions-LoginNotify, CheckUser
AronManning added a subtask for T237593: [Epic] CheckUser 2.0: Compare: T175587: Add a user-agent parser to CheckUser.
Nov 7 2019, 6:48 AM · Epic, Anti-Harassment, CheckUser
AronManning added a parent task for T175587: Add a user-agent parser to CheckUser: T237593: [Epic] CheckUser 2.0: Compare.
Nov 7 2019, 6:48 AM · Anti-Harassment, CheckUser
AronManning removed a subtask for T132892: CheckUser UI revamp: T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.
Nov 7 2019, 6:47 AM · Design, Stewards-and-global-tools, CheckUser
AronManning added a subtask for T237595: [Epic] CheckUser 2.0: Timeline: T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.
Nov 7 2019, 6:47 AM · Epic, Anti-Harassment, CheckUser
AronManning edited parent tasks for T234980: Implement an option to highlight non-standard user-agent strings in CheckUser, added: T237595: [Epic] CheckUser 2.0: Timeline; removed: T132892: CheckUser UI revamp.
Nov 7 2019, 6:47 AM · CheckUser

Nov 6 2019

AronManning removed a subtask for T139810: RFC: Overhaul the CheckUser extension: T24119: Enhance Blocking and tagging from checkuser interface: add new page.
Nov 6 2019, 8:43 AM · Goal, Epic, User-notice, WMF-Legal, Trust-and-Safety, Stewards-and-global-tools, CheckUser
AronManning removed a parent task for T24119: Enhance Blocking and tagging from checkuser interface: add new page: T139810: RFC: Overhaul the CheckUser extension.
Nov 6 2019, 8:43 AM · Stewards-and-global-tools, CheckUser
AronManning added a subtask for T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses: T36438: Reverse DNS lookup.
Nov 6 2019, 8:35 AM · User-Daimona, Patch-For-Review, User-Huji, MediaWiki-extension-requests, Stewards-and-global-tools, MediaWiki-extensions-LoginNotify, CheckUser
AronManning added a parent task for T36438: Reverse DNS lookup: T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses.
Nov 6 2019, 8:35 AM · Stewards-and-global-tools, CheckUser
AronManning added a comment to T237486: Organize tasks related to the overhaul of CheckUser.

I suggest the following tree to separate tasks expected to be done in 2019 (T132892: CheckUser UI revamp are tasks from 2016)

Nov 6 2019, 7:55 AM · CheckUser
AronManning added a subtask for T237039: [Epic] CheckUser 2.0: Preliminary check: T236981: CheckUser 2.0: Create a new Special page in CheckUser for the redesigned version.
Nov 6 2019, 6:42 AM · Epic, CheckUser, Anti-Harassment
AronManning added a parent task for T236981: CheckUser 2.0: Create a new Special page in CheckUser for the redesigned version: T237039: [Epic] CheckUser 2.0: Preliminary check.
Nov 6 2019, 6:42 AM · Patch-For-Review, MW-1.35-notes (1.35.0-wmf.8; 2019-11-26), Anti-Harassment (The Letter Song), CheckUser
AronManning added a subtask for T139810: RFC: Overhaul the CheckUser extension: T237039: [Epic] CheckUser 2.0: Preliminary check.
Nov 6 2019, 6:31 AM · Goal, Epic, User-notice, WMF-Legal, Trust-and-Safety, Stewards-and-global-tools, CheckUser
AronManning added a parent task for T237039: [Epic] CheckUser 2.0: Preliminary check: T139810: RFC: Overhaul the CheckUser extension.
Nov 6 2019, 6:31 AM · Epic, CheckUser, Anti-Harassment
AronManning added a comment to T237486: Organize tasks related to the overhaul of CheckUser.

Root: T139810 RFC: Overhaul the CheckUser extension
Hub/parent tasks with many subtasks:

  • T132892: CheckUser UI revamp
  • T237039: [Epic] CheckUser 2.0: Preliminary check
Nov 6 2019, 6:27 AM · CheckUser
AronManning added a subtask for T132892: CheckUser UI revamp: T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.
Nov 6 2019, 6:27 AM · Design, Stewards-and-global-tools, CheckUser
AronManning added a parent task for T234980: Implement an option to highlight non-standard user-agent strings in CheckUser: T132892: CheckUser UI revamp.
Nov 6 2019, 6:27 AM · CheckUser
AronManning updated subscribers of T132892: CheckUser UI revamp.
Nov 6 2019, 6:20 AM · Design, Stewards-and-global-tools, CheckUser
AronManning updated subscribers of T132892: CheckUser UI revamp.

https://prtksxna.github.io/wmf-cu-prototype/ (presented in T237039 - source) looks very good.

Nov 6 2019, 6:18 AM · Design, Stewards-and-global-tools, CheckUser

Oct 13 2019

AronManning awarded T122296: Allow checking by last 64 bits of an IPv6 address a Like token.
Oct 13 2019, 6:01 PM · IPv6, Stewards-and-global-tools, CheckUser

Oct 8 2019

AronManning added a watcher for CheckUser: AronManning.
Oct 8 2019, 7:45 PM

Oct 7 2019

AronManning added a watcher for Discourse: AronManning.
Oct 7 2019, 8:58 PM

Oct 6 2019

AronManning added a member for Anti-Harassment: AronManning.
Oct 6 2019, 10:46 PM
AronManning added a watcher for Anti-Harassment: AronManning.
Oct 6 2019, 10:45 PM
AronManning added a watcher for StructuredDiscussions: AronManning.
Oct 6 2019, 10:43 PM
AronManning added a comment to T166812: Epic⚡️ : User reporting system.

I haven't seen any information about the design / implementation of this system, so I've drafted a proposed workflow from creating a report all the way to decision making, in a process similar to an ArbCom case, that's applicable to simple, everyday reports as well.

Oct 6 2019, 10:24 PM · Anti-Harassment
AronManning awarded T234520: Flag edit(summary) as incivil a Like token.
Oct 6 2019, 10:03 PM · MediaWiki-General

Oct 4 2019

AronManning added a comment to T232415: mw-revision should be a warningbox.

Thank you to the devs for this update. Revision info is more noticeable now, while before I often missed it.
Much appreciated!

Oct 4 2019, 5:46 PM · MW-1.34-notes (1.34.0-wmf.25; 2019-10-01), User-notice, Notice, UI-Standardization

Sep 20 2019

AronManning added a comment to T129747: Proposal: allow a second email address (wikimail, password reset, notifications).

The motivation for this feature was to keep the private email address hidden, when sending email on-wiki. This can be achieved with an alternative solution that is simpler for the user, but might complicate configuring the server a bit.
A common solution to this problem is to give a wiki email address to users (such as username@en.wikipedia.org), and forward/proxy emails to the private address.
Emails sent on-wiki have the header field From: username@en.wikipedia.org
Replies (and any email) sent to username@en.wikipedia.org are only accepted from confirmed user email addresses (SPF / DKIM fields checked). This identifies the sender's username2 account.
The body of the email and a few header fields (Subject, Date, Content-Type, Content-Transfer-Encoding) are sent to the user's private address with Sender: username2@en.wikipedia.org
As a result editors only see the username of the sender. It's up to the editors to share their private email address, if they choose to.
"en.wikipedia.org" can be any wiki instance.

Sep 20 2019, 12:38 AM · Proposal, MediaWiki-User-preferences, MediaWiki-Email