Page MenuHomePhabricator

Potentially semi-protecting all properties: best approach?
Open, Stalled, Needs TriagePublic


There is an ongoing discussion at If the Wikidata community decides to protect properties so that they can only be edited by autoconfirmed users, what would the best/most efficient technical solution to implement this be? Some proposed options are:
A) via the AbuseFilter
B) $wgNamespaceProtection
C) Protect properties individually (e.g., by bot)

Event Timeline

Mike_Peel created this task.Jun 2 2020, 9:03 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 2 2020, 9:03 PM

$wgNamespaceProtection could be a good option
AbuseFilter and bot protection should probably not be used if the idea is to protect all properties.

We also currently have a user right for altering property terms which could be useful?

Change Property terms (labels, descriptions, aliases) (property-term)

This wouldn't cover changes to statements (but adding that user right could also be an option?

Jasper added a subscriber: Jasper.Jun 3 2020, 7:44 PM

I agree with Addshore: the abuse filter's performance should not be hindered by this kind of "namespace" protection. $wgNamespaceProtection is what's needed here.

In my opinion, if you have no business altering property terms, you have no business editing that property at all. But that should be made the subject of an additional discussion, and thus isn't quite in scope of this request.

@Addshore The property-term user right is something that would have to be granted so that people could edit property labels, right? I think that's going too far for now as it would have to be given to quite a few editors. $wgNamespaceProtection sounds good.

Agreed. Let's go with $wgNamespaceProtection. So I take it you'd like us to set this to allow the Property namespace to be only editable by autoconfirmed users, correct?

@Lydia_Pintscher Yes, editable by autoconfirmed users. The discussion is still ongoing, and I'm not quite sure how to close it, see

Lydia_Pintscher changed the task status from Open to Stalled.Jun 6 2020, 5:50 PM

Cool :)
I'm setting this to stalled then pending closing of the discussion. Please set it to open once you feel we can move forward.