| Literature DB >> 27043712 |
Jacobien van Apeldoorn1, Arthur Schram2,3.
Abstract
Indirect reciprocity involves cooperative acts towards strangers, either in response to their kindness to third parties (downstream) or after receiving kindness from others oneself (upstream). It is considered to be important for the evolution of cooperative behavior amongst humans. Though it has been widely studied theoretically, the empirical evidence of indirect reciprocity has thus far been limited and based solely on behavior in laboratory experiments. We provide evidence from an online environment where members can repeatedly ask and offer services to each other, free of charge. For the purpose of this study we created several new member profiles, which differ only in terms of their serving history. We then sent out a large number of service requests to different members from all over the world. We observe that a service request is more likely to be rewarded for those with a profile history of offering the service (to third parties) in the past. This provides clear evidence of (downstream) indirect reciprocity. We find no support for upstream indirect reciprocity (in this case, rewarding the service request after having previously received the service from third parties), however. Our evidence of downstream indirect reciprocity cannot be attributed to reputational effects concerning one's trustworthiness as a service user.Entities:
Mesh:
Year: 2016 PMID: 27043712 PMCID: PMC4820101 DOI: 10.1371/journal.pone.0152076
Source DB: PubMed Journal: PLoS One ISSN: 1932-6203 Impact factor: 3.240
Data Overview.
| Dutch | Israeli | All | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Female | Male | Female | Male | |||||||
| Serv. | Neutr. | Serv. | Neutr. | Serv. | Neutr. | Serv. | Neutr. | Serv. | Neutr. | |
| 30 | 30 | 28 | 25 | 19 | 19 | 19 | 19 | 96 | 93 | |
| 16 | 6 | 14 | 11 | 11 | 12 | 10 | 9 | 51 | 38 | |
| 53.3% | 20.0% | 50.0% | 44.0% | 57.9% | 63.2% | 52.6% | 47.4% | 53.1% | 40.9% | |
| 8 | 1 | 7 | 3 | 4 | 5 | 8 | 3 | 27 | 12 | |
| 3 | 3 | 2 | 2 | 4 | 3 | 1 | 1 | 10 | 9 | |
| 26.7% | 3.3% | 25.0% | 12.0% | 21.1% | 26.3% | 42.1% | 15.8% | 28.1% | 12.9% | |
| 50.0% | 16.7% | 50.0% | 27.3% | 36.4% | 41.7% | 80.0% | 33.3% | 52.9% | 31.6% | |
| 31.3% | 33.3% | 35.7% | 54.5% | 27.3% | 33.3% | 10.0% | 55.6% | 27.5% | 44.7% | |
Notes. Columns distinguish between the profile types created, “Serv.” = serving profile; “Neutr.” = neutral profile. In addition: “resp. rate” = #responses/#requests*100%; # yes is number of offers to provide the service; # maybe = number of responses that kept open the possibility of providing the service (but did not yet offer it); “% yes/req” = #yes/#requests*100%; “%yes/resp” = #yes/#responses*100%; “%no/resp” = (#responses–#yes–#maybe)/ #responses*100%. Any member that replied to be willing to provide the service for at least part of the time requested is reported as a ‘yes’. A member that replied that no service could be provided is reported as a ‘no’. Other answers, such as “I don’t know yet”, “let me come back to you in a few days” or “Can you tell me a little bit more about yourself first? I might be able to serve you”, are reported as a ‘maybe’. Only the first reply is reported, meaning that a ‘maybe’ can never turn into a ‘yes’ or a ‘no’.
Determinants of Providers’ Decisions.
| Respond | Yes | Yes or Maybe | ||||
|---|---|---|---|---|---|---|
| serving profile | 0.152 | 2.18** | 0.250 | 2.69*** | 0.229 | 3.23*** |
| Dutch man | 0.126 | 1.11 | 0.084 | 0.84 | 0.001 | 0.03 |
| Israeli woman | 0.245 | 2.19** | 0.070 | 0.52 | 0.076 | 1.09 |
| Israeli man | 0.142 | 1.36 | 0.285 | 2.88*** | 0.094 | 1.10 |
| male | 0.134 | 1.91* | –0.076 | 0.53 | 0.069 | 0.49 |
| age/100 | –0.558 | 0.41 | –0.008 | 0.00 | 2.273 | 1.01 |
| #providers’ references | –0.004 | 0.39 | –0.021 | 1.48 | –0.023 | 1.67* |
| #travelers’ references | –0.007 | 0.72 | 0.006 | 0.55 | –0.003 | 0.33 |
| #friends | –0.007 | 1.64 | 0.005 | 1.05 | 0.008 | 1.37 |
| able to provide | –0.017 | 0.29 | –0.000 | 0.01 | 0.038 | 0.36 |
| days | 0.031 | 1.48 | 0.020 | 0.67 | 0.069 | 1.80* |
| #observations | 189 | 89 | 89 | |||
Notes. The first number in a cell denotes the marginal effect of the variable depicted in the row, in a probit regression explaining the dependent variable distinguished by the column; the second number gives the corresponding z-value. We use robust standard errors clustered at the profile type (eight clusters).
“Respond” = 1 if the provider sent any response at all and 0, otherwise. “Yes” = 1 if, conditional on responding at all, the provider agreed to provide the service, and 0, otherwise. “Yes or Maybe” = 1 if, conditional on responding at all, the provider agreed to provide or kept the option open (i.e., s/he did not reject the request), and 0, otherwise. “Serving profile” = 1(0) if the request was from a serving (neutral) profile. “Profile type” is a set of dummy variables indicating the gender/country background of the profile that sent the request (marginal effects are relative to Dutch women). “Provider characteristics” are obtained from the profile of the community member to whom the request was sent. “#providers’ references” denotes the number of references left by other members that have previously provided the service to the member to whom we sent a service request. “#travelers’ references” denotes the number of references left by other members that have previously received the service from the member to whom we sent a service request. “#friends” denotes the number of friends on the profile of the member to whom we sent a service request. “able to provide” = 1 (0) if the profile indicates the availability to offer the service as “yes” (“maybe”) (recall that no request can be sent to a member indicating “no”). “Days” indicates the number of days between submission of the request and the day for which the service was requested.
*(**,***) denotes statistical significance at the 10(5-,1-)% level.
Service requests sent.
| Female & Dutch | Male & Dutch | Female & Israëli | Male & Israëli | Total | ||
|---|---|---|---|---|---|---|
| History type: | Provision | 30 | 28 | 19 | 19 | 96 |
| Neutral | 30 | 25 | 19 | 19 | 93 | |
| Total | 60 | 53 | 38 | 38 | 189 |
Notes. Cells show per profile the number of requests were been sent. S8 File provides the raw data set acquired from these requests.