Ticket #495 (new task)

Opened 2 years ago

Last modified 2 years ago

process for dealing with content take-down requests

Reported by: https://id.mayfirst.org/malloryk Owned by:
Priority: major Milestone: 5
Keywords: Cc:
Project Area: Other Project: policy
Skill Set Required: Training or Documentation

Description

There have been a few requests for content to be removed from our sites and open archives of list serves.

The first question is should we always and fully comply with these requests or are there exceptions?

The second question is how we deal with take-downs?

I can offer my perspective just to start:

  1. MF/PL, the server host, won't comply with a request to take down information that infringes on free speech, even when the notice cites a violation of fair use. However, what if the request for take down is for information of a personal, sensitive nature? What if the request is coming from the person that created the content (like in the most recent case of an individual that had a film in 2007 and wants the submitted application's node removed)?
  2. If we decide to take down information, we should replace it with a standard node that preserves the title of the node (in case something linked here previously or a search engine found a cached copy of the old page) and replaces the body with text that indicates that it has been removed at ###'s request. Then, we can cite our policy on content creation and take-down requests here, too.

Change History

Changed 2 years ago by https://id.mayfirst.org/malloryk

This is the node that was requested for removal from nexusifc [at] gmail.com:
 http://www.ussf2007.org/en/node/2057

Changed 2 years ago by alfredo@…

Who made the request for removal of the node?

Alfredo

Changed 2 years ago by https://id.mayfirst.org/jamie

It seems as though the request came from the person that claims to have created the content (gleaned from Mallory's original post). Although it's not clear which of the two people identified in the post made the request.

I think you are on the right track with the policy Mallory. Did this request specifically state privacy concerns? I would even go as far as to say for privacy related take downs, we only redact the private information (and we try to make clear when people are submitting data that contact or otherwise potentially sensitive info will be public to discourage it's use).

jamie

Changed 2 years ago by https://id.mayfirst.org/malloryk

  • project set to policy
  • skillset changed from Group Consensus to Training or Documentation
  • type changed from question to task
  • project_area changed from Primary Web site/Communication to Other

The request doesn't address the nature of the content whatsoever. I'm paraphrasing, but it says "please remove this" only. No identification beyond email address.

Next steps:

  • We create this take down policy language, insert it here.
  • I respond to the email, citing the policy, and asking for clarification on which information is private.
  • Create a parallel policy for submission of data and place that language below all "submit" buttons? A checkbox of understanding probably isn't legally required, but we should confirm this.
  • Confirm legal responsibility to display content submission policy.

Changed 2 years ago by alfredo@…

We don't redact for MF/PL because we consider everything done by a member to be the property of all members and therefore of the movement. Is that applicable to USSF? Do others in the Social Forum leadership understand that?

I think it's applicable but I am not at all sure most USSF leaders do. I think we need to offer a policy explanation to some leadership body. No?

Alfredo

Note: See TracTickets for help on using tickets.