Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
72 65 79 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
66 54 78 -
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 1 promise resolved, 5 needed for a score.
All types combined: 71 (likely 64 to 77, high confidence), from 79 claims: 60 factual claims, 19 predictions. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Balaji Srinivasan's claims
227 claims · page 3 of 3
“But there’s potentially ways to do it where you basically do a MapReduce out to all of your phones, and you calculate it locally.”
Balaji Srinivasan, interviewee 25 April 2018 Balaji Srinivasan on the Power and Promise of the Blockchain (Ep. 39) (Conversations with Tyler)
It is potentially possible to run machine learning by distributing computation (MapReduce) to users' phones and calculating locally, keeping data local.
Not researched Checkable, but outside the sample that was researched.
Cite this claim
Balaji Srinivasan, “It is potentially possible to run machine learning by distributing computation (MapReduce) to users' phones and calculating locally, keeping data local.” (said 25 April 2018). Verdict: not researched. Reliability API, claim c_34103847e221, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_34103847e221
Claims without a verdict
- Unresolvable 148
- Not yet due 21
- Own records only 2
- Not researched 227
- Not checkable 1,091
Is a verdict here wrong, or do you speak for Balaji Srinivasan? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.