design button to reject takedown req for formal reasons

lucasgonze commented 12 years ago

incomplete, inaccurate, not copyright etc.

lucasgonze commented 12 years ago

Hey @paigedes, could you add this to your RFC-in-progress?

paigesaez commented 12 years ago

Sure. Can you fill me in on a little bit more of what this ticket means? A use-case perhaps?

lucasgonze commented 12 years ago

General story: A dispute is submitted. It fails to meet the formal requirements for a dispute. The site is not obligated to act on it.

Use case: meaningless or gibberish data. A submitter has filled in the dispute form with nothing but underscores in the text fields.

Use case: attacker manages to insert a bogus request with blank data.

Use case: the complaint is not about copyright.

On rejecting a dispute

if there is a valid email address on the request an email should be sent to the submitter saying that the request was denied because it didn't meet the formal requirements for a valid notice.
the site administrator should be able to add a note

On Fri, Oct 26, 2012 at 10:57 AM, paigedes notifications@github.com wrote:

Sure. Can you fill me in on a little bit more of what this ticket means? A use-case perhaps?

— Reply to this email directly or view it on GitHubhttps://github.com/lucasgonze/Safeharbor.in/issues/207#issuecomment-9821544.

lucasgonze / Safeharbor.in

design button to reject takedown req for formal reasons #207