Last modified: 2014-11-10 18:05:45 UTC
Not sure if maybe Wikimedia/Site requests would be the appropiate place. When an user account is blocked on a private wiki that has the 'wgBlockDisablesLogin' in the config, the blocked user should not continue to receive email notifications about pages changed on his watchlist. This is happening to me. Blocked users on 'wgBlockDisablesLogin'-wikis won't be able to login and check the change made, and there's the posibility that private data may be leaked in the edit summary (data that the user is not suposed to access anymore). Since blocking on those private wikis such as <http://noc.wikimedia.org/conf/highlight.php?file=private.dblist> (& I'm speaking for those that I know: CU and steward wikis) is not used as a way to prevent abuse, but as a tool to remove someone's access to the wiki, it makes sense IMHO to disable from blocked users the ability to continue to receive email notifications. I guess that that is the primary use of the tool in all of the other ones. Thanks.
We have the DisableAccount extension for this purpose, which according to <https://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php> is enabled on both stewardwiki and CUwiki. Is that not sufficient?
Presumably not. That is tool that we use and seemingly this report is that they still receive notifications. Deactivate an account (variation of Special:Block) ... deactivated MarcoAurelio (Talk | contribs) with an expiry time of infinite (account creation disabled) ...
(In reply to billinghurst from comment #2) > Presumably not. That is tool that we use and seemingly this report is that > they still receive notifications. > > Deactivate an account (variation of Special:Block) > > ... deactivated MarcoAurelio (Talk | contribs) with an expiry time of > infinite (account creation disabled) ... Nope. That is the normal 'block' option (the block log messages are customized over there). Deactivation mentioned by Legoktm above is what is done via Special:DissableAccount. However it (is/was?) policy of that wiki not to use that powerful blocking tool unless it was strictly necessary (compromised accounts, etc.) as suggested by WMF because its use was not logged anywhere (cf. bug 32782 - not sure if that's really logged now, there was an ad hoc page created there for that purpose) and because its use is only reversible with system administrator intervention. It is not rare that some CUs (and happened with stewards as well, tho less frequently) wants to take a break, drops the tools and it's access is removed, and after a couple of months the user regains the tools tho is allowed to have access to the Wiki again. It'd be overkill IMHO to call a sysadmin each time an account needs to be reactivated, when a simple "unblock" can be done. Rename is an option, to free again the name and create a new account under the old name; however his/her former edits will be attributed to their old account, which is not an optimal situation IMHO. Best regards.
