<?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 Justin Auciello on Medium]]></title>
        <description><![CDATA[Stories by Justin Auciello on Medium]]></description>
        <link>https://medium.com/@justinauciello?source=rss-5616f5d56e0f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dnRIkhddLUS8a4buZNYHYw.jpeg</url>
            <title>Stories by Justin Auciello on Medium</title>
            <link>https://medium.com/@justinauciello?source=rss-5616f5d56e0f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:31:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justinauciello/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[The Questions I Was Asking About the Internet in 2009]]></title>
            <link>https://medium.com/@justinauciello/the-questions-i-was-asking-about-the-internet-in-2009-44dc56e54e14?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/44dc56e54e14</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 13:01:35 GMT</pubDate>
            <atom:updated>2026-11-04T13:01:35.419Z</atom:updated>
            <content:encoded><![CDATA[<p>On April 26, 2009, I heard the fire sirens in Seaside Park, New Jersey, and decided to investigate. An electrical fire had broken out at the Sawmill Bar and Grill on the boardwalk, so I grabbed my BlackBerry, drove up Ocean Avenue, and started reporting on Twitter. My first photograph went up at 9:28 p.m.</p><p>By 9:48, inaccurate reports were circulating. Later that night, some people were claiming the Sawmill had burned down.</p><p>That was news to me. I was looking at a building that was very much still standing.</p><p>I checked information with an official, continued posting updates, and spent part of the following morning correcting rumors. Afterward, I wrote a lengthy blog post reconstructing the episode, complete with photographs, timestamps, and examples of how my reporting had spread through Twitter.</p><p>Four days later, I published <a href="https://auciello.tumblr.com/post/101937712/twitter-and-citizen-journalism-perfect-together"><em>Twitter and Citizen Journalism: Perfect Together</em></a>, examining how ordinary people could contribute to breaking news coverage.</p><p>“It may be mundane to you, but it’s newsworthy to me,” I wrote, referring to the traffic accidents, public disturbances, and other local incidents I’d been reporting that traditional newsrooms might overlook.</p><p>I was 29, working as an urban planner in New Jersey, and increasingly worried about my job during the Great Recession. I’d been involved with online communities since childhood, starting a bulletin-board system on a Macintosh Classic and connecting to FidoNet in 1992. I joined Twitter in 2007 and began using it more seriously the following year, partly to develop professional connections. But I also wanted to pursue journalism. I even applied to Gawker.</p><p>In February 2009, I resumed blogging after several years away from it. Nobody was paying me to write, and my planning job certainly didn’t require it. I was interested in cities, government, journalism, technology, and the ways people were using new platforms to communicate.</p><p>On March 30, I published one of my more substantial essays, <a href="https://auciello.tumblr.com/post/91320812/old-media-is-dying-so-what-is-to-be-done"><em>Old Media Is Dying, So What Is to Be Done?</em></a>.</p><p>The newspaper industry was in serious trouble. I examined circulation trends, advertising losses, changing media consumption, and the growth of Facebook and Twitter. I interviewed Dave Ford of Branded Evolution about the changing advertising business and considered what the migration of audiences online meant for traditional publishers.</p><p>The newspaper business model was clearly failing. But that didn’t make professional journalism any less essential.</p><p>I argued that allowing newspapers to disappear and assuming entrepreneurs would fill the void was untenable. Professional journalism was too important to democracy, particularly its role in holding government accountable.</p><p>I examined Senator Benjamin Cardin’s Newspaper Revitalization Act, which proposed allowing qualifying newspapers to operate as nonprofits, and proposals by John Nichols and Robert McChesney for substantial public investment in journalism.</p><p>I thought government intervention deserved serious consideration if it could sustain functioning newsrooms. At the same time, I worried about editorial independence and whether subsidies might discourage innovation.</p><p>Cardin’s proposed restrictions on political endorsements troubled me. I went too far in suggesting they might effectively eliminate editorial and opinion pages, but my concern about restrictions on independent journalism was genuine.</p><p>I was more receptive to Nichols and McChesney’s approach, although their suggestion of a $200 tax credit to encourage newspaper purchases struck me as misguided.</p><p>“This just does not pass the laugh test,” I wrote.</p><p>I was still buying newspapers myself, but subsidizing print purchases seemed a questionable way to address a structural crisis. If public money was going to support journalism, why not invest in sustaining the reporting itself?</p><p>At the same time, I saw an expanding role for ordinary people in documenting what was happening in their communities.</p><p>“We, the unpaid journalists, now carry a tremendous responsibility to report the news in our communities,” I wrote.</p><p>I was arguing for the preservation of professional reporting while enthusiastically embracing the possibilities of citizen journalism. The two weren’t mutually exclusive. Residents could contribute firsthand observations and local knowledge, while professional journalists could provide investigation, context, and sustained coverage.</p><p>I was experimenting with some of those possibilities myself. In addition to the Sawmill fire, I volunteered for Hoboken411’s live coverage of the city’s notoriously rowdy St. Patrick’s Day festivities, followed and shared reports after a fatal aircraft collision over the Hudson River, and <a href="https://auciello.tumblr.com/post/178219753/seaside-heights-nj-posted-430-pm-updated">reported from Seaside Heights</a> as emergency crews searched for a teenager who had disappeared in the surf.</p><p>By July, I was describing something I called <a href="https://auciello.tumblr.com/post/148409146/if-youre-a-news-junkie-with-a-penchant-for">“Hybrid Media.”</a></p><p>Following the sweeping federal corruption arrests in New Jersey, I examined how professional journalists were combining traditional reporting with Twitter updates, video, and other digital tools. Their sources, institutional knowledge, and ability to explain complicated developments remained indispensable, even as the methods of gathering and distributing news were changing.</p><p>“Not so fast,” I wrote in response to the suggestion that traditional journalism was dead and readers would be left with 140-character updates.</p><p>I was interested in how professional journalism and citizen contributions could work together. I was also confident that online entrepreneurs would help fill gaps as newspapers disappeared. That last assumption was probably too optimistic. Making it easier to publish and distribute information doesn’t guarantee that someone will continue investigating complicated stories, attending municipal meetings, or covering developments long after the initial excitement has passed.</p><p>My interest in these questions extended directly into my planning work.</p><p>In March 2009, I published <a href="https://thenewwaveplanner.tumblr.com/post/86995102/the-new-wave-of-interactions"><em>The New Wave of Interactions</em></a>, examining how mobile technology and social networks could improve public participation in urban planning.</p><p>Why couldn’t residents photograph broken sidewalks, report problems electronically, and track how municipalities responded? Why was so much government information still difficult to obtain?</p><p>I followed San Francisco’s innovations in 311 services, open data, and mapping applications. In June, I wrote about its Twitter-based 311 service, which allowed residents to report maintenance problems directly to city government.</p><p>“There’s a substantial difference between being tech savvy and actively establishing open lines of communication,” I wrote.</p><p>Some municipalities were embracing new approaches to communication. Others seemed perfectly content treating their websites as electronic bulletin boards.</p><p>“It’s really not that difficult,” I declared.</p><p>Opening a communication channel wasn’t necessarily difficult. Getting government to listen, respond, and follow through was another matter.</p><p>I was also interested in how online networks might strengthen physical communities. In September, I <a href="https://auciello.tumblr.com/post/196761265/so-as-more-of-us-retreat-into-our-self-selected">responded to a column by Mary Newsom about “Third Places”</a>, arguing that social media and neighborhood platforms could complement the gathering places where people developed relationships with their neighbors.</p><p>In January 2010, I explored the intersection of journalism and planning more directly in <a href="https://thenewwaveplanner.tumblr.com/post/360538260/meshing-hyperlocal-news-and-community-planning"><em>Meshing Hyperlocal News and Community Planning: Just Cover It</em></a>.</p><p>As a planner, I knew how consequential seemingly routine municipal decisions could be. Zoning amendments, redevelopment proposals, and transportation projects might affect neighborhoods for decades, yet many residents knew little about them.</p><p>I wondered whether hyperlocal journalism could help close those information gaps. Someone might care deeply about what happens in a neighborhood without knowing that an important planning decision is underway. That isn’t necessarily apathy. Sometimes people simply aren’t hearing about the issues.</p><p>Journalism and planning seemed naturally connected to me. Both concerned how communities function, how decisions are made, and whether residents have enough information to participate.</p><p>Some of these interests eventually carried into Jersey Shore Hurricane News, which I founded in 2011, and my later Information as Aid work in Puerto Rico. Operating those systems gave me firsthand experience with the demands of collecting information, verifying reports, responding to questions, and maintaining relationships with residents and institutions.</p><p>That experience also helped inform the Civic Signal Framework I’ve developed more recently. It brings together functions I’d been exploring in different ways since 2009, from gathering community observations and identifying patterns to verification, interpretation, and public communication.</p><p>I didn’t have that framework in mind in 2009. I was writing, reporting, experimenting, and trying to understand how these developments might change communities.</p><p>Reading the original posts, I’m struck by how familiar the problems remain. We have extraordinary tools for publishing information, documenting conditions, and communicating with institutions. Yet local journalism remains financially vulnerable, public information is often fragmented, and meaningful public engagement remains difficult.</p><p>My newspaper essay was fundamentally concerned with preserving journalism’s public value while its traditional business model was collapsing. The other posts approached related questions from different directions: how residents could contribute information, how journalists could make sense of it, and how government could become more responsive.</p><p>Years of practical experience have given me a much better understanding of how difficult it is to organize and sustain that work, even when technology makes participation relatively easy.</p><p>The underlying questions haven’t changed nearly as much as the technology.</p><p>Seventeen years ago, I wanted to know why residents couldn’t report a broken sidewalk and find out what happened afterward.</p><p>Today, that’s easy enough to do.</p><p>Getting someone to fix the sidewalk can still be another matter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44dc56e54e14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Superstorm Sandy — 14 years today]]></title>
            <link>https://medium.com/@justinauciello/superstorm-sandy-14-years-today-1d2880e3492b?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d2880e3492b</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 22:32:20 GMT</pubDate>
            <atom:updated>2026-10-29T22:32:20.077Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The following is a post to Jersey Shore Hurricane News.</em></p><p>Fourteen years ago today, Sandy made landfall in New Jersey.</p><p>I’ve been going through the JSHN archive, which contains nearly 20,000 posts and other records, plus approximately 14,000 JSHN-authored replies, dating back to 2011. There were 572 posts between October 25 and November 6, 2012, alone. And 267 recurring volunteer/donation request posts through June 2014. Reading them again has brought back a lot.</p><p>JSHN was only 14 months old, but people across the area were already using it every day to share what was happening in their communities. Residents sent reports and photographs, asked questions, and helped one another find answers. Sometimes someone would question a report or offer information we hadn’t heard yet. We’d follow up, compare accounts, check with official sources, and publish what we could establish. Often, the responses would tell us what to look into next.</p><p>I’d evacuated South Seaside Park the night before landfall and was holed up in the dining room at my parents’ house inland, keeping up with JSHN. A few hours before landfall, my dad walked in with a big smile on his face, carrying a big bowl of chips and a frosty mug of beer for me. I can still picture him standing there.</p><p>The reports were coming in constantly. People wanted to know what was happening to their homes, whether their neighborhoods were flooding, and how to reach family members. Rumors were everywhere. One of our posts from October 29 read:</p><p>“DO NOT POST RUMORS ON THE WALL — IF YOU HEAR A RUMOR, SEND A PRIVATE MESSAGE TO THE PAGE, AND WE’LL INVESTIGATE”</p><p>And people did. There were so many conversations happening privately, often with people who couldn’t get reliable information about their own streets or loved ones. We’d try to find someone in the area who could tell us what was happening or check a report against other information. There were plenty of questions we couldn’t answer.</p><p>On October 30, we posted:</p><p>“If you need to be rescued, reply here. Authorities are monitoring.”</p><p>Some of those requests are still difficult to read. Exact addresses, water rising, elderly residents and babies inside homes. People desperately trying to get help. With 911 systems overwhelmed in some areas, we worked with the New Jersey Office of Emergency Management to get information about people needing assistance to authorities. We also urged people to call 911 first.</p><p>The days afterward were exhausting. People needed gasoline, food, shelter, and information about neighborhoods they couldn’t reach. I found the old threads where we kept asking, sometimes every half hour:</p><p>“WE’LL CONTINUE TO POST THIS EVERY 30 MINUTES → WHERE CAN WE FIND GAS, FOOD, ICE, GENERATORS, ETC???”</p><p>People responded from their towns with information about what was available. Others would add updates, let us know when something had changed, or answer questions from people they’d never met. We’d check what we could and keep publishing. Often, people were helping one another right there in the comments before I could even get to the questions.</p><p>A tremendous amount of this was happening while contributors were dealing with flooded homes, power outages, and uncertainty about their own families.</p><p>And it went on long after Sandy moved away. JSHN continued covering the recovery through that first winter, well into the following summer, and for years afterward. Residents kept sharing information about rebuilding, asking where help was available, and bringing attention to problems in their communities.</p><p>I know this anniversary brings back painful memories for many. Some of you lost homes, businesses, and places that had been part of your lives for generations. Not everyone returned, and the character of the area has changed considerably.</p><p>Looking through the archive, I’m reminded of how much people did for one another. JSHN couldn’t have known what was happening across so many communities without residents taking the time to share what they knew, often under terrible circumstances. And sometimes people didn’t need an update from us at all. They found the answers by helping each other.</p><p>I think about that today, especially with all the AI-generated images, rage bait, and misinformation circulating online. There’s something worth preserving about people reporting what they’re actually seeing in their own communities, having a place to ask questions, and knowing that someone is taking the time to check the information.</p><p>To everyone who was part of this community during Sandy and the long recovery that followed, thank you for what you did for one another. I haven’t forgotten.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d2880e3492b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Hurricane Helene Revealed About the Information Systems Communities Rely On]]></title>
            <link>https://medium.com/@justinauciello/what-hurricane-helene-revealed-about-the-information-systems-communities-rely-on-be9c987ca26f?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/be9c987ca26f</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 14:22:49 GMT</pubDate>
            <atom:updated>2026-09-16T14:22:49.546Z</atom:updated>
            <content:encoded><![CDATA[<p>A just-published Stanford Social Innovation Review <a href="https://ssir.org/articles/entry/appalachian-resilience-after-hurricane-helene">piece</a> about Appalachian recovery after Hurricane Helene argues that trust is infrastructure.</p><p>The relationships that helped communities respond did not appear after the storm. They had been built over years. The same is true of information. Every community has an information system, whether we plan for it or not, and during a crisis we find out very quickly where information moves, where it stops, who people trust and which institutions are positioned to act.</p><p>I saw this after Superstorm Sandy in New Jersey. People were using Jersey Shore Hurricane News to report conditions that were changing faster than official channels could capture them. The work involved sorting credible reports from incomplete ones and getting urgent information where it needed to go.</p><p>Five years later, after Hurricane Maria, I saw the same problem at a much larger scale in Puerto Rico. Communications systems across the island had been badly damaged, and many communities knew what was happening around them but had few reliable ways to reach institutions and organizations that could respond.</p><p>Through <em>Información Como Ayuda</em>, people across the island reported what they were seeing and hearing. We verified those reports, shared them publicly and routed urgent needs when necessary.</p><p>Technology helped. The system worked through relationships, local knowledge and organizations already embedded in communities. Information had to reach someone who could use it, and the recipient needed enough confidence in the source to act.</p><p>That same pattern appears in the Appalachian recovery. Trust built over years became operational infrastructure after Helene. Existing relationships helped communities move resources when larger systems slowed or failed.</p><p>Information moves through relationships too.</p><p>Crises make those connections easier to see. They also expose where they are weak. Planners already look at other systems this way, asking how they perform under pressure and what happens when part of the network fails.</p><p>Where do people turn when they need reliable information? How does what residents know reach institutions? Where does that flow break down?</p><p>The connection may run through a local news outlet, a community organization, an emergency manager or simply a person everyone knows to call. The relationships between those actors are often informal, which makes the system easy to overlook until something goes wrong.</p><p>Communities need a clearer understanding of how information already moves and where the connections need support. That does not mean creating another platform. It means knowing what already exists and where the weak points are.</p><p>That is part of resilience planning too.</p><p>Local networks can help bridge gaps during a crisis. They cannot carry the full burden of response. They are most useful when what they know can reach institutions with the capacity to act.</p><p>We plan for failure in other systems before it happens. We should do the same with information.</p><p>A disaster should not be the first time we discover how a community’s information system works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be9c987ca26f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From First Dispatch to Rebuilding: The Seaside Boardwalk Fire]]></title>
            <link>https://medium.com/@justinauciello/from-first-dispatch-to-rebuilding-the-seaside-boardwalk-fire-6cfdfcf098ce?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cfdfcf098ce</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 17:18:06 GMT</pubDate>
            <atom:updated>2026-09-09T20:52:07.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-QuQj-Y53_9PfWLcmdLsqA.png" /><figcaption>Flames rip through Kohr’s ice cream shop on the Seaside Park boardwalk about 15 minutes after the first dispatch on September 12, 2013. (Photo: Justin Auciello)</figcaption></figure><p>Thirteen years ago this week, I was home in South Seaside Park when I heard the Seaside Park fire whistle sounding repeatedly through town. I had grown up hearing that whistle and knew what it meant when it kept sounding. Then I received a text saying the boardwalk was on fire.</p><p>The first fire dispatch went out at <strong>2:20 p.m</strong>. on September 12, 2013.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMmLny4YcEOo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMmLny4YcEOo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMmLny4YcEOo%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/80155c88484af6c19e8d0a2f322efc4e/href">https://medium.com/media/80155c88484af6c19e8d0a2f322efc4e/href</a></iframe><p>I was likely on the scene by about <strong>2:28</strong> to <strong>2:30</strong>, and at <strong>2:33:31</strong> p.m. I posted the <a href="https://www.facebook.com/photo.php?fbid=675194762500039&amp;set=a.293573297328856.77386.261650307187822&amp;type=1">first JSHN photograph</a> from the fire: crews were battling a fire at Kohr’s Ice Cream, we were there, and updates would follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMlycI7QZXdhEeCeuzhdeQ.png" /><figcaption>The first photo posted on JSHN by me. These are the first arriving firefighters. Flames were not yet visible. (Photo: Justin Auciello)</figcaption></figure><p>I lived only a couple of miles away. When I arrived, the fire was still concentrated around Kohr’s and Biscayne Candy. From a close but safe distance, I could see flames coming from the Kohr’s building, as captured in the lead image and <a href="https://www.facebook.com/photo/?fbid=675197645833084&amp;set=a.550955013736924">posted to JSHN</a>, as firefighters began what would become an enormous operation. I opened the emergency scanner on my phone and started reporting through Jersey Shore Hurricane News while <a href="https://whyy.org/articles/seaside-parkheights-boardwalk-fire-under-control/">communicating with WHYY/NewsWorks</a>, where I was covering the Shore.</p><p>The JSHN archive preserves those first minutes better than my memory does. At <a href="https://www.facebook.com/photo/?fbid=675207792498736&amp;set=a.550955013736924"><strong>2:39:56</strong></a>, more companies were arriving, the adjacent building was burning and firefighters were trying to protect the Sawmill and nearby structures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MSC4i-H6k0kWkfBmmc0Duw.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>Video <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675198552499660">followed within minutes</a>. By about <strong>2:52</strong>, the fire had reached a third alarm and <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675202802499235/">water supply was already becoming an issue</a>. <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675211422498373">More video</a> <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675224749163707/?__cft__[0]=AZgzsnBOHmwlK4aTbTitNUtynuJoqt5mL_tDFSrJnTKVgeqHcjuiq-BSQiv8wwFxfphXNlArzpDuZsvwaAt2hd8HtucOh7Cic1t9r6skt_1aHtvmbEeAdJlAvhwj9CoLEXx4h0_mpBP48JXkdXE8_g&amp;__tn__=%2CO%2CP-R">then followed</a>.</p><p>At <strong>3:05</strong>, I was standing about 100 feet away when part of the Kohr’s building collapsed. I wrote that the heat at my position had become considerably hotter. At <strong>3:14</strong>, <a href="https://www.facebook.com/photo/?fbid=675213145831534&amp;set=a.550955013736924">the upper portion came down</a>, several explosions could be heard, embers were moving north and radio traffic indicated that the fire might be traveling beneath the boardwalk. Kupper’s and Park Seafood were fully involved. By <strong>3:39</strong>, the structure I had <a href="https://www.facebook.com/photo/?fbid=675221472497368&amp;set=a.550955013736924">first seen burning was gone</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVxlzEthtPHvkNOFWghreg.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>I had been there only minutes after the first dispatch, before the fire became the regional and national story people remember now. JSHN was reporting it in real time from inside the community where it was happening.</p><p>Less than a month later, Caroline O’Donovan at Nieman Lab <a href="https://www.niemanlab.org/2013/10/journalists-of-the-jersey-shore-how-a-novice-reporter-built-a-news-network-from-scratch/">opened a profile of JSHN</a> not with Hurricane Sandy, which had brought the project national attention, but with the September 12 fire. She reconstructed the beginning of the coverage, noting the first post before 2:34 and 27 more JSHN posts that day as photographs, video, observations and hundreds of community comments moved through the page.</p><p>I was doing ordinary field reporting: watching the fire, photographing it, shooting video, listening to emergency radio traffic, talking with people and reporting developments to WHYY. At the same time, people elsewhere around the scene were sending photographs, observations and questions through JSHN. They could see things I could not see from wherever I happened to be standing.</p><p>That became the rhythm of the afternoon. I would observe something directly, hear something over the radio or receive information through JSHN, work to establish what I could, then report through one or both channels. Some contributor information stayed on JSHN. Some became leads. Some moved into WHYY’s reporting after additional verification and reporting.</p><p>At one point I almost got arrested while recording near the scene. The perimeter seemed to change every few minutes. I moved on, then ran into a much simpler problem that could have stopped the reporting just as effectively: my phone was nearly dead.</p><p>In 2013, that phone was my mobile newsroom. I was using it to post to JSHN, communicate with NewsWorks editors and sources, take photographs and video, listen to radio traffic and receive reports from people around the area.</p><p>A woman who lived on the third floor of a condominium at Ocean and Stockton recognized me as the person who ran Jersey Shore Hurricane News and invited me upstairs so I could charge it. Her apartment had a balcony with a direct view of the fire. For part of that afternoon, her home became an improvised newsroom.</p><p>By <strong>4:04 p.m.</strong>, I had moved across the street from the boardwalk from where I started and was reporting flames coming from structures north of the Sawmill and Funtown Arcade. At <strong>4:42</strong>, from the Ocean Terrace condominiums at Stockton and Ocean, I recorded the fire continuing north with <a href="https://www.facebook.com/photo/?fbid=675233192496196&amp;set=a.550955013736924">several structures fully engulfed and Jack and Bill’s burning</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Wf-d3UkM3rjMw6gbAv_vw.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>That afternoon, the community was part of the reporting in ways that went well beyond sending tips. People supplied photographs, observations, corrections, questions and vantage points. Someone literally opened her home so the reporting could continue.</p><p>The fact that this was my own community mattered too. I had grown up in Seaside Park about two miles from the fire. These were not unfamiliar business names I was learning from a damage list. I knew where Kohr’s sat in relation to Kupper’s, Park Seafood, the Sawmill, Funtown Arcade, Jack and Bill’s and Maruca’s. I knew the boardwalk because I had spent my life walking it.</p><p>During the fire, WNYC put me on the air and I found myself trying to explain what I was watching to people far beyond Seaside. I talked about growing up nearby and going to the boardwalk for ice cream as a kid. I remember describing it as watching my childhood burn.</p><p>That familiarity also helped with the reporting. When someone asked about a particular building or stretch of boardwalk, I knew exactly what they meant. Later, when the fire became folded into the larger Sandy narrative, it helped preserve an important distinction.</p><p><em>The Seaside Park boardwalk itself had not been destroyed by Sandy. </em>Much of it remained intact. Funtown Pier had suffered catastrophic damage, but the commercial boardwalk beside it survived. That became important after investigators determined that the September fire was connected to Sandy-damaged electrical equipment beneath a boardwalk that had remained standing above it.</p><p>By <strong>5:20 p.m.</strong>, NewsWorks identified me as the editor of Jersey Shore Hurricane News reporting from the scene and carried my assessment that <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675252395827609/?__cft__[0]=AZhm2RutSGJB7TfqMVWYVxoCyo_ewCgfW5Y2_WwQ6ssT5ru0PBobTeHR36ja8rA3hBfD8CsBGr47vuEwiM-41tz8ziaj5Iej7a-MHDhzAe5_vx4sXZAFvvGKzYnw3hj9AVglICFYw4zMg96AMWLnDA&amp;__tn__=%2CO%2CP-R">most of the boardwalk between Stockton and Porter avenues appeared to be destroyed</a>. Jack and Bill’s, Kupper’s French Fries and Park Seafood were among the businesses gone.</p><p>On JSHN, the reporting was more granular. People were asking about individual businesses and streets, sharing photographs and supplying views from places I could not reach. WHYY was building the larger live story around official briefings, sourcing and developments from the scene.</p><p>At <strong>5:43</strong>, another JSHN video showed thick black smoke and flames intensifying as part of Jack and Bill’s collapsed. At <strong>6:18</strong>, I reported to NewsWorks that the fire appeared to have moved north of Maruca’s and that firefighters were cutting into the boardwalk near Lincoln Avenue in an effort to stop it.</p><p>At <strong>6:40</strong>, I reported another increase in fire intensity immediately north of Funtown Arcade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlLZz0qeU4qpK5bQ4fKC6w.png" /><figcaption>(Screencap: Justin Auciello)</figcaption></figure><p>Emergency radio traffic indicated that firefighters were preparing a water line from Barnegat Bay, and a Forest Fire Service helicopter had been requested in case a water drop became necessary.</p><p>Information moved in both directions. JSHN contributors extended what I could see from the ground. Some of that information, once established, moved into WHYY. Reporting and official information from WHYY moved back through JSHN, where people added local knowledge or raised the next question.</p><p>By <strong>7:21 p.m.</strong>, JSHN was reporting a ten-alarm fire and a state of emergency in Seaside Park. At <strong>7:42</strong>, I posted a photograph contributed by Kim Hino showing another view of the fire: the remnants of Kohr’s in the foreground, another structure burning northeast of the Sawmill and both the Sawmill and Funtown Arcade still appearing intact from the exterior.</p><p>At <strong>8:11</strong>, I reported that <a href="https://www.facebook.com/photo/?fbid=675306779155504&amp;set=a.550955013736924">flames had increased again in several structures</a>. The shell of Jack and Bill’s had collapsed about fifteen minutes earlier. Beachcomber had sustained considerable damage, but radio traffic indicated that the Lincoln Avenue trench had stopped the fire from advancing farther north.</p><p>By just before <strong>8:50</strong>, <a href="https://www.facebook.com/photo/?fbid=675346172484898&amp;set=a.550955013736924">crews had made considerable progress</a>. Fire remained in several structures, but the flames were no longer as intense.</p><p>At <strong>8:52</strong>, I shot video from Stockton and Ocean avenues that WHYY incorporated into its live coverage. The southwest wind was so strong that I could stand remarkably close to the southern end of the fire zone and barely smell smoke. I told NewsWorks that I was close enough that I could almost hit the fire with a baseball because almost everything was being blown east toward the ocean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWlAlAjuHky8zcx8h-eodw.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>My photographs and video were moving through both JSHN and WHYY.</p><p>One of the earliest images became the earliest known published photograph of the fire. I had taken it while Kohr’s was still intact, catching a firefighter running as a fireball erupted behind him. It later appeared on the front page of The Star-Ledger and was also used by The New York Times. The photograph came from the very beginning of the fire, before the Kohr’s building collapsed.</p><p>The reporting was also moving far beyond the Shore.</p><p>While I was still covering the fire and its immediate aftermath, news organizations around the country and overseas were contacting me for photographs and video. CNN requested high-resolution fire video. ABC asked to use footage for <em>Good Morning America</em>. CBS News and NBCUniversal requested photographs. The Wall Street Journal sought high-resolution images. The European Pressphoto Agency contacted me about distributing fire photographs internationally.</p><p>I was still moving around a fire scene a few blocks from where I had grown up while pieces of what I was seeing were moving through much larger news organizations.</p><p>JSHN had been built primarily to serve people in and around the Jersey Shore. During the fire, the same reporting stream residents were using to find out whether a particular business was still standing was also supplying photographs, video and eyewitness reporting well beyond the area.</p><p>At <strong>9:15</strong>, an orange glow remained east of Jack and Bill’s. Smoke continued rising and <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675324579153724/?__cft__[0]=AZhG0QNxONYEdL-jv5yb69AvgbmoWuNhgrGoxrcoTcBN2mRQ5xZtefiK0LCrhqkgZIN_Pbu1SJUv0NQKuclI5HFHn1cpEiKeJOny0xwTi5sdXHo9iAn4tD7ihuNczphi4dbNEhd65GtXiho-cIMP8Q&amp;__tn__=%2CP-R">firefighters were still streaming water</a> over several buildings.</p><p>By <strong>10:55 p.m.</strong>, JSHN reported that the blaze was about 70 percent contained and tried to clarify what had survived.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mvv1I_WbV-FV9bxuHUM_3w.png" /><figcaption>(Screencap: Justin Auciello)</figcaption></figure><p>The Sawmill, almost directly across from where the fire had begun, remained standing. From what I had observed between about 2:35 and shortly before 10, the building appeared to have sustained smoke, water and heat damage, but significant portions were intact.</p><p>The fire was eventually declared under control before midnight. Firefighters remained in place, roads stayed restricted and portions of the destroyed boardwalk continued burning beneath collapsed structures.</p><p>I finally left to decompress at home. When I got there, I noticed that the buttons on my short-sleeve button-down were fastened incorrectly. It was the first shirt I saw when I ran out of the house more than 10 hours earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nil-1izj-AR1ihrjQnJctQ.png" /></figure><p>I went back the next morning.</p><p>At <strong>8:46:29 a.m. </strong>on Friday, September 13, JSHN posted a substantial daylight report from the scene. The fire was still smoldering. White smoke was blowing out over the ocean and there was a distinct smell of burned wood south of Funtown Pier. Firefighters were hitting hot spots inside the charred remains. Investigators were there but had not yet been able to fully work through the scene.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*oTE6VdgyFCAx8eSmI2OliA.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>A few hundred feet away, surfers were catching clean waves.</p><p>That remains one of the clearest memories of the morning. Smoke was rising from the boardwalk while people were surfing nearby, the ocean moving along as if nothing extraordinary had happened on land.</p><p>The <a href="https://whyy.org/articles/the-morning-after-the-seaside-park-boardwalk-in-ruins/">NewsWorks dispatch from the scene that morning explicitly sent readers back to Jersey Shore Hurricane News</a> for the previous day’s real-time coverage, describing it as running from moments after the blaze began until the fire was brought under control before midnight.</p><p>The morning kept producing news. At about <strong>9:30</strong>, three Seaside Park police officers who had worked the fire scene were injured when seating in the back of a transport vehicle gave way and they fell onto the roadway near O Street and Ocean Avenue. Medevacs were dispatched to transport them to a trauma center. I <a href="https://www.facebook.com/photo/?fbid=675604429125739&amp;set=a.550955013736924">photographed the aftermath</a>, and the image was published through both JSHN and WHYY.</p><p>At <strong>10:41</strong>, JSHN posted Governor Chris Christie’s announcement that the fire was 95 percent contained. Minutes later he said the investigation would probably take days. At <strong>10:56</strong>, the page <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/675616009124581">carried his description of the trench</a> at Lincoln Avenue as the decisive moment in keeping the fire from spreading farther north.</p><p>At <strong>11:44</strong>, I posted another photograph. The boardwalk was still smoldering, and amid the wreckage a Funtown Pier sign remained standing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ipoTYLwVumLu1zTHLQpvoQ.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>At <strong>6:03 p.m.</strong>, almost twenty-eight hours after the first dispatch, firefighters <a href="https://www.facebook.com/photo/?fbid=675754455777403&amp;set=a.550955013736924">were still dousing hot spots</a> just south of Jack and Bill’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*K7eZKNVi4340ocg7rQdL2w.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>Minutes later, <a href="https://www.facebook.com/photo/?fbid=675757072443808&amp;set=a.550955013736924">I photographed</a> Seaside Park firefighter Mike Tumolo’s jacket hanging from a post, with smoke, structural remnants and the Funtown sign in the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U7uf-aJmOiQQ6yz2-HzbJA.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>Then JSHN contributor Blaire Lornez <a href="https://www.facebook.com/photo/?fbid=675773859108796&amp;set=a.550955013736924">sent an aerial image</a> of the sun setting over the bay with the fire smoldering in the foreground.</p><p>By then the questions had changed. During the fire, people wanted to know where the flames were moving. The next day they wanted to know what had survived, <a href="https://www.facebook.com/photo/?fbid=675824212437094&amp;set=a.550955013736924">what was open</a>, whether the fire could flare again and what would happen next.</p><p>That continued through the weekend. JSHN corrected reports circulating elsewhere that investigators had deemed the fire suspicious. They had not. The investigation remained open. We also <a href="https://www.facebook.com/photo/?fbid=676028982416617&amp;set=a.550955013736924">reminded people that most of the Seaside Heights boardwalk</a> had not burned and that people were already walking the unaffected sections.</p><p>Firefighters continued working the ruins. Contributor photographs showed people who had been there from the beginning still dealing with hot spots long after most of the live television coverage had moved on.</p><p>People also began responding to the loss in less official ways.</p><p>Jack and Bill’s had been part of this stretch of boardwalk for generations. After the fire, friends and regulars <a href="https://whyy.org/articles/first-look-at-what-remains-after-the-devastating-nj-boardwalk-fire/">held an “Irish Wake”</a> for it, complete with bagpipers, pallbearers and urn with ashes from the bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*tShVhhBHAEbxUyMU9aqIYw.png" /><figcaption>The Irish Wake for Jack and Bill’s at Aztec bar on the boardwalk in Seaside Heights. (Photo: Justin Auciello)</figcaption></figure><p>It would be easy to treat that as a quirky Shore story. It was really about what people had lost. They were mourning a place where they had worked, met friends, spent summer nights and accumulated years of memories.</p><p>The same thing was visible inside JSHN. Contributors and commenters recognized storefronts from fragments in photographs, asked about businesses just outside the frame and supplied memories along with information.</p><p>On <strong>September 17</strong>, <a href="https://www.facebook.com/JerseyShoreHurricaneNews/videos/677525402266975">I was there when investigators announced</a> that the fire was accidental and had originated beneath the structure housing Biscayne Candies and Kohr’s, where electrical equipment and wiring compromised by Sandy floodwater had failed.</p><p>For WHYY, <a href="https://whyy.org/articles/fire-investigators-superstorm-sandy-contributing-factor-to-boardwalk-fire/">I reported beyond the announcement</a>, talking with experts about the effects of saltwater intrusion on electrical systems and how damage could persist long after flooding appeared to have receded.</p><p>The story was sometimes described outside the area as if Sandy had destroyed the Seaside Park boardwalk and the fire then destroyed its replacement. That was not what happened. Funtown Pier had been devastated by Sandy, but much of the Seaside Park boardwalk remained intact. The fire exposed a more complicated legacy of the storm: infrastructure beneath the surviving boardwalk had been compromised even though the boardwalk above it remained.</p><p>Exactly one week after the fire, I <a href="https://whyy.org/articles/a-week-later-touring-the-seaside-boardwalk-fire-scene/">went inside the closed fire zone</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*uoRI82-rE3D_tKt7Pq6b1Q.png" /><figcaption>Me under the still-standing entrance to Funtown Pier sign.</figcaption></figure><p>I entered the boardwalk between Kohr’s and Biscayne Candy at <strong>about the same time of day the first fire units had been dispatched seven days earlier: 2:20 p.m.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-IidsaO9ie1jFMKGDeoPw.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>A week earlier, firefighters had been sent to a report of flames beneath a functioning boardwalk. About thirteen minutes later, I was posting from the scene. Seven days later, I was standing in almost the same place surrounded by what remained.</p><p>Before walking through it, I knew what had burned. I had watched it happen, photographed it and spent the intervening week looking at images supplied by JSHN contributors. Seeing it slowly on foot was different.</p><p>I remember closing my eyes and thinking about what that part of the boardwalk normally sounded and smelled like: people sitting at Park Seafood, french fries cooking at Kupper’s, custard coming from the machines at Kohr’s, games and music and conversations blending into the background noise of a summer night.</p><p>When I opened my eyes, almost everything capable of burning was black.</p><p>Charred wood, twisted metal and wiring extended through the ruins. Nails that once held the boardwalk down remained in orderly rows in the sand even where the boards themselves were gone. The Funtown Pier sign was down. Beneath broken concrete, material was still smoldering in places.</p><p>The destruction was uneven, which made the walk stranger. The Sawmill remained standing. Funtown Arcade had survived better than seemed possible from some of the fire night images. Short stretches of familiar boardwalk remained beside spaces where almost everything had disappeared.</p><p>A JSHN commenter had described the scene as looking like “doomsday.” I later brought that comment into the WHYY piece about the walk.</p><p>I wrote then that those businesses meant more than buildings because that was where we went to meet.</p><p>I still think that is the simplest explanation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCXm-fWT1flXK2M9A-wtRQ.png" /><figcaption>(Photo: Justin Auciello)</figcaption></figure><p>The reporting on Park Seafood brought that down to one family. Owner Nick Dionisio had already dealt with Sandy flooding the restaurant, the death of his father, his mother being displaced from Ortley Beach and a difficult 2013 summer. Then the fire destroyed the business.</p><p>When I <a href="https://whyy.org/articles/park-seafood-owner-vows-to-return-following-devastating-seaside-boardwalk-fire/">interviewed him afterward</a>, he was already talking about returning.</p><p>What I did not understand that afternoon was that I would keep reporting from those same few blocks for years.</p><p>In October, the <a href="https://whyy.org/articles/seaside-boardwalk-demolition-debris-removal-advancing-rapidly/">subject became demolition</a>. Heavy equipment moved through the fire zone while JSHN contributors continued documenting the changing landscape. Familiar buildings became wreckage, the wreckage disappeared and <a href="https://whyy.org/articles/seaside-boardwalk-fire-cleanup-continues-to-rapidly-advance/">new sight lines opened</a> where structures had stood for decades.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*pemiqLfJVPksSJD3KghbBg.png" /><figcaption>(Photo: Joe Verderosa)</figcaption></figure><p>By the end of October, <a href="https://whyy.org/articles/aerial-video-seaside-boardwalk-fire-zone-now-just-mostly-sand/">aerial imagery</a> showed much of the four-block fire zone reduced almost entirely to sand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1acPlXAA6OZmHxouAZfIQ.png" /><figcaption>(Photo: Mercer Photography)</figcaption></figure><p>Then the subject changed again.</p><p>Over the winter and into spring 2014, JSHN followed the reconstruction almost board by board. We reported when the small publicly owned piece of Seaside Heights boardwalk damaged by the fire was completed. Contributor Kevin Michelson documented pilings going into the privately owned Belle Freeman property in Seaside Heights while the Seaside Park portion awaited Land Use Board approval.</p><p>After that approval, he reported again when the first pilings went into the Seaside Park section between Porter and Stockton. Construction moved across the sand toward the goal of reconnecting the two towns.</p><p>By late May, <a href="https://whyy.org/articles/aerial-video-of-seaside-boardwalk-construction-progress/">aerial footage showed</a> a new boardwalk advancing through the fire zone. The <a href="https://whyy.org/articles/first-business-returns-in-seaside-park-since-boardwalk-fire/">Sawmill reopened in June</a>, nine months after the fire, with customers sitting outside again beside newly laid boards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*GvXt-ZHphJG0IixAXmaCfg.avif" /><figcaption>(Photo: Joe Standard/PR Aerial Photography &amp; Video Services)</figcaption></figure><p>Just before the Fourth of July, the final board went down and pedestrians could once again walk continuously between Seaside Park and Seaside Heights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*7ifhawJlYOCxV8AJkwlnyg.png" /><figcaption>Late June 2014. (Photo: Justin Auciello)</figcaption></figure><p>In September, I had watched boards burn. In October, we watched the wreckage disappear until much of the area was bare sand. In spring, JSHN contributors documented pilings being driven into that sand and new decking advancing across it. By July, the physical connection was restored.</p><p>The businesses took much longer.</p><p>Jack and Bill’s eventually reemerged away from the boardwalk as Jax Garage. More than eight months after the fire, manager Steven Pasquarosa told JSHN how compressed the preceding two years had felt: Sandy flooded them, they rebuilt, and then the fire burned them out again. They found another building and started over.</p><p>Park Seafood took years. Original Kohr’s and 3 Brothers Pizza also eventually began returning. By April 2017, <a href="https://whyy.org/articles/building-construction-continues-on-boardwalk-consumed-by-fire/">I was still reporting through WHYY</a> from essentially the same ground as seven permanent buildings finally rose along the Seaside Park boardwalk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkFygHsv6ZaFy5wcwRW9_Q.png" /><figcaption>(Photo: Jim Brill)</figcaption></figure><p>Almost four years had passed.</p><p>Looking through the archive now, what interests me most is the continuity.</p><p>The next morning, I was back. A week later, I walked into the origin area at essentially the same time the original dispatch had gone out.</p><p>Then the questions kept changing. Why had it happened? Which businesses would return? What would happen to the empty land? When would the boardwalk reconnect? Would the businesses actually come back?</p><p>JSHN and WHYY let me follow those questions in different ways. JSHN provided a continuous community reporting network drawing information from people who knew the place. WHYY gave me editors, a newsroom and the space to report more deeply on the investigation, infrastructure, recovery and the people whose livelihoods had been tied to those buildings.</p><p>Looking back, I can see more clearly what was happening around the reporting itself. We had already seen versions of it during Irene and Sandy, and would see it again during numerous smaller events before and after them. Residents were not simply receiving information. They were contributing observations, photographs, questions and local knowledge. Journalism was one part of a larger information network that also included emergency responders, government officials, businesses and people who knew the place intimately. Information moved back and forth among those different actors, and the work did not end when the immediate crisis passed. The same network kept helping people understand what had happened, what remained uncertain and what came next.</p><p>Less than a month after the fire, Nieman Lab used the event to explain how JSHN worked: a reporter physically inside the event while a much larger community contributed to the reporting around him.</p><p>Nobody decided at 2:20 p.m. on September 12, 2013 that this would become a four year reporting project. There was simply another question every time the place changed.</p><p>What matters more to me thirteen years later is that we stayed with the place after being first stopped mattering: through the night, the next morning, the smoldering days afterward, the investigation, demolition and years of rebuilding.</p><p>The fire lasted hours. What happened on those few blocks afterward took years, and the reporting followed it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cfdfcf098ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ida Changed Where New Jersey Was Looking Again]]></title>
            <link>https://medium.com/@justinauciello/ida-changed-where-new-jersey-was-looking-again-fd6967212f8b?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd6967212f8b</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 16:13:55 GMT</pubDate>
            <atom:updated>2026-09-02T16:13:55.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJwa0-UkqR7lZ45chqzpYw.jpeg" /></figure><p>Five years ago, Ida changed where New Jersey was looking again. Irene, ten years earlier, had been a stark reminder of what Floyd showed in 1999: some of New Jersey’s worst tropical impacts can happen well inland. Then Sandy shifted much of the attention to the coast.</p><p>During Ida, some of the worst impacts were away from the coast, and flooding quickly became the story. JSHN had started a decade earlier during Irene, before years of coastal recovery, resilience planning and efforts to reduce risk after Sandy.</p><p>The Shore was still part of Ida, but by the evening of September 1, 2021, JSHN was following destructive tornadoes across South and Central Jersey and increasingly severe flooding farther north.</p><p>At 9:37 p.m., I posted: “We’ve been here for a decade and have never seen this type of rain so quickly.” Less than two hours later: “We can’t keep up with the flooding reports everyone is sharing…”</p><p>By the next morning, the focus had shifted to rescues, rising rivers and the first recovery needs.</p><p>We had seen the pattern before with Irene. Ida brought it back into view after nearly a decade shaped by Sandy.</p><p>(Image: Rutgers University Archives)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd6967212f8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Case for a Federated Civic Information Network]]></title>
            <link>https://medium.com/@justinauciello/the-case-for-a-federated-civic-information-network-da47525dee2f?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/da47525dee2f</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 12:45:26 GMT</pubDate>
            <atom:updated>2026-08-31T12:51:04.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_oOGaCgcW9V-b-vdw8oyw.jpeg" /><figcaption>Jersey Shore Hurricane News, October 30, 2012. During Sandy, people used JSHN to report rescue needs while the New Jersey Office of Emergency Management monitored the page and worked through the formal response system. The arrangement illustrates how a federated civic information network can work in practice.</figcaption></figure><p>The problem is no longer simply a lack of information. What is still scarce is trusted local capacity to help people figure out what is actually going on.</p><p>Trust gets people in the door. They keep coming back if the source is useful, especially when things get confusing or the volume gets high. The harder work is turning scattered signals into enough shared understanding that people can make sense of what is happening.</p><p>I think we should be building more local capacity to do that, and connecting it through a federated civic information network. By federated, I mean that the pieces remain independently operated but can connect and work together when useful.</p><p>As AI makes polished information easier and cheaper to produce, more of the difficult work sits elsewhere: figuring out what people are actually seeing, what can be verified and what deserves attention. AI can help when the volume gets high by grouping reports, spotting likely duplication and surfacing questions that keep going unanswered. But the consequential judgments still belong with people who understand the community and are accountable there.</p><p>Most places already have pieces of such a system. Different institutions hear different things and reach different people. What they often lack are the connections that allow those signals to become a usable picture.</p><p>Journalism is one important node in that broader civic information ecosystem. Its reporting, verification and accountability functions are essential. But that does not mean every information flow has to pass through a newsroom.</p><p>The point is not to make any one institution the permanent center. It is to help communities understand what is happening and connect information with the people who can do something useful with it.</p><p>The need or problem is what organizes the network, with different nodes becoming more or less central depending on what is required. Emergency management may hold operational authority in a crisis, journalism may become more central around accountability, and a nonprofit or public agency may hold the key capacity during a service disruption.</p><p>Different parts of a community hold different kinds of knowledge and capacity. Residents may have firsthand knowledge, agencies operational authority, and libraries or community organizations relationships and reach. Planners can add institutional, regulatory and spatial context, while service providers may see emerging needs before others do.</p><p>A local node could serve as one entry point for community reports, keep track of where they came from, verify what it can and recognize what it cannot resolve locally. It could route questions or signals to people or institutions with the right expertise or authority, help connect needs with available community capacity, then pay attention to whether anything useful comes back.</p><p>A recent example came during New Jersey’s SNAP disruption, when JSHN collected information from multiple sources, checked it, followed the questions that surfaced and adjusted what we were looking for as new gaps became visible. I wrote separately about what that experience suggests for a federated civic information system.</p><p>Communities would not all have to organize this the same way. A node might be one organization or several. Nodes could share tools, methods and supporting capacity while control stays local. They could also provide redundancy: if one pathway is overloaded or unavailable, another trusted node may still be able to receive, interpret or route a signal. It also means the whole system does not depend on any one organization or person always being there. Some information could move between them when there was a reason for it. Most would stay local.</p><h3>I had seen the basic logic before</h3><p>In 1992, when I was in sixth grade, I ran a dial-up bulletin-board system from a Macintosh Classic in my bedroom and became FidoNet node 1:2605/615. With a 2400-baud modem, that little computer could exchange messages with independently operated systems around the world.</p><p>Each BBS had its own sysop and local community. They did not have to become one giant service to be connected. Common protocols allowed information to move while each system remained independently operated.</p><p>Years later, I built something much closer to the civic information model with Jersey Shore Hurricane News. The idea from the beginning was not simply to publish information, but to create a network of people who could help keep one another informed.</p><p>People sent observations, photographs and questions. I then verified, contextualized and published to the wider community. Other times a question or signal needed to go somewhere else, like a referral to a government service, and the job was to connect it with someone who could respond and bring what we learned back to the community.</p><p>JSHN’s relationship with the New Jersey Office of Emergency Management became one of the clearest examples.</p><h3>What Sandy showed</h3><p>The NJOEM relationship began well before Sandy. During Hurricane Irene, I was told that state emergency management telecommunicators were monitoring JSHN because it was a new source actively disseminating information during the storm. They did not know who was behind the service or whether it would cause public alarm. Less than three months later, NJOEM’s external affairs officer reached out, asking to meet about emergency management issues and inviting me to tour the state’s Regional Operations Intelligence Center and Emergency Operations Center.</p><p>The relationship developed from there. In March 2012, NJOEM invited me to serve on the media panel for a Basic Public Information Officer training course, representing social media and JSHN alongside a traditional media representative.</p><p>After the June 2012 derecho knocked out power across parts of New Jersey, NJOEM asked JSHN to clarify that generators being deployed in Atlantic County were intended for traffic signals, not individual residences. They also asked us to steer people away from sending unsolicited food and goods into affected areas because those donations could create additional problems for responders.</p><p>JSHN had access to a large public network and could see how people were responding to an emergency. NJOEM had operational knowledge about what responders needed and what could make their work harder. Information could move between those perspectives, and what we told the community could change accordingly.</p><p>By the time Sandy approached, that kind of exchange had become familiar. NJOEM communicated directly with us about the forecast, evacuation information and public messaging. I had alerted NJOEM about the many signals I was detecting that there was growing chatter about people deciding to remain at home in storm surge risk areas and the potential for 911 to become overloaded. Its external affairs officer thanked JSHN for sticking with National Weather Service and National Hurricane Center information. When reports about evacuation orders began circulating, I could go directly to NJOEM to find out what was actually confirmed.</p><p>So when Sandy arrived, we were not trying to establish a relationship in the middle of a catastrophe. We already knew how to reach one another and had experience exchanging information under pressure.</p><p>As local 911 and emergency communications came under severe strain, distress reports reached JSHN through Facebook comments and messages and through people trying to relay information for others. Some people said they could not get through to 911. At the height of the surge, I was in regular communication with NJOEM and sent them a JSHN thread containing people who needed rescue. NJOEM responded that emergency systems were overwhelmed and that it would try to follow up.</p><p>Soon afterward, NJOEM sent a message to me to post to the broader JSHN community explaining that phone problems were affecting local emergency authorities. It said the agency was monitoring the JSHN page and trying to get rescue requests to local officials, while still urging people to continue calling 911.</p><p>Mary Goepfert, formerly with NJOEM, later recalled the role of the New Jersey State Police Public Safety Telecommunicators, writing that they played “a key role in tracking and responding to those FB calls for help.”</p><p>One of the posts from that night reduced the arrangement to a few words: “If you are still trapped or know somene who is, please reply here.” That may be the clearest expression of what the network had become. JSHN was the public facing intake point at that moment, while operational authority remained with emergency management.</p><p>JSHN was not 911 and was not trying to become emergency management. But we had a trusted channel people were already using and conversational access to a geographically dispersed public. We could ask for the information that made a report more useful: Where exactly are you? Who is there? What is happening now? Is there a way to contact them? NJOEM had capabilities we did not: authority, operational coordination and the ability to dispatch emergency resources.</p><p>The information also moved in the other direction. After Sandy, I contacted NJOEM because rumors about the water supply were spreading rapidly. Rather than simply sending back a correction, they asked how much activity I was seeing around the issue because they were trying to determine its scope and intensity. The same relationship was used to work through other information problems, including rumors about looting and FEMA food vouchers.</p><p>This was more than a government agency sending alerts through a popular Facebook page. The community generated signals. JSHN could detect patterns across them. NJOEM could supply authoritative information or operational context, and that could move back into the community.</p><p>Neither network needed to become the other. They needed to connect, with responsibility shifting according to what each could actually do. The state did not need JSHN to become government, and JSHN did not need NJOEM to become a community conversation. Each had different relationships, information and capabilities. The value was in interoperability and, in that moment, redundancy. The relationship that made that possible had been built before Sandy.</p><h3>Another kind of connection</h3><p>In 2013, I began reporting daily for WHYY/NewsWorks while continuing to operate JSHN independently. <a href="https://medium.com/@justinauciello/the-bridge-is-part-of-the-infrastructure-4b0b12878e1e">That created a different kind of connection.</a> JSHN had a large, trusted, geographically distributed community network. WHYY had newsroom capacity, institutional reach and the ability to support deeper reporting.</p><p>Something surfacing through JSHN could become a reporting question that I pursued through WHYY. That reporting could then come back through JSHN, where people might add context, raise another question or point to something we had missed.</p><p>Nobody designed the arrangement as a federated civic information network, but retrospectively, that is close to how it functioned. JSHN remained an independent local node while gaining access to capacity it did not have to build itself.</p><p>A trusted local node does not necessarily need to become bigger. It should be able to reach outward for help while keeping its relationship with the community local.</p><p>Which part of the network matters most can change with the problem. Federation allows those connections without requiring one institution to permanently organize the rest.</p><h3>Information as Aid</h3><p>After Hurricane Maria, I led the development and field operation of Internews’ <a href="https://medium.com/@justinauciello/the-bridge-is-part-of-the-infrastructure-4b0b12878e1e">Information as Aid</a> program in Puerto Rico, where basic infrastructure was severely degraded. During a crisis, useful information can itself function as aid.</p><p>The work was not simply getting information out. We looked first at how people were finding and sharing information after much of the normal communications infrastructure had failed, then built a two-way system around what communities were asking and experiencing rather than simply what institutions wanted to tell them.</p><p>Information moved through radio, community groups and informal networks. We had to hear what people needed, make sense of what was coming in, work questions through the system and bring something useful back.</p><p>Information as Aid is the clearest example in my own experience of a civic information system deliberately developed from the ground up. JSHN’s relationships with institutions such as NJOEM and WHYY show the federated part more directly.</p><p>There are already systems that solve pieces of this problem. The 211 network has more than 200 locally operated agencies working every day to connect people with services and resources, and that role continues during disasters. Community Information Exchanges connect organizations through shared resource directories and closed-loop referrals. City Bureau’s <a href="https://www.documenters.org/">Documenters Network</a> connects locally operated programs through common technology, training and support. CDAC-supported national and subnational platforms establish relationships, roles and feedback channels before disasters so they are already in place when a crisis occurs.</p><p><a href="https://outliermedia.org/">Outlier Media</a> in Detroit has built a newsroom around residents’ information needs, using two-way texting to let people request information, raise problems and connect directly with reporters. Those conversations can also reveal information and accountability gaps that shape further reporting. <a href="https://representovertown.com/">Represent Overtown</a>, established in Miami in 2026, is building a community-led newsroom and communications hub that describes itself as shared local infrastructure, owned, governed and shaped by the community.</p><p>Open Referral takes on another piece. Its Human Services Data Specification gives independent information systems a common way to exchange structured resource data.</p><p>What still appears to be missing is a mature, general-purpose civic information system that puts these pieces together across institutions and informal networks: locally controlled nodes that operate continuously, keep track of where information came from, make sense of what they are hearing, route signals toward people who can do something with them, and bring useful understanding back to the community. Such a system could also provide redundancy when normal information channels are under stress.</p><p>None of this requires inventing every piece from scratch. <a href="http://linkedin.com/pulse/strengthening-civic-information-network-we-already-have-auciello-1c3se/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base%3BmlmGN2zZSJuO4tpEMePH5A%3D%3D">Most of the pieces already exist somewhere.</a> What they generally do not do is work together as one persistent civic information network.</p><h3>Can the system travel?</h3><p>JSHN has already shown that much of this can work in practice. Other models, including Outlier Media, Represent Overtown, 211, Community Information Exchanges, Documenters and humanitarian information systems, demonstrate different pieces of the same broader architecture.</p><p>What interests me now is how those pieces can connect without requiring every community to build the same thing.</p><p>That does not mean reproducing any one organization or model exactly. Communities would need to build around their own people, institutions, needs and relationships.</p><p>Some of the machinery can be shared: ways of listening, checking information, connecting scattered reports, routing questions or signals to people who can act on them, and returning useful information to the community.</p><p>Trust, judgment and local relationships cannot be imported. They have to be built in place.</p><p>Independent local nodes can still use shared methods and draw on one another when useful, without giving up local control.</p><p>JSHN gives me a long-running laboratory for understanding what that requires. The broader field shows that the pieces can take many forms. The next question is what it takes to connect them so information can move more reliably between the people who have it and the people who can use it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da47525dee2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bridge Is Part of the Infrastructure]]></title>
            <link>https://medium.com/@justinauciello/the-bridge-is-part-of-the-infrastructure-4b0b12878e1e?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b0b12878e1e</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Fri, 28 Aug 2026 12:58:21 GMT</pubDate>
            <atom:updated>2026-08-29T13:02:37.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWnqJqfG3w-haLZ6BiELew.jpeg" /><figcaption>Working through an early design for Información Como Ayuda in San Juan, Puerto Rico, in early November 2017. Looking back, I can see many of the same questions I am still working on now: how information enters a network, how it moves through it, and how it reaches the people best positioned to respond.</figcaption></figure><p>Lately, I’ve been thinking about federation as a practical question: what does it take for different parts of a civic information system to remain independent and still function as a network?</p><p>That has made me look differently at two chapters of my own work that, for years, I thought of as related but distinct.</p><p>One began in 2011 at the Jersey Shore, where an independent, community-powered information network became closely connected to public media.</p><p>The other was in Puerto Rico in 2017 after Hurricane Maria, where we rapidly built <em>Información Como Ayuda</em> (Information as Aid), a Spanish-language humanitarian information system around what people were seeing, asking and needing amid an ongoing emergency.</p><p>They developed very differently.</p><p><a href="https://www.niemanlab.org/2013/10/journalists-of-the-jersey-shore-how-a-novice-reporter-built-a-news-network-from-scratch/">Jersey Shore Hurricane News</a> grew organically out of ideas I had been thinking and writing about for years. More than two years before I founded it, I was already <a href="https://thenewwaveplanner.tumblr.com/post/360538260/meshing-hyperlocal-news-and-community-planning">blogging</a> about more participatory, community-led ways of producing and sharing local information.</p><p><a href="https://reliefweb.int/report/puerto-rico-united-states-america/recovery-post-maria-puerto-rico">Information as Aid</a> was intentionally designed under crisis conditions, informed by an information needs assessment and by some of what I had already learned from operating JSHN.</p><p>Thinking about federation has made me see the same basic pattern in both. No single institution needed to control the whole information system. Different organizations and people could remain independent while information moved between them.</p><p>I use “federated” here in that fairly simple sense: the participants remain independent, but the connections between them allow information to move without one organization owning the whole system.</p><h3>JSHN and public media</h3><p>Jersey Shore Hurricane News began in 2011 as a community-powered information network. People did not simply receive information from it. They contributed to it.</p><p>Contributors reported flooding, outages and road conditions. They sent photographs and observations. And they asked questions and pointed toward things that needed attention.</p><p>Months after Superstorm Sandy, WHYY reached out to me directly in the spring of 2013 as it was experimenting with different community-reporting models and looking for new ways to cover the Jersey Shore.</p><p>By the time it brought me on under contract during the summer of 2013 to produce <em>Down the Shore</em>, its daily coverage of Jersey Shore news and life, JSHN had already become a large and trusted regional network.</p><p>JSHN did not become part of WHYY, and WHYY did not own JSHN. I continued operating it while working from home as a freelance reporter for WHYY.</p><p>That <a href="https://www.linkedin.com/feed/update/urn:li:activity:7342177125740756992/">made me the bridge</a>.</p><p>What surfaced through JSHN <a href="https://medium.com/@justinauciello/the-bay-was-sending-a-signal-jshn-was-built-to-hear-it-6b77acd87df3">could inform what I reported</a> for <em>Down the Shore</em>. A question coming repeatedly from the community could become a reporting question. Something residents were seeing could lead me into deeper reporting on recovery, infrastructure, environmental risk or public policy.</p><p>Working with WHYY gave me editors, access to officials and experts, and more capacity to dig into complicated issues. For the most part, there was no separate handoff to another reporter. I was working on both sides of the bridge.</p><p>Over seven years, I also periodically appeared on WHYY’s nightly news program to discuss the news of the day, sometimes drawing directly on reporting and information that had surfaced through JSHN. Some of what surfaced through the community network could become deeper reporting and then reach a broader audience through broadcast.</p><p>Because I was an independent freelancer, that bridge was not exclusive to WHYY. I also reported for WNYC and appeared on air when it needed Jersey Shore coverage. WHYY was by far the deepest and most sustained newsroom relationship, but JSHN remained independent, and I could bring what was surfacing there into more than one newsroom.</p><p>And the flow could come back the other way.</p><p>People responded to the reporting through JSHN. They added information, raised follow-up questions and described how policies or infrastructure problems were actually playing out where they lived. Sometimes reporting answered a question. Sometimes it produced a better one.</p><p>Publication did not have to end the process. Community experience could inform my reporting, the reporting could return through the community network, and the response could help shape what I reported next.</p><p>JSHN remained independent, as did the newsrooms. I was the direct link between them.</p><h3>Building Information as Aid</h3><p>I had been living primarily in Puerto Rico for about a year and a half when Hurricane Maria struck in September 2017. During that time, I was still operating Jersey Shore Hurricane News and reporting for WHYY from Puerto Rico.</p><p>For roughly the first 10 days, I had no connectivity and very little reliable information about what was happening beyond what I could see and hear around me. Our house in San Juan had four feet of water inside, and we were staying with family on the opposite side of the island.</p><p>The difficulty was not simply getting news out. People needed basic orientation: what was happening, where help was available, what was true and what conditions were like elsewhere on the island.</p><p>A few weeks after the storm, Internews hired me to work on an <a href="https://listeningpostcollective.org/wp-content/uploads/2025/10/Puerto-Rico.pdf">information needs assessment</a>. With help from remote Internews colleagues, I began looking more systematically at what people needed to know, what information was missing and how information was still moving despite widespread communications failures.</p><p>We also paid close attention to what was already working.</p><p>One of the places that surfaced was WALO Radio in Humacao, in eastern Puerto Rico, not far from where Maria made landfall. My Internews colleague Jesse Hardman had heard that WALO was worth looking at because it had been broadcasting urgent information and functioning as a community hub after the storm.</p><p>I reached out to understand what the station was doing and what it was hearing from its audience. That helped inform the assessment and began a relationship that would become important later.</p><p>In November, through a partnership between Internews and NetHope, I led the design and launch of Information as Aid, a humanitarian information system built around the needs we had identified.</p><p>Some of what I had learned at the Shore carried directly into the design. People needed to be participants in the information system, not simply its audience. <a href="https://medium.com/@justinauciello/in-a-crisis-communities-are-not-the-audience-they-are-the-signal-13c185777760">In a crisis, what communities are seeing, asking and experiencing is itself an important signal</a> about where information is missing and what may need attention. Information also needed to keep moving in both directions after something was published.</p><p>Puerto Rico required a different structure.</p><p>We selected citizen reporters partly based on where they already lived, so the team would reach different parts of the island, including communities that were difficult to reach and barely connected to the outside. We brought the group together for a full-day training before reporting began.</p><p>Some lived in places with little or no internet because cell towers were still down, lacked electricity or could not reliably get diesel to keep generators running.</p><p>That made their presence more important, not less.</p><p>When communications fail, information does not only have trouble getting into a community. Information also has trouble getting out. Conditions, questions and urgent needs can remain in place because few people outside know they exist.</p><p>A reporter already living there could surface information that otherwise might never travel.</p><p>NetHope had established WiFi hubs in downtown plazas in a number of municipalities. Reporters could gather information in poorly connected communities and use those hubs to communicate with the broader team.</p><p>Reporting was only part of their role. Their presence allowed them to hear what communities were asking and surface conditions that might otherwise remain invisible.</p><p>I served as the central editor. Often the editorial process started before there was a finished story. A reporter might bring forward something people were saying or experiencing, and we would work through the actual question, what remained uncertain and what needed more reporting.</p><p>They would go back out, report further and return with a story. I would review it again before publication.</p><p>Those stories were published through our centralized Information as Aid Facebook page. They were not limited to the mechanics of hurricane recovery. The reporters also covered people, communities and everyday life on an island that was continuing to live while it recovered.</p><p>The Facebook page quickly became a two-way recovery information hub, eventually reaching about 60,000 followers, although I thought of them more as contributors. People received information there, but they also asked questions, supplied information and told us what they needed to know.</p><p>We actively sought those information needs and shared them with local and international NGOs working across Puerto Rico. What communities were telling us could shape our reporting, but it could also help humanitarian organizations understand where information gaps and needs were emerging.</p><p>We also created a separate WhatsApp network for local, island-wide and international responders. It was a working information-sharing network where organizations and individuals exchanged information, compared what they were seeing and helped connect needs with resources or answers. We reinforced those relationships through regular in-person meetings.</p><p>Especially in late 2017 and early 2018, not everything called for a story.</p><p>Reporters sometimes encountered urgent needs that required action more than publication. They could bring those needs directly to municipal officials and town halls. We documented multiple instances where needs brought forward by correspondents resulted in a response.</p><p>Other times, something published on the Facebook page prompted people in the broader community to step forward with help, information or resources.</p><p>The operative question was not always, “How do we turn this into journalism?”</p><p>It was: <strong>What does this situation require, and who in the network is best positioned to respond?</strong></p><p>When information comes into a newsroom, the natural response is often journalism. A broader civic information network can leave other paths open from the start. The information might need a reporter, a municipality, an NGO or someone in the community.</p><p>Information as Aid itself had a central editorial core. The broader system around it was federated. WALO, CPI, humanitarian organizations, municipalities, responders and community actors retained their own roles while information could move between them.</p><p>As the recovery progressed through 2018 and 2019, the system evolved. We added printed newsletters distributed through resilience hubs and community centers, extending the work beyond digital channels.</p><p>The reporting also followed a deliberately connected set of recovery issues: housing, health, infrastructure, economic development and the fabric of communities.</p><p>My background as an urban planner influenced that structure. Planning had trained me to look at those systems together rather than as separate beats. A housing problem could reveal an infrastructure problem. A health issue might expose problems with transportation or access. Economic recovery could look very different from one municipality to another.</p><p>Our citizen reporters <a href="https://medium.com/@INTERNEWSPR">documented</a> how those issues were playing out at ground level.</p><p>The relationship with WALO grew during this period. Our reporters began appearing in recurring radio features, bringing their reporting to a broader regional audience. Through Internews, we also provided WALO with subgrants to pursue additional reporting of its own on the same recovery topics.</p><p>WALO remained its own newsroom. It could take an issue surfaced through the network and report further.</p><p>We later added another level through Centro de Periodismo Investigativo. CPI received an Internews subgrant, and the data-journalism workshop and fellowship work were deliberately focused on the same broad recovery areas our citizen reporters and WALO were already covering.</p><p>A citizen reporter might document how a housing or health problem was affecting one community. WALO could pursue the issue through regional reporting. CPI could investigate the larger structures behind it.</p><p>Internews funded my role and made subgrants to WALO and CPI, while NetHope paid the citizen reporters. The organizations remained independent even as the work became increasingly connected.</p><p>We had first encountered WALO while trying to understand the information environment after Maria, not while looking for a station to carry our content. It was already serving its community. We learned from that work first and connected our systems later.</p><p>You do not always build a network from scratch. You identify what already works, build what is missing and strengthen the connections between them.</p><p>Information as Aid continued through several rounds of funding before ending in the summer of 2020. The responder WhatsApp network outlasted the formal project and remains active today, with members still sharing information.</p><p>The relationships lasted longer than the project itself.</p><h3>Two different architectures</h3><p>At the Shore, the architecture developed organically. JSHN was already a functioning community information network, and I became a human bridge between it and institutional journalism.</p><p>In Puerto Rico, I could build some of those lessons into the system deliberately. Citizen reporters already living around the island surfaced information locally. The editing helped test and develop what they were hearing before publication. Different kinds of information could then move toward journalism, government, humanitarian organizations or the community itself.</p><p>As recovery progressed, the reporting could deepen through WALO and CPI, while the WhatsApp network linked local organizations and responders across Puerto Rico. We also drew on useful institutions that already existed rather than trying to recreate them.</p><p>The work was partly about building what was missing and partly about connecting what was already there.</p><p>That is what now feels federated to me: the parts could remain independent, while the connections between them made the larger system work.</p><p>A newsroom does not have to sit at the center of the civic information system.</p><p>Journalism can be one part of a larger network, connected to a trusted, community-powered information system that continuously surfaces what people are experiencing, asking and trying to understand.</p><p>Sometimes what surfaces needs journalism. Sometimes it needs an official response. Sometimes another organization or another resident is better positioned to act.</p><p>The community network does not have to become part of the newsroom, and the newsroom does not have to own the network. They can remain independent and still be closely connected.</p><p>Sometimes the bridge can be the same person working across those systems. In other cases, it can be an editor, a correspondent, a responder network or a relationship between organizations that develops over time.</p><p>Journalism becomes especially valuable when its particular strengths are connected to places where public needs are already surfacing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b0b12878e1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keeping a Two-Way Information System Responsive]]></title>
            <link>https://medium.com/@justinauciello/keeping-a-two-way-information-system-responsive-dd742e552425?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd742e552425</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 16:04:47 GMT</pubDate>
            <atom:updated>2026-08-19T16:07:45.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G41p_HrLJ5LN3WbU-JKueg.png" /></figure><p>One thing COVID made especially clear to me is how much of the work in a two-way information system can remain invisible if you look only at what gets published.</p><p>Jersey Shore Hurricane News had been working this way since 2011. During calm and crisis, people sent information and questions into the network. I would look across what was coming in, verify what I could, figure out what was useful to the broader community, and bring information back.</p><p>By the time COVID arrived, people already knew JSHN as a place to turn when they were trying to understand what was happening. COVID was different because the information need did not peak and recede. It kept changing.</p><p>Early on, I got into a daily practice of asking:</p><p>“What questions do you have?”</p><p>“What do you want to know today?”</p><p>Those prompts would regularly generate well over a hundred responses.</p><p>I started looking at them less as individual questions and more as a picture of what the community was trying to understand. In effect, it became a rolling information needs assessment.</p><p>Sometimes the useful signal was seeing the same confusion come up repeatedly. That told me there was an information gap worth trying to close.</p><p>Much of the work happened inside those threads. As questions accumulated, I was checking information, reaching out to sources and figuring out what could be answered there and what was useful enough to bring back to the broader community.</p><p>That became harder to sustain as the pandemic went on.</p><p>I did not see another local steward performing quite the same function across the Shore. Government agencies and news organizations were producing information, of course, but JSHN occupied a different place in the local information system. People brought questions and observations into the network, and I was paying attention to what they were collectively saying.</p><p>Information needs that might otherwise have been scattered across the community were showing up together in one place. That made them easier to understand collectively, but it also concentrated much of the work of responding to them in one place.</p><p>There is a funding implication here beyond capacity. Two-way information systems also need support for providing practical information people can use, not just for producing stories. Sometimes the most useful response is simply information that helps someone understand what is happening and what to do next.</p><p>That work still requires capacity. One useful answer can come out of a much larger body of questions and signals that had to be sorted through and understood. Funding these systems means accounting for that work as well as what ultimately gets published.</p><p>The better the loop works, the more capacity it may take to keep it working.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd742e552425" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Same Operating System]]></title>
            <link>https://medium.com/@justinauciello/the-same-operating-system-c692bbbe2f5a?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c692bbbe2f5a</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Sat, 15 Aug 2026 14:15:32 GMT</pubDate>
            <atom:updated>2026-08-15T14:15:32.774Z</atom:updated>
            <content:encoded><![CDATA[<p>I have worked across very different fields, but much of the work comes down to the same thing: making sense of a complicated question well enough to give someone a useful answer.</p><p>A recent planning assignment brought that into focus for me.</p><p>A client wanted to know whether a property was worth pursuing as an affordable housing opportunity. He wanted a yes or no because he was deciding whether to keep putting time and money into it.</p><p>But I could not get to that answer responsibly without going much deeper.</p><p>The question pulled in planning history, zoning, sewer capacity, affordable housing obligations, litigation, prior approvals, project economics, and recent zoning changes that had removed density incentives previously available in the area.</p><p>The analysis showed real potential. It also showed several things that still had to be resolved before I would be comfortable telling him to move forward.</p><p>So that became the answer. There was enough here to keep looking, but not enough yet to make the call.</p><p>I laid out what we know, what is still uncertain, what could actually change the outcome, and what we need to resolve next.</p><p>I have worked this way my entire career.</p><p>I might be untangling an issue for a litigation report, reporting an environmental story for public media, looking at information access problems in a Middle Eastern country, or trying to understand what people need to know in a community after a disaster.</p><p>Those are very different assignments, but I am doing the same thing in each one.</p><p>I am trying to understand how the system actually works and follow the information far enough to see what is solid, what is not, and what I can reasonably conclude from it.</p><p>The useful answer is not always the cleanest one. Sometimes the work shows that there is enough to keep going, but also makes clear what still has to be figured out before making the decision.</p><p>That was the answer here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c692bbbe2f5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bay Was Sending a Signal. JSHN Was Built to Hear It.]]></title>
            <link>https://medium.com/@justinauciello/the-bay-was-sending-a-signal-jshn-was-built-to-hear-it-6b77acd87df3?source=rss-5616f5d56e0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b77acd87df3</guid>
            <dc:creator><![CDATA[Justin Auciello]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 15:09:05 GMT</pubDate>
            <atom:updated>2026-08-28T12:55:23.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKg3g1SKOT6EnkBsPNe9ZQ.png" /><figcaption>A silt plume in the Barnegat Bay off Seaside Park on Aug. 5, 2015. (Image courtesy of Save Barnegat Bay)</figcaption></figure><p><em>How a Barnegat Bay plume tested the civic information system I had built through Jersey Shore Hurricane News</em></p><p>On August 5, 2015, an aerial photograph captured a large brown plume spreading into the Barnegat Bay from a newly constructed pump station in Seaside Park, New Jersey.</p><p>The image was alarming, but it did not explain itself. It did not show what the material was, why the station was operating during dry weather, whether the water was safe or what the discharge might reveal about the new Route 35 drainage system.</p><p>It was the beginning of a public question.</p><p>What followed is an early example of the operating model I now describe through the <a href="https://medium.com/@justinauciello/toward-a-civic-signal-system-methodology-a9b57fba5188">Civic Signal Framework</a>.</p><p>Important information often enters public view in fragments, well before an agency issues a finding or a newsroom has a complete story. Someone notices something. Another person documents it. Questions begin to circulate. Journalists, officials, technical experts and community members each hold part of the picture.</p><p>The work is to connect those pieces without getting ahead of the evidence.</p><p>By then, I had already built Jersey Shore Hurricane News to do that work.</p><p>The plume did not first enter public view through a government announcement or inspection report. Members of the community saw it, documented it and brought it into the JSHN network. JSHN gave that observation somewhere to go. It provided a public space where the image could circulate, residents could ask questions and local knowledge could begin shaping the reporting.</p><p>The community supplied the signal.</p><p>JSHN provided the architecture for receiving it, testing it and returning verified information to the public.</p><p>At the time, I was also reporting for WHYY’s NewsWorks. That relationship became central to how the story developed.</p><p>JSHN and WHYY were not simply publishing the same information in two places. They served different but connected roles in the same flow of information.</p><p>JSHN surfaced the signal, gathered public attention and helped identify the questions that needed answers. My WHYY reporting brought formal reporting capacity into the process. I contacted the New Jersey Department of Transportation, the Department of Environmental Protection, Ocean County health officials and Save Barnegat Bay, then worked to place their explanations and concerns within the larger context of the Route 35 reconstruction project.</p><p>On August 8, I published <a href="https://whyy.org/articles/dot-silt-plume-in-barnegat-bay-off-seaside-park-unusual-but-waters-safe/">the first WHYY report</a> identifying the source of the plume as the new 8th Avenue pump station. It was one of nine stations installed between Bay Head and South Seaside Park as part of the post-Sandy reconstruction of Route 35.</p><p>NJDOT spokesman Steve Schapiro called the plume unusual but said it was not hazardous. The department attributed it to silt that had accumulated inside the drainage system during construction, along with sediment disturbed from the bay bottom by the force of the discharge. NJDOT also said Ocean County had tested the water and found it safe.</p><p>The state said the pump had been taken offline and would be activated when necessary to prevent flooding. It also acknowledged that crews were still inspecting and cleaning manholes and pipe joints and applying hydraulic cement to address leaks. Once that work was complete, NJDOT said, the pumps should operate less frequently.</p><p>Save Barnegat Bay raised a different set of questions. Why was groundwater apparently entering a system intended to collect stormwater runoff? Why was the station operating during dry conditions? What could infiltrating groundwater carry into the bay? Were the containment and treatment measures working as intended? Could a single sample answer the broader ecological concerns?</p><p>The reporting did not force those competing claims into a simple verdict.</p><p>The available testing did not show an immediate bacterial hazard. At the same time, the plume was real, the discharge was unusual, construction sediment had entered the system and questions about groundwater infiltration and future releases remained unresolved.</p><p>Verification did not mean automatically accepting the most reassuring explanation. It also did not mean treating a visible plume as proof of contamination or wrongdoing.</p><p>It meant establishing what was known, identifying what remained uncertain and preserving a record against which later evidence could be measured.</p><h3>The JSHN and WHYY/NewsWorks relationship</h3><p>Information moved in both directions.</p><p>Community observations and discussion through JSHN helped shape the questions that required formal answers. My resulting WHYY reporting then returned through JSHN, where residents could evaluate the findings, add observations, challenge explanations and identify what needed further attention.</p><p>WHYY created a durable reported record. JSHN kept that reporting connected to the people who were watching what was happening locally.</p><p>That relationship mattered to how the case unfolded. JSHN was not merely a distribution channel for finished journalism. It was a civic information system I had built to receive early signals, organize public attention, conduct verification and return useful information to the community.</p><p>From the beginning, the public was not treated only as an audience. In this case, residents, photographers, boaters and environmental advocates supplied observations, evidence, questions and local knowledge. But those contributions did not organize themselves. JSHN gave those fragmented contributions somewhere to come together within disciplined reporting and verification.</p><p>Publication did not end the work. It returned information to the same network that had helped generate the original questions, creating a continuous feedback loop.</p><p>In Civic Signal Framework terms, the sequence was already visible: <strong>detect the signal, verify what could be established, connect it to the responsible institutions, synthesize the competing information, orient the public and return the findings to the community.</strong> That return created the <strong>feedback loop</strong>. Residents and advocates could assess the response, contribute new evidence, raise additional questions, and help determine what required further reporting. As new plumes appeared, the cycle began again with a stronger evidentiary record.</p><h3>A nearby beach closure</h3><p>Several days later, the situation became more complicated.</p><p>On August 11, rainfall and runoff led officials to post an advisory at the 5th Avenue bay beach in Seaside Park. The following day, swimming was prohibited after samples showed enterococcus bacteria levels of 180, 220 and 220 colonies per 100 milliliters, above the standard of 104.</p><p>By August 13, swimming <a href="https://whyy.org/articles/no-swimming-at-seaside-park-bay-beach-for-second-consecutive-day-due-to-bacteria/">had been prohibited</a> for a second consecutive day.</p><p>The beach was only a few blocks from the 8th Avenue pump station. Given the timing and location, residents and environmental advocates naturally asked whether the bacteria exceedance was connected to the plume.</p><p>It was a reasonable question. It was not an established fact.</p><p>JSHN reported the closure, contacted the responsible agencies and made clear that the relationship was unknown. When a commenter offered a possible explanation, I responded: “That’s possible, but I can’t speculate.”</p><p>That exchange shows how I handled uncertainty.</p><p>A civic information system must make room for legitimate concern without allowing a possibility to become a conclusion. Observation, suspicion, plausibility and verification are not interchangeable. The public should be able to see the difference.</p><p>Ocean County attributed the elevated bacteria levels to rainfall and runoff and said the closure was unrelated to the pump station. Around noon on August 13, the beach reopened after new samples returned results of 40, 10 and less than 10 colonies per 100 milliliters, all within the applicable standard.</p><p>JSHN reported the closure and the reopening. The public was not left with an outdated impression that the beach remained closed. It was also not left with an unsupported belief that the plume had caused the bacteria exceedance.</p><p>The new information returned to the same community that had raised the question.</p><h3>The dry-weather signal</h3><p>The question of why the pumps were operating during dry periods was not incidental. It became part of the documented evidence.</p><p>On September 9, photographer Gregory Coraggio captured new aerial images showing sediment near several pump stations. Some of the material appeared both inside and outside barriers intended to contain suspended particles.</p><p>The pumps were running despite the area having gone approximately three weeks without significant rainfall. Save Barnegat Bay argued that this indicated groundwater was infiltrating the drainage pipes and carrying fine material through the system. State lawmakers were also asking why the pumps were repeatedly cycling and whether the water was coming from rainfall or infiltration through the sandy soil.</p><p>I <a href="https://whyy.org/articles/sediment-flow-into-water-presents-qserious-consequencesq-to-barnegat-bay-health-group-says/">published a follow-up WHYY report</a> on September 10.</p><p>Save Barnegat Bay said its one-day sampling had not identified pollutants above applicable standards. Salinity readings, however, suggested varying degrees of groundwater infiltration into a system the organization said was intended to be sealed.</p><p>The group argued that fine particles in the backfill surrounding the pipes were being carried into the system as groundwater entered through leaks. It also questioned whether the booms were adequately containing sediment before it reached open water.</p><p>NJDOT had already announced that crews were cleaning silt from drainage pipes and pump stations in Seaside Park, Seaside Heights, and South Seaside Park. The department said hydraulic cement was being applied to prevent water infiltration and seal the system.</p><p>By then, the issue had moved beyond explanation. Corrective work was underway.</p><p>The evidence did not support a dramatic declaration that the bay had been contaminated. It also did not eliminate the questions raised by repeated sediment releases, groundwater infiltration and the effectiveness of the containment measures.</p><p>The reporting had to account for both.</p><p>A discharge did not have to be toxic to matter environmentally. The drainage system could substantially improve flood protection while still experiencing engineering problems that deserved scrutiny. And an agency’s answer to an immediate public health question did not necessarily resolve the broader ecological or operational concerns.</p><p>Those distinctions are often lost in daily reporting. They require continuity and institutional memory. A new photograph becomes more meaningful when someone recognizes its connection to what happened weeks or months earlier.</p><p>JSHN supplied that continuity.</p><p>The archive did not begin again with each plume. New observations entered an existing record that already contained aerial images, agency statements, water testing results, environmental concerns, corrective work and unresolved questions.</p><p>Each new signal carried the weight of what had already been documented.</p><h3>By October, the disagreement had hardened</h3><p>The questions did not end with the September cleaning and sealing work.</p><p>On October 17, Coraggio again used a drone to document a plume at the 8th Avenue pump station. Save Barnegat Bay said the images showed sediment outside the containment barriers and argued that groundwater entering the drainage system could be carrying contaminants from two known NJDEP sites into the estuary.</p><p>The dry weather operation was now part of the public record. My <a href="https://whyy.org/articles/claim-of-pollution-in-barnegat-bay-silt-plume-is-false-state-spokesman-says/">October 21 article</a> noted that residents had been observing the pump stations operating through extended periods without rain since that summer.</p><p>Save Barnegat Bay was no longer describing the condition as an isolated construction problem. It called the situation an “environmental disaster” and demanded continuous mechanical monitoring, particularly because Ocean County did not test water at bay beaches during the off-season.</p><p>NJDOT rejected that characterization.</p><p>Department spokesman Kevin Israel said the allegations of pollution were false. He acknowledged that water infiltration and natural silt accumulation could continue while contractors finished sealing the system, but maintained that the sediment was clean, the barriers were functioning and the water remained safe.</p><p>The department also pointed to the drainage system’s performance during the early October nor’easter, saying it had prevented massive flooding.</p><p>That complicated the dispute further. The drainage network being questioned for recurring sediment discharges had also provided a significant flood control benefit.</p><p>The story could not be reduced to a choice between a successful public-works project and an environmental failure.</p><p>Both questions mattered. Was the drainage infrastructure reducing flooding? Was it also releasing sediment or allowing groundwater infiltration in ways that required further correction and monitoring?</p><p>The October article preserved those competing claims without declaring either side’s broader interpretation proven. Save Barnegat Bay had not established through the available testing that the plume contained harmful concentrations of pollutants. NJDOT, however, was still sealing the pipes and connections and acknowledging that infiltration and silt discharge could occur while that work continued.</p><p>By this stage, the same information flow was also producing accountability.</p><p>The community kept producing visual evidence. The environmental organization interpreted that evidence and raised technical concerns. The state defended the project and challenged the language being used against it. My reporting documented the disagreement, separated measured facts from disputed conclusions, and kept the public record open.</p><p>The system did not stop functioning because the institutions involved disagreed. That was when its discipline mattered most.</p><h3>The signal returned</h3><p>October was not the end of the story.</p><p>On March 18, 2016, Save Barnegat Bay discovered another plume, this time near the Kearny Avenue bay beach and public dock in Seaside Heights. The organization reported it to NJDEP and identified the area as important winter flounder habitat.</p><p>It was the fourth significant plume documented in the reporting in less than a year.</p><p>NJDOT said the discharge occurred while a contractor was cleaning accumulated silt from one of the storm-drainage systems. The pumps were shut down for additional cleaning, and DEP said inspectors would investigate. The state again maintained that the discharged material was clean.</p><p>The March incident matters because it shows that the civic signal loop remained active after the initial news cycle had passed.</p><p>The location had changed, but the network recognized the pattern. An environmental organization documented the condition and notified regulators. The earlier reporting provided context.</p><p>In a <a href="https://whyy.org/articles/another-silt-plume-appears-in-the-barnegat-bay/">March 20, 2016 report</a>, JSHN and WHYY identified it not as an isolated brown patch in the bay, but as the fourth significant event associated with the same drainage infrastructure.</p><p>The archive later recorded that workers continued sealing pipes and manhole connections during the spring of 2016 to address infiltration concerns.</p><p>There was no single dramatic resolution. Instead, the public record shows recurring observation, repeated institutional response, and continued corrective work.</p><p>That is often what environmental accountability actually looks like.</p><h3>A distributed environmental sensing system</h3><p>No newsroom could station a reporter beside every pump station and outfall from Bay Head to South Seaside Park. No environmental organization could watch every section of Barnegat Bay at all times. No government agency could guarantee that every unusual discharge would be detected internally before someone in the public noticed it.</p><p>A distributed community, however, could watch from many places at once.</p><p>Residents, photographers, boaters, advocates, local officials, journalists, and JSHN contributors each held part of the picture. On their own, those observations might have remained isolated or anecdotal. Once those observations entered JSHN, they could become part of a larger public record.</p><p>A resident could report discolored water. A photographer could provide aerial imagery. An environmental organization could identify the outfall and explain its concerns. I could contact the responsible agencies and test competing claims. County officials could provide laboratory results. NJDOT could explain how the infrastructure was designed to operate.</p><p>The findings could then return through JSHN, where the public could compare those explanations with what appeared during the next discharge.</p><p>This was more than crowdsourcing. Crowdsourcing describes the collection of contributions. JSHN provided an operating method for determining what those contributions meant, what required verification, which institutions needed to answer and what information should be returned to the public.</p><p>Journalists have always received tips, interviewed officials, checked claims, and published updates. JSHN did not invent those practices.</p><p>It created a public space where an observation could surface before anyone fully understood its significance. Uncertainty could enter in the form of questions.</p><p>What is that plume? Why is the pump operating? Is the water safe? Are the containment measures working? Has this happened elsewhere? What is the state doing about it?</p><p>Those questions created the path toward verification.</p><p>Environmental problems often begin this way. Someone notices discoloration, an odor, unusual runoff, sediment, dead fish, or another condition that does not look right. The person may not know what caused it or whether it represents a serious threat. They simply know that something has changed.</p><p>The first signal may be incomplete. It may ultimately prove harmless. But ignoring those observations until an institution formally validates them leaves a significant gap in public awareness.</p><p>The answer is not to publish every claim as fact. It is to create a disciplined way of receiving uncertain information, testing it, connecting it with institutional knowledge and reporting the results back to the public.</p><h3>Why the plume remains significant</h3><p>The Barnegat Bay plume can be remembered as a dispute over brown water, storm drains, and a major highway project.</p><p>What matters more to me now is what the episode revealed about civic information.</p><p>JSHN had become another source of environmental awareness around a major public infrastructure project. It did not replace regulators, engineers, laboratories, environmental organizations, or professional journalism. It connected them.</p><p>Residents saw that their observations could matter. Environmental advocates brought technical concerns into a broader public discussion. My reporting identified patterns that extended beyond a single event. Government agencies had to explain what the public was seeing. Those explanations remained available for comparison when new evidence appeared.</p><p>An effective civic information system cannot operate only from the top down. It must also receive information from residents, move it across institutional boundaries, return verified answers to the people who raised the questions, and keep the feedback loop going.</p><p>JSHN did not emerge automatically from community participation. Community members supplied the observations, photographs, concerns, and local knowledge that made it valuable. I built and maintained the structure that gave those signals somewhere to go.</p><p>The Barnegat Bay plume did not end with a single finding. People continued watching. New evidence continued entering the record. Officials continued responding. Corrective work continued.</p><p>Years before I had language for the <a href="https://medium.com/@justinauciello/toward-a-civic-signal-system-methodology-a9b57fba5188">Civic Signal Framework</a>, I had already built its operating architecture through JSHN.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b77acd87df3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>