Content deleted Content added
Citation bot (talk | contribs) Alter: title, template type. Add: chapter-url, date, chapter, s2cid. Removed or converted URL. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox3 | #UCB_webform_linked 901/2306 |
|||
Line 75:
The algorithmic outsourcing techniques used in human-based computation are much more scalable than the manual or automated techniques used to manage outsourcing traditionally. It is this scalability that allows to easily distribute the effort among thousands of participants. It was suggested recently that this mass outsourcing is sufficiently different from traditional small-scale outsourcing to merit a new name [[crowdsourcing]].<ref>{{cite magazine |url=https://www.wired.com/2006/06/crowds/ |title=The Rise of Crowdsourcing |author=Howe, Jeff |magazine=Wired |date=June 2006|access-date=12 May 2022}}</ref> However, others have argued that crowdsourcing ought to be distinguished from true human-based computation.<ref>{{cite book |url=https://www.springer.com/gp/book/9781461488057 |title=Handbook of Human Computation |author=Michelucci, Pietro |access-date=12 May 2022}}</ref> Crowdsourcing does indeed involve the distribution of computation tasks across a number of human agents, but Michelucci argues that this is not sufficient for it to be considered human computation. Human computation requires not just that a task be distributed across different agents, but also that the set of agents across which the task is distributed be ''mixed:'' some of them must be humans, but others must be traditional computers. It is this mixture of different types of agents in a computational system that gives human-based computation its distinctive character. Some instances of crowdsourcing do indeed meet this criterion, but not all of them do.
Human Computation organizes workers through a task market with APIs, task prices, and software-as-a-service protocols that allow employers / requesters to receive data produced by workers directly in to IT systems. As a result, many employers attempt to manage worker automatically through algorithms rather than responding to workers on a case-by-case basis or addressing their concerns. Responding to workers is difficult to scale to the employment levels enabled by human computation microwork platforms.<ref name="mw-cw">{{cite journal | last1 = Irani | first1 = Lilly|author1-link=Lilly Irani | year = 2015 | title = The Cultural Work of Microwork | journal = New Media & Society | volume = 17 | issue = 5 | pages = 720–739 | doi = 10.1177/1461444813511926| s2cid = 377594 }}</ref> Workers in the system Mechanical Turk, for example, have reported that human computation employers can be unresponsive to their concerns and needs<ref name="to-acm">{{cite book | last1= Irani|first1=Lilly|last2 = Silberman | first2 = Six |title=Proceedings of the SIGCHI Conference on Human Factors in Computing Systems |chapter=Turkopticon | year=2013|series=Chi '13
==Applications==
| |||