Change Details

Result of {T309625} With the changes in IP assignment in the industry, our blocking tools are becoming useless every day. Cookie blocking has surgical precision and can be used to make sure blocked users stay blocked, specially indef-blocked ones. Examples: - User:Foo is a new sock of an LTA, starts to abuse and we indef block User:Foo. The LTA logs out and either tries to create a new account or login with a sleeper account. - Status quo: In some cases the user will get an auto block and gets blocked for a day. - Proposal: Attempt to login, or edit another a new username should immediately lead to an indef auto-block (with a block id). - 1.1.1.1 is a bored high school kid and thinks it's funny to vandalize Wikipedia and as result, the IP gets blocked for a week. The mobile provider usually change IP to something else in an hour or more. - Status quo: The vandal continues. - Proposal: Attempt to edit, creating an account and so on should lead to the one-week block being copied to the new IP with the same settings. - User:Bar is a problematic user who got blocked for a week but he has trouble respecting the block - Status quo: The user easily can create a new account and bypass the block. - Proposal: Attempt to login, or edit under another username should immediately lead to an one-week auto-block with a block id. Attempt to edit as IP should also block that given IP with the same settings with the same exact expiry I admit some cases can lead to exposing private information of vandals and blocked users but 1- This is mostly permitted by ToS given the fact that they are trying to bypass the block. And it can also be mitigated by IP masking. There might be also some cases of collateral damage but such damages are next-to-none comparing to the current system of range blocks. And similar to those collateral damages, admins can always unblock the mistakes This won't fix all cases as sophisticated LTAs would clear the cookies and come back but: 1- It still reduces the majority of our vandals who are typically high school kids with little technical knowledge and specially on mobile which free up a lot of much valued volunteer's time. 2- It adds more work to the sophisticated LTAs, they have to jump to more hoops to bypass blocking. We can start by just making sure indef-blocked users stay blocked (but also need to make sure it wouldn't make cause issues in cases of unacceptable username blocks where rename or another user is acceptable).

Result of {T309625} With the changes in IP assignment in the industry, our blocking tools are becoming useless every day. Cookie blocking has surgical precision and can be used to make sure blocked users stay blocked, specially indef-blocked ones. Examples: - User:Foo is a new sock of an LTA, starts to abuse and we indef block User:Foo. The LTA logs out and either tries to create a new account or login with a sleeper account. - Status quo: In some cases the user will get an auto block and gets blocked for a day. - Proposal: Attempt to login, or edit another a new username should immediately lead to an indef auto-block (with a block id). - 192.168.0.1 is a bored high school kid and thinks it's funny to vandalize Wikipedia and as result, the IP gets blocked for a week. The mobile provider usually change IP to something else in an hour or more. - Status quo: The vandal continues. - Proposal: Attempt to edit, creating an account and so on should lead to the one-week block being copied to the new IP with the same settings. - User:Bar is a problematic user who got blocked for a week but he has trouble respecting the block - Status quo: The user easily can create a new account and bypass the block. - Proposal: Attempt to login, or edit under another username should immediately lead to an one-week auto-block with a block id. Attempt to edit as IP should also block that given IP with the same settings with the same exact expiry I admit some cases can lead to exposing private information of vandals and blocked users but 1- This is mostly permitted by ToS given the fact that they are trying to bypass the block. And it can also be mitigated by IP masking. There might be also some cases of collateral damage but such damages are next-to-none comparing to the current system of range blocks. And similar to those collateral damages, admins can always unblock the mistakes This won't fix all cases as sophisticated LTAs would clear the cookies and come back but: 1- It still reduces the majority of our vandals who are typically high school kids with little technical knowledge and specially on mobile which free up a lot of much valued volunteer's time. 2- It adds more work to the sophisticated LTAs, they have to jump to more hoops to bypass blocking. We can start by just making sure indef-blocked users stay blocked (but also need to make sure it wouldn't make cause issues in cases of unacceptable username blocks where rename or another user is acceptable).

Result of {T309625} With the changes in IP assignment in the industry, our blocking tools are becoming useless every day. Cookie blocking has surgical precision and can be used to make sure blocked users stay blocked, specially indef-blocked ones. Examples: - User:Foo is a new sock of an LTA, starts to abuse and we indef block User:Foo. The LTA logs out and either tries to create a new account or login with a sleeper account. - Status quo: In some cases the user will get an auto block and gets blocked for a day. - Proposal: Attempt to login, or edit another a new username should immediately lead to an indef auto-block (with a block id). - 1.1.1- 192.168.0.1 is a bored high school kid and thinks it's funny to vandalize Wikipedia and as result, the IP gets blocked for a week. The mobile provider usually change IP to something else in an hour or more. - Status quo: The vandal continues. - Proposal: Attempt to edit, creating an account and so on should lead to the one-week block being copied to the new IP with the same settings. - User:Bar is a problematic user who got blocked for a week but he has trouble respecting the block - Status quo: The user easily can create a new account and bypass the block. - Proposal: Attempt to login, or edit under another username should immediately lead to an one-week auto-block with a block id. Attempt to edit as IP should also block that given IP with the same settings with the same exact expiry I admit some cases can lead to exposing private information of vandals and blocked users but 1- This is mostly permitted by ToS given the fact that they are trying to bypass the block. And it can also be mitigated by IP masking. There might be also some cases of collateral damage but such damages are next-to-none comparing to the current system of range blocks. And similar to those collateral damages, admins can always unblock the mistakes This won't fix all cases as sophisticated LTAs would clear the cookies and come back but: 1- It still reduces the majority of our vandals who are typically high school kids with little technical knowledge and specially on mobile which free up a lot of much valued volunteer's time. 2- It adds more work to the sophisticated LTAs, they have to jump to more hoops to bypass blocking. We can start by just making sure indef-blocked users stay blocked (but also need to make sure it wouldn't make cause issues in cases of unacceptable username blocks where rename or another user is acceptable).