Wikidata:Bureaucrats' noticeboard/Archive/2020/06

From Wikidata
Jump to navigation Jump to search
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Pintoch

@Ymblanter: Per Wikidata:Requests_for_comment/Reforming_the_property_creation_process#Admin_activity, creating properties will count as an administrative action. So Pintoch will only meet the inactivity condition as of 1 September. Note I do not propose an reinstatement of adminship in this case as he seems no longer have an interest.--GZWDer (talk) 01:40, 2 June 2020 (UTC)[reply]

Indeed, it looks like property creation is not reflected in this count (which makes our job more difficult, but this is not the point now). Pintoch has made two administratve actions in December (and never since) but has created a bunch of properties in February. Comments on how to proceed are welcome.--Ymblanter (talk) 05:42, 2 June 2020 (UTC)[reply]
Unless Pintoch comes back, I don't think there is any benefit to regranting adminship now, only to remove it in a few months. I would propose:
  • If Pintoch returns before 1 September and requests to have their permissions restored, adminship be restored as a matter of policy, since it was removed accidentally
  • If Pintoch does not make any such request by 1 September, the rights stay removed, and a new RfA is needed
Just my $0.02. --DannyS712 (talk) 06:03, 2 June 2020 (UTC)[reply]
The stupid thing is that they are around, they have for example reacted on my message at their talk page.--Ymblanter (talk) 07:57, 2 June 2020 (UTC)[reply]
Hi, thanks for trying to get this right! I really do not mind losing those user groups, I am indeed no longer involved in these activities. So I am happy not to be an admin and not to be a property creator anymore. Thank you all for your work! − Pintoch (talk) 16:06, 2 June 2020 (UTC)[reply]
I think we can probably treat this as a resignation then and the appropriate clauses apply. --Rschen7754 18:03, 2 June 2020 (UTC)[reply]

Mass… waitings

Hello Bureaucrats,

I am editing populations with QS2 and, apparently, it will not happen in hours, but in days. Editing stops on a batch and I have to restart, no matter what time of day. I need to identify the problem and also to shorten the time as much as possible. Could you grant me flood for this operation, please? I will return the flag when finished. —Eihel (talk) 12:45, 3 June 2020 (UTC)[reply]

Hello Eihel, I am not certain the flag will help much, but I granted the flag for a week. Please remove it when you are done. Lymantria (talk) 14:41, 3 June 2020 (UTC)[reply]
Everybody doing more then 6 edits per minute is running into waits due to server lag, this issue is already there for months, and affects every tool. This should not be solved by giving the chosen few exceptional rights, but should be solved by the source of the issue. Edoderoo (talk) 19:49, 19 June 2020 (UTC)[reply]
This is the second time I have asked for this right, but I did not think it was an abuse, IMHO. On June 3, so after the granting of Flood, I had to start the batch again with a new csv file and the control of the last batch entries in WD (more than 6000 entries), because QS2 freezed. This facility was transformed into a work of Sisyphus. So, indeed, this right did not help much on June 3. I remember that there were other temporary batches, but the scrolling did not seem to me normal. Maybe User:Epìdosis also found a difference that day (if he remembers it).
The batch of June 5 worked normally and my environment did not change, the problem came from elsewhere. This is what I express above: I do not prevent anyone from editing on WD and I conform to the speed of everyone usually, but this request allowed me to remove a problem from the equation on the problem cited above. As a reminder, I could have let QuickStatementsBot do the work in the background, for me, at the same speed. Cordially. —Eihel (talk) 02:58, 20 June 2020 (UTC)[reply]
Interestingly, yesterday (June 20) and today the load is much more evenly distributed and the max lag always 1-2 sec. So something has changed or was fixed. It is unsatisfying to speculate, can someone give information? --SCIdude (talk) 08:30, 21 June 2020 (UTC)[reply]
IIRC the amazing annoying lags are from phab:T243701. — regards, Revi 18:13, 22 June 2020 (UTC)[reply]