Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Page MenuHomePhabricator

ruwiki user runs into $wgRateLimits rate limit when editing
Closed, InvalidPublicBUG REPORT

Description

Copy from VRT [[ticket:2024112610011561]]

What happens?:
A person cannot edit Wikipedia, he gets a message "Вы исчерпали установленное для борьбы со злоупотреблениями ограничение на количество выполнений запрошенного действия за короткий промежуток времени. Пожалуйста, повторите попытку через несколько минут." (I'm not sure how it should be in original, something like 'You have reached the anti-abuse limit on the number of times the requested action can be performed in a short period of time. Please try again in a few minutes.')
He tried edit from IP, from an account, in different ways, but since 1 ноября 2021 (since his registrarion) he has been able to do just two edits (https://ru.wikipedia.org/wiki/Special:Contributions/Демин_М.)

Something similar was discussed on https://ru.wikipedia.org/wiki/Википедия:Форум/Архив/Технический/2023/06#Фильтр_правок , but there wasn't any conclusion (and the person is sure that he is editing once at a time and not anonymously).

What should have happened instead?:
Wikipedia should be an encyclopedia that anyone can edit.

Event Timeline

Aklapper changed the task status from Open to Stalled.Dec 2 2024, 1:01 PM
Aklapper updated the task description. (Show Details)
Aklapper removed a project: Russian-Sites.

Does this also happen on other Wikimedia wikis, or only on Russian Wikipedia?

Sorry, I tried to edit "Russian-Sites" only.

Message in English is "actionthrottledtext": "As an anti-abuse measure, you are limited from performing this action too many times in a short space of time, and you have exceeded this limit.\nPlease try again in a few minutes."
Sounds like you run into the $wgRateLimits setting.
This sounds a bit like https://translatewiki.net/wiki/Thread:Support/Increase_tolerance_of_anti-abuse_measure (though not for translations).

Aklapper renamed this task from Publishing VRT [[ticket:2024112610011561]] to ruwiki user runs into $wgRateLimits rate limit when editing.Dec 3 2024, 9:21 AM
Aklapper changed the task status from Stalled to Open.
Aklapper updated the task description. (Show Details)

This task is not actionable in the Wikimedia-Site-requests board (and hence will languish indefinitely) unless there's a local on-wiki consensus to raise the rate limits and a new specific value to set them to.

Pppery changed the task status from Open to Stalled.Dec 4 2024, 6:52 PM
Pppery moved this task from Unsorted to Single wikis on the Community-consensus-needed board.

If you want to solve this user's problem, no setting need to be changed. A sysop assigning that user "confirmed" group is enough.

Boldly closing per last two comments (thanks for the additional info!)

The tags are wrong, but the task closure is also wrong: the problem isn’t that $wgRateLimits is configured a certain way, the problem is that they are getting triggered even though the user is clearly not in the wrong here. It is clearly some sort of bug. This should’ve been investigated further, not speedily denied.

The tags are wrong, but the task closure is also wrong: the problem isn’t that $wgRateLimits is configured a certain way, the problem is that they are getting triggered even though the user is clearly not in the wrong here. It is clearly some sort of bug. This should’ve been investigated further, not speedily denied.

More likely the user is using an IP shared with many people and up to 8 edits from non-confirmed users per minute can be made from single IP. Adding confirmed to the user will help in this case

More likely the user is using an IP shared with many people and up to 8 edits from non-confirmed users per minute can be made from single IP. Adding confirmed to the user will help in this case

Hello,

As a CU I can say that the IP is not shared. The affected user is completely alone there.

matmarex subscribed.

I investigated, looked up this user in the ratelimit log channel and confirmed that the rate limits are working correctly, and this is not a bug. The IP that they are connecting from has a reduced limit for security reasons. As already suggested above, you can add them to the "confirmed" user group to let them bypass this limit.

I investigated, looked up this user in the ratelimit log channel and confirmed that the rate limits are working correctly, and this is not a bug. The IP that they are connecting from has a reduced limit for security reasons. As already suggested above, you can add them to the "confirmed" user group to let them bypass this limit.

(You can link to the Phab task for reference purpose even if it may be security protected and most subscribers can not see)

Good point, the relevant task is T326691.

@matmarex The IP that they are connecting from has a reduced limit for security reasons. - shouldn't this be explicitly stated on a contributions page of this IP? Where this could be discussed by all users (not in closed ticket), appealled and revoked? I think, this shouldn't be something we learn about on random phab ticket, this shadow bans should be more transparent for users in local communities.

@MBH Making the details public would make the anti-abuse restrictions easier to evade, but they are known to the stewards elected by the community, and to the WMF Security team.