Autoblock/zh

自动封锁是一个自动的封锁的IP地址，由MediaWiki软件做的. 自动封锁是企图从一个被封锁的用户最近使用的IP地址编辑Wiki的结果.

用户每次编辑Wiki，使用的IP地址连接到网站是由MediaWiki软件的权力Wiki记录. 日志的IP地址使用由每个用户是私人饲养的，只有通过用户查核员访问MediaWiki软件的用户可以访问. 当一个用户试图封锁网站的编辑，IP地址从他们的编辑是“自动封锁”具有相同的设置为阻止用户（随着时间的例外和阻止电子邮件），所以他们不可能做出相同的编辑匿名或不同的用户名下. 如果另一个用户试图使用自动封锁IP地址，他们是自动封锁为好，而且他们可能试图使用而阻止任何其他的IP地址，是自动封锁以及. 然后，其他使用那些IP地址的用户也可能被阻止，并继续前进. 在某些情况下，该系统可以螺旋和许多用户可能autoblocked即使他们没有blockworthy. As of September 2017, this does not happen. While logged in users can be affected by autoblocks, autoblocks do NOT propagate from IP addresses to accounts.

解封一位自动封禁的用户
如果一个用户自动封锁，例如如果一个命名用户解除封锁，但他们的IP地址仍然是自动封锁，管理员可以明确自动封锁的：


 * 回顾为列表Special:BlockList，搜索用户的帐户名称. 这是一个区分大小写的搜索. 
 * 确定关联的编号 #xxxxx. 如果搜索这个编号，请确保包含 "#" 号
 * 点击 "" 链接解除对 #xxxxx 的封禁

注意，一旦自动封禁被解除，这个用户的账户名将不再出现在列表里.

日志消息
有时“”一词将出现在封锁消息中. 这意味着当一个用户被封禁时，只有他们的用户名被封禁，但其他使用相同 IP 地址的用户依然可以自由地编辑.

封禁的默认设置是开启自动封禁，但不会明确地在封禁消息中提到这一点. 要禁用对一个账号的自动封锁，管理员必须要手动取消勾选 " " 复选框.

主功能


当自动封禁发生时，用户可能因为使用相同互联网服务提供商的另一个用户的行为而被封禁. 因此，不同的用户可能最终会被封锁，即使他们个人没有做错任何事情. 这被称为「附带损害」. 例子：


 * 用户:Susan，管理员，封禁用户:Bort为24小时 Susan 并不知道，Bort 使用 AOL 编辑维基，并且实施封禁的时候自动封禁是开启的.
 * 1) 用户 Steven，同样在家里使用 AOL，被分配到了 Bort 上次使用过的 IP 地址，然后登录了维基.
 * 2) MediaWiki 软件检测到 Steven 使用的 IP 地址，认定这是 Bort 的行为，以管理员 Susan 的名义，对 Steven 施行了 24 小时的封禁.  Susan 并没有收到此次封禁的通知. Steven 并没有真正被封禁，但因为自动封禁，他依然无法用他被新分配到的 IP 地址进行编辑.
 * 3) Steven 收到了「你被封禁了」的消息，并不知道什么是自动封禁，然后很愤怒，想知道管理员 Susan 为什么封禁了他.
 * 4) Steven 试图用他的工作电脑登录（并不使用 AOL）.
 * 5) MediaWiki 软件检测到 Steven 正在试图绕过封禁，并把他的工作 IP 地址也自动封禁了. 再一次地，Steven 并没有被封禁所以这并没有发生.
 * 6) Steven 的一位同事，正使用着同样的工作 IP 地址，试图访问维基.
 * 7) MediaWiki 软件检测到了这位同事，也自动封禁了他，以及他未来可能会用到 IP 地址. 这也不会发生，原因同上.
 * 8) And so on...

It is important for users to understand that administrators do not set autoblocks; once they have blocked a user with autoblocking enabled, autoblocks are set by the MediaWiki software. Autoblocks do not appear in administrators' block logs, and the administrators are not notified of them. This is a necessary consequence of keeping logged-in users' IP addresses private. So while the IP address responsible for each edit is recorded by the MediaWiki software, this cannot be accessed, even by administrators and even when the user is blocked.

追踪
If is enabled a cookie  will be set on an autoblocked user's browser. 这意味着即使在登出并移动到一个新IP地址之后，用户仍然会被封禁.

当cookie设置，和用户尝试编辑一个页面，页面将加载在cookie指定原封禁和防止用户制作编辑. This does not, however, create a new autoblock for the new IP address. That only happens if the user logs into the original blocked account.

This form of tracking is dependent on the user's browser retaining the cookie, and so will not work for all blocked users in all situations. The feature is intended to provide a small extra level of protection against blocks being circumvented.

禁用自动封锁
When a block is issued, autoblocking is usually turned on by default, except for common dynamic IP ranges, such as those used by AOL. A list of such automatically exempt IP ranges can be found at MediaWiki:Autoblock whitelist.

Administrators can disable autoblocking at the time of blocking a user, by unchecking the checkbox. Once an "enabled" block is placed, it can also be fixed by modifying the user's block, but this should not be done unless absolutely necessary.

自动重置
There is an internal autoblock expiry time variable,, which is set to 24 hours, meaning that autoblocks only last for 24 hours. However, in the case of dynamic IP address pools (such as those used by AOL), this may affect hundreds of users before the block expires. So in the case of an indefinite block, autoblocks may continue to be set by the software, weeks or months after the initial block has been set. Older indefinite blocks, dating from before the autoblock exemption whitelist and the option to disable when blocking, may also trigger autoblocks.

IP封锁列表
When IP addresses are autoblocked, they appear in Special:Ipblocklist (but not in the admin's block log) with a special mask that prevents the IP address from being seen. Autoblocks register on Special:Ipblocklist, Special:AutoblockList and in the banner available to the blocked user, with the name of the admin that set the original block. However, the admin is not notified that an autoblock has been placed. Diligent administrators who lift a block early may wish to check the Ipblocklist in order to check for any autoblocks that need to be cleared.

提示

 * It is helpful for all involved, especially AOL users, who are often chronically autoblocked by collateral damage, to remain patient and remember that it is the software that is responsible for the autoblock, not the administrator who is unfortunate enough to have his or her name appear on the block log.
 * Equally important is for admins to check Special:Ipblocklist and Special:AutoblockList regularly, and unblock all autoblocks from a particular user if more than two autoblocks are set in rapid succession.
 * If more than two IP addresses are autoblocked within seconds/minutes of each other, it is a good indication that it is a dynamic IP address pool and the blocks are collateral damage.