Community Wishlist Survey 2021/Wikidata/Slow and fast edits
The survey has concluded. Here are the results!
Slow and fast edits
- Problem: WDQS is overloaded by a number of edits, many of them are unimportant.
- Who would benefit:
- Proposed solution: We introduce a new parameter "slow" which will deprioritize change dispatch/WDQS. See d:User_talk:BrokenSegue/API_Proxy#New_"slow"_parameter.
- More comments:
- Phabricator tickets:
- Proposer: GZWDer (talk) 06:20, 26 November 2020 (UTC)
- Support Sounds easy enough to implement. Also easy to game, but it would lift the bar. Can you run some numbers on potential impact? Dagelf (talk) 08:14, 9 December 2020 (UTC)
- Support Jcwang1986 (talk) 08:56, 9 December 2020 (UTC)
- Oppose (to make a remark here); "unimportant" is a highly subjective classification; I think we should not even try to rate edits or user activity for their "importance" as this might easily alienate those whose edits are found to be "unimportant". —MisterSynergy (talk) 09:01, 9 December 2020 (UTC)
- Support MisterSynergy, I think this is supposed to be a thing people decide for themselves when they start their batch--"my batch can go slow" Abductive (talk) 09:18, 9 December 2020 (UTC)
- Support Thomas Kinz (talk) 21:34, 9 December 2020 (UTC)
- Oppose - This proposal is far too broad and not properly worked out. Husky (talk) 16:16, 11 December 2020 (UTC)
- Support should be doable using in example with tags and it would work as hint for WQS updater that which updates can be batch update later. --Zache (talk) 19:00, 11 December 2020 (UTC)
- Oppose - less is more many times small edits may be important and so underestimated: see MisterSynergy's comment as well, Klaas `Z4␟` V: 14:58, 12 December 2020 (UTC)
- Oppose --Jarekt (talk) 15:20, 12 December 2020 (UTC)
- Support Kartsriv (talk) 17:24, 19 December 2020 (UTC)