Thread by @profcarroll

This week in our #TechMediaDemocracy collab course @informor @justinhendrix and I hosted @JuliaAngwin @karaswisher @Moonalice @cwarzel for session on Platform Patterns & Algorithms thinking about what’s at stake this year, need for sources/methods, architecture of accountability

In our @parsonsdesign after-panel Zoom, we took cues from @JuliaAngwin @Moonalice to think about tools/methods/models yet built, or fully redesigned. Our design centric view framed UX as oft overlooked/mistaken as a mere byproduct of algos in these discussions. Also the Intl POV.

Mindblowing was @JuliaAngwin describing all the nuts and bolts that need to machined from scratch to build a data collector at the service of algorithmic accountability journalism that don’t leak data and cause collateral harm. What does building the tools you rely on teach you?

*to be machined from scratch; mind still blown

Imagine having to build your own embeds because every nifty free service copy and paste shortcut is a data leak. That’s what they do at @themarkup, to do what they do. Reveals our collective dependence on risky shortcuts!

One of my students imagined an interface where she had more agency over the presentation of content and the network she was accessing because it was decentralized and it sounded at lot like Web 1.0 to my middle aged ears. Pre-app. Pre-platform. The avant garde.

MVP award of the panel IMO goes to @cwarzel who fielded tough questions on how to use data leaks to journalists for good. We don’t (yet) have laws/leverage to expose data abuse. It reveals asymmetry of knowledge that we rely on guilty feeling data merchants who leak to the press.