Open Source is Not Enough: The Importance of Algorithm Transparency

These are slides from Rachel Shadoan's OSBridge talk on Algorithm Transparency. Opaque algorithms increasingly control our access to information, on the web and beyond. Why is that a problem, and what can we do about it?

Transcript

1. Open Source is Not Enough: The Importance of Algorithm Transparency
2. Rachel Shadoan @rachelshadoan @akashiclabs
3. What is an algorithm? Inputs Finite ordered list of instructions Outputs
4. Recipes are algorithms Yogurt Mango Ice 1.Place inputs in blender 2.Blend until smooth Smoothie
5. Outputs Depend on Inputs Yogurt Mango Ice 1.Place inputs in blender 2.Blend until smooth Smoothie No ingredients → No smoothie
6. Outputs Depend on Inputs Rocks Wood chips Motor oil 1.Place inputs in blender 2.Blend until smooth Giant mess Bad ingredients → bad smoothie
7. We are algorithms Environmental Stimulus Really Complex Biological Stuff Thoughts and Actions
8. We can only think about the things we’ve been exposed to
9. Evaluating the quality of the inputs we receive is necessary to evaluate the quality of our thoughts
10. Unknown Unknowns Really Complex Biological Stuff Thoughts and Actions Opaque algorithms interfere with our ability to evaluate the validity/value of inputs to our brain algorithm ???? ???? Opaque (“Black Box”) Algorithm
11. Algorithm Transparency Means No Secrets • Inputs can be scrutinized • Control surfaces are clearly described • Algorithm steps and internal state can be scrutinized • Assumptions and models used by the algorithm are clearly described • Justification available for outputs produced
12. Old Information Access Algorithms
16. Internet-Age Information Access Algorithms
21. So what can we do?
22. Open those opaque boxes! • Support projects that use transparent algorithms • Demand transparency from the opaque algorithms you use • Foster algorithm transparency in your own projects
23. But my algorithms are already open source!
24. But my users don’t want to know!
25. But my algorithm is too advanced to explain to my users!
26. Transparency for Your Projects
27. Talk to Your Users • How do they think it works? • What control do they think they have over its outputs? • What do they wish they knew about it?
28. Document, Document, Document • What inputs does the algorithm work on? • What internal state does the algorithm maintain? • What assumptions/models does the algorithm use? • What control surfaces does the algorithm have? • For any given result, why was that result produced?
30. Credits Al McNutty, CC 2.0, via Flickr Megan Amaral, CC 2.0, via Flickr Kyle aka Wackyland, CC 2.0, via Flickr UConn Libraries MAGIC, CC 2.0, via Flickr Pete aka ComedyNose, CC 2.0, via Flickr Smithsonian’s National Zoo, CC 2.0, via Flickr
31. Credits, Continued Malingering, CC 2.0, via Flickr Ourania, CC 2.0, via Flickr