OpenNews/hackdays/storyandalgorithm/conditionofanonymity: Difference between revisions

OpenNews/hackdays/storyandalgorithm/conditionofanonymity (view source)

Revision as of 19:11, 17 June 2012

25 bytes added , 17 June 2012

no edit summary

Danxoneil

24

edits

@@ Line 17: / Line 17: @@
 </li></ul>
 <ul><li><b>Anything else we should know:</b> We need people who can help review the "because clauses" and mark interesting ones for display. Here's [https://docs.google.com/document/d/1c7ohf_JKmvaqvUJYJq9vhjIhhsgVl5KY-t-rknfO0QI/edit a document we're using to plan our work].
 </li></ul>
-*<b>How is this project useful?</b> It serves to highlight and draw attention to the reasoning given for using anonymous sources, and it does so in an accessible, entertaining way.
+<ul><li>
-*<b>Where is this project going and what lessons/concepts can be applied to other projects?</b> The goal product is to have a web application and Twitter bot that tweets out reasons given for anonymity. The project was developed by using a lightweight way to find structure in unstructured text. Many industries use consistent phrasing (e.g. style books for journalists, standard operating procedure in police departments), and it makes it easy to find consistent phrasing with a minimum of programming effort. And, sometimes organizations use common phrases as a defense mechanism (e.g. no comment), but this turns that approach on its head because the consistent language is exactly what makes it so easy to find, gather, and analyze repeated references.
+<b>How is this project useful?</b> It serves to highlight and draw attention to the reasoning given for using anonymous sources, and it does so in an accessible, entertaining way.
+</li></ul>
+<ul><li><b>Where is this project going and what lessons/concepts can be applied to other projects?</b> The goal product is to have a web application and Twitter bot that tweets out reasons given for anonymity. The project was developed by using a lightweight way to find structure in unstructured text. Many industries use consistent phrasing (e.g. style books for journalists, standard operating procedure in police departments), and it makes it easy to find consistent phrasing with a minimum of programming effort. And, sometimes organizations use common phrases as a defense mechanism (e.g. no comment), but this turns that approach on its head because the consistent language is exactly what makes it so easy to find, gather, and analyze repeated references.