<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Caroline C. on Medium]]></title>
        <description><![CDATA[Stories by Caroline C. on Medium]]></description>
        <link>https://medium.com/@caroline.crandall?source=rss-460db1fe90c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*pKa1i5FC4n57w-dlSdM1JQ.png</url>
            <title>Stories by Caroline C. on Medium</title>
            <link>https://medium.com/@caroline.crandall?source=rss-460db1fe90c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:20:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@caroline.crandall/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[An Update from the Acceptable Ads Committee]]></title>
            <link>https://medium.com/@caroline.crandall/an-update-from-the-acceptable-ads-committee-e9bc5b1d3da2?source=rss-460db1fe90c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9bc5b1d3da2</guid>
            <category><![CDATA[advertising]]></category>
            <dc:creator><![CDATA[Caroline C.]]></dc:creator>
            <pubDate>Wed, 25 Oct 2017 20:18:27 GMT</pubDate>
            <atom:updated>2017-10-25T20:18:27.438Z</atom:updated>
            <content:encoded><![CDATA[<p>The AAC is starting on some really interesting and exciting research this month, but we are also doing some official housekeeping. The AAC was originally appointed by the committee founders at Eyeo, but moving-forward, the committee is elected by its members. That election happened by September 1st, and many of the members were re-elected as representatives. Here is the full list with a bit of detail.</p><p><strong>Advertisers</strong>: Breanna Fowler, Dell</p><p><strong>Digital Rights Organizations: </strong>Holmes Wilson, Fight for the Future and Paul-Olivier Dehaye, PersonalData.IO</p><p><strong>Creative Agent: </strong>Jon Lefley, Saatchi &amp; Saatchi</p><p><strong>User Representative: </strong>Caroline Crandall, California College of the Arts</p><p><strong>Researchers: </strong>Arvind Narayanan, Princeton University</p><p><strong>Content Creators: </strong>Gavin Hall, TED Talks</p><p><strong>Advertising Agency: </strong>Gabriel Cheng, M&amp;C Saatchi Mobile</p><p><strong>Ad Tech Agency</strong>: James Sciolto, Bidio</p><p><strong>User Agent:</strong> Michael O’Neill</p><p>A few changes in membership were in the Ad Tech Agency Group, the Researcher Group and the User Agent Representative. James Sciolto, Co-Founder &amp; Chief Marketing Officer at Bidio, is now the new representative for the Ad Tech Agency Group; and Arvind Narayanan, Assistant Professor at Princeton University and new member since August is the new representative for the Researcher Group. Michael O’Neill now joins us at the User Agent Representative and Marty Kratky-Katz joins the Ad Tech group as a member.</p><p>At this stage, the Committee still has to fill a position for a <strong>Digital Rights Organization</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9bc5b1d3da2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The AAC’s First Meeting]]></title>
            <link>https://medium.com/@caroline.crandall/the-aacs-first-meeting-6122ccdb3933?source=rss-460db1fe90c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6122ccdb3933</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[advertising]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Caroline C.]]></dc:creator>
            <pubDate>Thu, 03 Aug 2017 18:34:25 GMT</pubDate>
            <atom:updated>2017-08-03T19:21:32.868Z</atom:updated>
            <content:encoded><![CDATA[<p>The Acceptable Ads Committee held its first meeting in New York on Tuesday July 11th — a formal hand-off from eyeo GmbH to the AAC.</p><p>Committee members heard from eyeo’s developers, leadership, and legal team about the program’s current status, the research done to date, and the mandate entrusted to the AAC.</p><p>As a first step, we want to gather as much data as possible to understand where the current standards are falling short. That data can help us zero in on viable areas of improvement and can also help us understand the most critical metrics for identifying success.</p><p>While eyeo can supply us with some of that data, the committee plans to reach out to academics, users, publishers and advertisers to get a more complete picture of the digital ad blocking landscape. Our diverse team is committed to having a multi-dimensional understanding of the challenges ahead.</p><p>Here is a snapshot of some of the questions that the committee came up with as we brainstormed research we wanted to gather:</p><ul><li>What are actionable KPIs for Acceptable Ads criteria?</li><li>What is the monitoring process for whitelisted publishers and how effective is it?</li><li>What research has been done about acceptable ads for mobile devices?</li><li>What do we know about edge cases?</li><li>What are missing dimensions in the Acceptable Ads criteria (privacy, security)?</li><li>Through which mechanisms and processes should we gather feedback?</li></ul><p>Some of these questions may seem like they have obvious answers — but we feel strongly that advocating for the best possible criteria for Acceptable Ads users means approaching these standards with intention, quantifiable data, and a healthy dose of skepticism. We believe strongly that we must consider all different ways of thinking about this problem if we are going to solve it meaningfully.</p><p>We will keep you all posted as we launch into the deep research dive of this process, especially because we will be asking many of you for your input.</p><p>From New York,</p><p>The AAC</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6122ccdb3933" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to fight the fake news problem without becoming arbiters of truth]]></title>
            <link>https://medium.com/@caroline.crandall/how-facebook-can-fight-the-fake-news-problem-without-becoming-arbiters-of-truth-efd24ed296ab?source=rss-460db1fe90c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/efd24ed296ab</guid>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Caroline C.]]></dc:creator>
            <pubDate>Fri, 16 Dec 2016 18:13:48 GMT</pubDate>
            <atom:updated>2017-01-13T20:38:53.889Z</atom:updated>
            <content:encoded><![CDATA[<p>Social media platforms are in between a rock and a hard place when it comes to fighting fake news. On the one had, companies have a tremendous opportunity to create more informed readers and therefore more informed voters. On the other hand, trying to fact-check the enormous amount of content that circulates on their platforms is a herculean task, especially since fact-checking content is a very manual process that is difficult to scale.</p><p>I think there is another way forward.</p><p>Perhaps social media platforms could weed out fake content by making subtle changes to the interfaces and platforms where content is shared.</p><p>Here is a story to explain what I mean:</p><p>I spent about 4 years working as a TV producer in local news, writing and vetting stories. Before I sat down to write a given story, say for example a 20 second story about a national piece of legislation, I would read 5–6 different versions of that story from places like the Associated Press, the Wall Street Journal, The New York Times, and any other source that was relevant.</p><p>Even across venerated news sources like those ones, there were usually always subtle but critical differences in reporting. I enjoyed reading them back to back; at the end I felt like I had a more complete sense of overall picture. This is a time-consuming process, but it could be distilled rather quickly.</p><p>What if we could design an interface where when someone clicked on a story, the right hand column of the screen could show how that story was told by different outlets. If the story was fake, a related headline could debunk it quite quickly (either there were no related headlines or clashing related headlines).</p><p>This type of interface could create readers that had a multi-dimensional sense of the content around them, and could create readers who are the fact-checkers themselves.</p><p>Obviously this small idea is not a well-researched or vetted one, rather it is just an example to illustrate a simple point: maybe the best way to combat fake news is to drown it out with real news? If we design interfaces that give a reader more context, we create more informed readers without being arbiters of truth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efd24ed296ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The problem with the “fake news problem”]]></title>
            <link>https://medium.com/@caroline.crandall/the-problem-with-the-fake-news-problem-6a08f464bf28?source=rss-460db1fe90c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a08f464bf28</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[fake-news]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Caroline C.]]></dc:creator>
            <pubDate>Mon, 28 Nov 2016 15:57:44 GMT</pubDate>
            <atom:updated>2016-11-28T15:57:44.309Z</atom:updated>
            <content:encoded><![CDATA[<p>The explosion of “fake news” is a troubling trend — even more so now that a Stanford study indicates many students struggle to differentiate between legitimate and biased news sources.</p><p>But how we frame this problem is critical to solving it.</p><p><strong>The problem with fighting “fake news” is that it suggests there is some sort of binary duality, a clear line between real and fake, truth and lies.</strong></p><p>And while falsehoods may be relatively easy to pin down, the truth is much more elusive. A favorite history teacher of mine said once, “every story is a donut, the truth is in the middle.” The truth can be different things to different people.</p><p>However complicated, the perspective-driven and elusive nature of a “true” story can lead us to some interesting places. Or, to nest it in design thinking paradigms: How can we create more informed users with those complex qualities in mind?</p><p><strong>How can we design the networks we use to share information to provide a more contextual and complete version of stories?</strong></p><p>We can give people better tools to understand the narratives happening around them. We can create context-driven interfaces that surround even the most unbelievable and dubious stories with vetted and transparently-sourced ones.</p><p>We can drown out the fake news with the good, limit the echo chamber effect, and we can do it without wading into the complicated world of censorship.</p><p>This question involves a much more thorough design effort — but there are a few specific ideas that stand out at me currently.</p><p>1. Our current mode of navigating and reading web pages, stories, newsfeeds, is by and large vertical. We scroll up and down, from most important to least. There is an inherent prioritization implied in how information is given to us — but we are usually not privy to how articles are ranked. It would be useful to know this.</p><p>2. It would also be useful to add another dimension to our feeds and pages. That dimension should be context. So much of what I have read in the past few weeks asks readers to shoulder the burden of finding good news for themselves. And I agree that we all must be better about vetting our news, but I also believe that if we really want that to happen we need to design for it too.</p><p>3. What if related articles or articles of a different bias or a whole spectrum of opinions were available at one swipe right or left? Or if users could see the spectrum without even having to swipe? Or users could drill down and back up again across varying posts about the same story or topic?</p><p>These are just some preliminary ideas — but design has an immense opportunity to shape how we absorb information for the better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a08f464bf28" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>