Page MenuHomePhabricator

Expose actor IDs via the API
Open, Needs TriagePublic

Description

To people working with the MediaWiki API, exposing an actor_id field (as a prop of various lists, as a parameter of various actions currently accepting a user, etc.) would be useful for some of the same reasons as detailed in T167246 for MediaWiki internally: mainly, that we wouldn’t need as much storage space to manage information on “ones who act on a wiki”, and could use plain 64-bit integers instead of variable-size user (name) strings or (user, user_id) tuples.

My concrete use case is that in the SpeedPatrolling tool, I want to maintain a list of users whose edits should not be shown to the tool user anymore. Since the tool is concerned with unpatrolled changes, those users will often be anonymous, so I can’t use the user_id alone. However, storage space in the user’s session is limited, so I can’t store as many users as user strings or (user, user_id) tuples as I could store actor_ids. (There are various ways to work around this, of course, we don’t need to get distracted discussing those – this is just supposed to be a motivating example.)

(I don’t know if this is already planned as part of T188327 anyways, but I couldn’t find any reference to it on Phabricator, so I’m creating this task.)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 3 2019, 1:59 PM
Anomie added a subscriber: Anomie.

There's currently no plan to do so; I thought there was a reason why not, but I can't find it now. I may be confusing it with CommentStore comment IDs, which are intended to be internal and not exposed via the API.

Nirmos added a subscriber: Nirmos.Feb 5 2019, 1:22 AM