Change Details

Due to the privacy policy, CheckUserLog can only be viewed by users who have permission. Although the CheckUsers can organize and publicly publish the statistics of these logs, but some people still believe that some information was concealed. I recommend that the system provide a interface to query the log which the information can be public, like 'When and who query a UserCheck with the reason, or no reason for privacy policy'. This will strike a balance between privacy and openness. There are some variables to control the function. *enablePublicUserCheckLog: to enable or disable the interface of public CheckUserLog. *hideReasonForInit: because the reason of some old log will have the privacy data, it must be hidden. the default value is true to hidden the reason. *defaultChoicenToHiddenReasonWhenQuerying: the interface 'Special:CheckUser' will add a new option to choose whether hide the reason or not. It will public the reason if the option is be checked. This variable is used to control whether the option is checked by default. The default value is true to indicate that the option is checked by default. the database schema of log [https://www.mediawiki.org/wiki/Extension:CheckUser/cu_log_table] will add a new column to mark whether the reason is public or not. That is all. I hope to consider this suggestion.

Due to the privacy policy, CheckUserLog can only be viewed by users who have permission. Although the CheckUsers can organize and publicly publish the statistics of these logs, but some people still believe that some information was concealed. It may be necessary to check the log directly without violating the privacy policy. I recommend that the system provide a interface to query the log which the information can be public, like 'When and who query a UserCheck with the reason, or no reason for privacy policy'. This will strike a balance between privacy and openness. There are some variables to control the function. *enablePublicUserCheckLog: to enable or disable the interface of public CheckUserLog. *hideReasonForInit: because the reason of some old log will have the privacy data, it must be hidden. the default value is true to hidden the reason. *defaultChoicenToHiddenReasonWhenQuerying: the interface 'Special:CheckUser' will add a new option to choose whether hide the reason or not. It will public the reason if the option is be checked. This variable is used to control whether the option is checked by default. The default value is true to indicate that the option is checked by default. the database schema of log [https://www.mediawiki.org/wiki/Extension:CheckUser/cu_log_table] will add a new column to mark whether the reason is public or not. That is all. I hope to consider this suggestion.

Due to the privacy policy, CheckUserLog can only be viewed by users who have permission. Although the CheckUsers can organize and publicly publish the statistics of these logs, but some people still believe that some information was concealed. It may be necessary to check the log directly without violating the privacy policy. I recommend that the system provide a interface to query the log which the information can be public, like 'When and who query a UserCheck with the reason, or no reason for privacy policy'. This will strike a balance between privacy and openness. There are some variables to control the function. *enablePublicUserCheckLog: to enable or disable the interface of public CheckUserLog. *hideReasonForInit: because the reason of some old log will have the privacy data, it must be hidden. the default value is true to hidden the reason. *defaultChoicenToHiddenReasonWhenQuerying: the interface 'Special:CheckUser' will add a new option to choose whether hide the reason or not. It will public the reason if the option is be checked. This variable is used to control whether the option is checked by default. The default value is true to indicate that the option is checked by default. the database schema of log [https://www.mediawiki.org/wiki/Extension:CheckUser/cu_log_table] will add a new column to mark whether the reason is public or not. That is all. I hope to consider this suggestion.