Skip to main content
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described heredescribed here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

enter image description here

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

enter image description here

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

enter image description here

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.
added 40 characters in body
Source Link
user364819
user364819

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

imgenter image description here

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

img

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

enter image description here

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.
Source Link
user336085
user336085

Such a process exists, but moderators cannot do it by themselves. They need help from an employee. The process is described here:

In the past, we've handled requests to delete sensitive information (passwords, etc.) from posts by hard-deleting revisions. This was... a bit dangerous. Henceforth, the team will handle these requests by altering each problematic revision in-place; an annotation will be added to redacted revisions to allow for moderator oversight.

img

These are currently visible only to moderators, and the actual data that was redacted remains inaccessible to everyone. Combined with the new "contact" UI, this should allow for considerably less overhead.

As a reminder, when requesting the removal of sensitive information:

  1. Make sure it's really sensitive. Someone posting their email address in a post seeking a reply probably isn't sensitive; presumably they intended to do that, so just edit it out & tell them to not be selfish. 2. Edit out the sensitive information. 3. Delete the post. 4. Contact us. We'll undelete once the revision history has been redacted.