{"id":279,"date":"2019-11-07T03:07:25","date_gmt":"2019-11-07T03:07:25","guid":{"rendered":"http:\/\/wordpress.cs.vt.edu\/cscw2019\/?p=279"},"modified":"2019-11-07T03:15:04","modified_gmt":"2019-11-07T03:15:04","slug":"reflection-on-soylent-a-word-processor-with-a-crowd-inside","status":"publish","type":"post","link":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/2019\/11\/07\/reflection-on-soylent-a-word-processor-with-a-crowd-inside\/","title":{"rendered":"Reflection on “Soylent: A Word Processor with a Crowd Inside”"},"content":{"rendered":"\n

Summary<\/strong>:<\/p>\n\n\n\n

Soylent<\/strong>, proposed by Michael S. Bernstein et al. , is a word processing interface that utilizes crowd contributions to aid complex writing tasks ranging from error prevention and paragraph shortening to automation of tasks like citation searches and tense changes<\/em>. Soylent<\/strong> aids the writing process by combining Amazon’s Mechanical Turk workers and Microsoft Word. Soylent<\/strong> comprises of 3 components:<\/p>\n\n\n\n

  1. Shortn <\/li>
  2. Crowdproof <\/li>
  3. The Human Macro <\/li><\/ol>\n\n\n\n

    Shortn works on shorterning the request text down to 78%\u201390% of it’s original size. Crowdproof catches spelling and grammatical errors, with the accuracy of 67%. Human macro refers to custom requests made to the Mechanical Turkers. So far there has been 88% of intent success, which basically means 88% of the time the custom requests made to Turkers were understood correctly and was dealt with. <\/p>\n\n\n\n

    Soylent<\/strong> uses Find-Fix-Verify to make changes. They distribute the requests and first find the places that need attention. Then they apply Fix to those parts. Later they verified whether the fix applied was acceptable or not.<\/p>\n\n\n\n

    Reflection<\/strong>:<\/p>\n\n\n\n

    To me, the idea about crowd-sourcing one of the problems that still can’t be dealt with computers totally yet seems pretty novel. Though these days Google’s text prediction, spelling and grammatical error detection and reply to messages is pretty scary, but it’s still far from perfect. We still need to ask our co-workers, lab-mates, friends to assist us with proof-reading. So in that aspect, Soylent<\/strong> is an amazing idea. <\/p>\n\n\n\n

    While going through the paper, I was thinking that the whole idea is basically a bigger version of Wizard of Oz. My thought was pretty much verified with the line “Our work suggests that it may be possible to transition from an era where Wizard of Oz techniques were used only as prototyping tools to an era where a \u201cWizard of Turk\u201d can be permanently wired into a system.<\/em>” I really loved the idea of using crowd-sourcing to solve problem and later on use that to train Artificial intelligence, so that they can deal with similar problems in the future. I think the other technology that uses similar idea is Captcha<\/strong>. <\/p>\n\n\n\n

    The Lazy Turker<\/em><\/strong> and Eager Beaver<\/em><\/strong> problem seemed pretty interesting to me. We do seem to come across such problem in different settings. I really loved how they forced the lazy turkers to put more effort in their work. The usage of find-fix-verify definitely helped mitigating the problem of these cases.<\/p>\n\n\n\n

    One of the aspects I loved most about the paper was their conclusion. They actually showcased how Soylent<\/strong> works by shortening, proofreading their conclusion section using it. That’s pretty creative. I love it!<\/p>\n\n\n\n

    P.S: Through the paper this was going through my head and I HAD<\/strong> to add it here.<\/p>\n\n\n\n

    \"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

    Summary: Soylent, proposed by Michael S. Bernstein et al. , is a word processing interface that utilizes crowd contributions to aid complex writing tasks ranging from error prevention and paragraph shortening to automation of tasks like citation searches and tense changes. Soylent aids the writing process by combining Amazon’s Mechanical Turk workers and Microsoft Word….<\/p>\n","protected":false},"author":267,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-279","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/posts\/279","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/users\/267"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/comments?post=279"}],"version-history":[{"count":4,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/posts\/279\/revisions"}],"predecessor-version":[{"id":290,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/posts\/279\/revisions\/290"}],"wp:attachment":[{"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/media?parent=279"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/categories?post=279"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.cs.vt.edu\/cscw2019\/wp-json\/wp\/v2\/tags?post=279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}