Autoblock/fr

Un "autoblocage" arrive lorsqu'une adresse IP est bloquée automatiquement par le logiciel MediaWiki. Les autoblocages sont le résultat d'une tentative d'édition du wiki à partir d'une adresse IP récemment utilisée par un utilisateur bloqué.

Chaque fois qu'un utilisateur édite le wiki, l'adresse IP utilisée pour se connecter au site est enregistrée par le logiciel MediaWiki qui alimente le wiki. Un journal de adresse IP utilisées par chaque utilisateur est gardaient en privé, accessible uniquement par les utilisateurs avec checkuser accès à le MediaWiki logiciel

The autoblock will duplicate most of the block settings, including if the block is sitewide or partial, but does not include the original duration, blocking email, and hardblock.

Déblocage d'un utilisateur autobloqué
Si un utilisateur est automatiquement bloqué, par exemple si un utilisateur nommé a été débloqué, mais son adresse IP est toujours bloquée automatiquement, un administrateur peut effacer le blocage automatique par:


 * Examiner la liste des Special:BlockList et rechercher le nom de compte de l'utilisateur. Il s'agit d'une recherche sensible à la case.
 * Identifier le #xxxxx nombre qui est associé. Si vous recherchez ce numéro, assurez-vous d'inclure le "#"
 * Unblocking the #xxxxx by clicking the "" link

Notez qu'une fois que le blocage automatique est effacé, le nom de compte de l'utilisateur n'apparaîtra plus dans la liste.

Journal des messages
Parfois, le terme "" apparaîtra dans un message bloqué. Cela signifie que lorsque l'utilisateur a été bloqué, "seulement" son nom d'utilisateur a été bloqué, mais d'autres utilisateurs sur la même adresse IP sont toujours libres de modifier.

Le paramètre par défaut d'un bloc consiste à faire fonctionner automatiquement le blocage automatique "activé", mais il ne le dit pas explicitement dans un message bloqué. Pour désactiver l'autoblocage par défaut d'un compte, les administrateurs doivent obligatoirement cocher la case "$message".

Fonctions Principales


Lorsqu'un blocage automatique se produit, les utilisateurs peuvent être automatiquement bloqués à la suite d'un bloc sur un autre utilisateur, qui utilisait probablement le même FAI. Ainsi, un utilisateur différent peut finir bloqué, bien qu'il n'ait personnellement rien fait de mal. Ceci est appelé "dommage collatéral". Exemple:


 * 1) L'utilisatrice Susan, en tant qu'administratrice, bloque l'utilisateur Bort pour une durée de 24 heures. Unknown to Susan, Bort uses AOL to edit the wiki, and an autoblock was enabled at the time of the block.
 * 2) User:Steven, who also uses AOL from home, and is currently assigned the IP address last used by Bort, signs on to the wiki.
 * 3) Steven receives a "You have been blocked" message when he clicks "Edit", doesn't understand what an autoblock is, and angrily demands to know why admin Susan has blocked him.
 * 4) Steven tries to edit from his work computer (which does not use AOL).  He learns that autoblocks only propagate from usernames to IP addresses, and decides to resume normal editing there.

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.

Suivi
If is enabled a cookie  will be set on an autoblocked user's browser. This means that the user will still be blocked even after logging out and moving to a new IP address.

When the cookie is set, and a user tries to edit a page, MediaWiki will load the original block specified in the cookie and prevent the user from making the edit. 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.

Désactivation du blocage automatique
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.

Réinitialisation automatique
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.

Liste des adresses ip bloquées
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. Instead, the block is identified by the block ID and is labeled "Autoblock #xxxxxx" in the BlockList. 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 blocklist in order to check for any autoblocks that need to be cleared.

Conseils

 * 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 their 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.