<?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:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/journalism">
  <channel>
    <title>Journalism</title>
    <link>https://www.linuxjournal.com/tag/journalism</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>When the Problem Is the Story</title>
  <link>https://www.linuxjournal.com/content/when-problem-story</link>
  <description>  &lt;div data-history-node-id="1340217" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/linuxstory.jpg" width="640" height="480" alt="""" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;Linux isn't a story anymore.&lt;/p&gt;&#13;
&#13;
&lt;p&gt;That's a good thing, but not an interesting one. Let me explain.&lt;/p&gt;&#13;
&#13;
&lt;p&gt;Journalism's main product is the story. In newsrooms, the three words uttered most often by editors to reporters are "What's the story?"&lt;/p&gt;&#13;
&#13;
&lt;p&gt;As I was taught by an editor long ago—and as I have found to be true constantly ever since—all stories are about three things:&lt;/p&gt;&#13;
&#13;
&lt;ol&gt;&lt;li&gt;&lt;strong&gt;A character&lt;/strong&gt;. Usually human, but not always. Could be a cause. A sports team. A political party. Could be good, or bad, or neither. All that matters is that the character is interesting. You can also have more than one, but a single one is better.&lt;/li&gt;&#13;
	&lt;li&gt;&lt;strong&gt;A problem or conflict&lt;/strong&gt;. A situation that challenges the character, or characters, further defining them and making them more interesting. Problems and conflict keep people interested, so they keep reading, watching, listening, turning pages, talking to others about it, and "move the narrative along" (as the news watchers like to say).&lt;/li&gt;&#13;
	&lt;li&gt;&lt;strong&gt;Movement toward resolution&lt;/strong&gt;. Doesn't matter if the end never arrives. Hell, look at soap operas. You just have to keep the story moving in the direction of conclusion. Newsroom aphorism: "No story ever starts with 'Happily ever after'." Another: "If your team is up forty points with five minutes left, your new story is about how you get out of the parking lot ahead of traffic."&lt;/li&gt;&#13;
&lt;/ol&gt;&lt;p&gt;All three of those are why Linux isn't much of a story any more, even though it's bigger in the world than it has ever been.&lt;/p&gt;&#13;
&#13;
&lt;p&gt;Linux had character when it was easy to cast as an underdog operating system, and the problem was beating Windows. Linus Torvalds, the father of Linux, did his best &lt;em&gt;not&lt;/em&gt; to be interesting, but his fans made him interesting anyway:&lt;/p&gt;&#13;
&#13;
&lt;p&gt;&lt;img alt="""" class="image-max_650x650" data-entity-type="file" data-entity-uuid="insert-max_650x650-88e62dcd-3f07-4781-977e-3a875d69c5a9" height="364" src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/geeksgetcute.png" width="650" /&gt;&lt;/p&gt;&#13;
&#13;
&lt;p&gt;Us included. The above is from a &lt;a href="http://searls.com/penguins/index.htm"&gt;slide show&lt;/a&gt; that was featured in &lt;a href="https://www.linuxjournal.com/article/5696"&gt;a story I wrote back in 2002&lt;/a&gt; that's off-web at the moment, but also beside the point, which is that Linus and his penguins were characters in stories that were interesting at the time and aren't anymore.&lt;/p&gt;&#13;
&#13;
&lt;p&gt;That's because Linux has achieved the world domination it longed for in the early years.&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/when-problem-story" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 19 Oct 2018 17:02:18 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1340217 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Will Anything Make Linux Obsolete?</title>
  <link>https://www.linuxjournal.com/content/will-anything-make-linux-obsolete</link>
  <description>  &lt;div data-history-node-id="1339379" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/12180f1.png" width="375" height="372" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
Remember blogging? Hell, remember magazine publishing? Shouldn't be hard.
You're reading some now.
&lt;/p&gt;

&lt;p&gt;
Both are still around, but they're obsolete—at least relatively. Two cases
in point: &lt;a href="http://blogs.harvard.edu/doc"&gt;my blog&lt;/a&gt;
and &lt;em&gt;Linux
Journal&lt;/em&gt;.
&lt;/p&gt;

&lt;p&gt;
Back when blogging was a thing, in the early 2000s, about 20,000
people subscribed to RSS feeds of my original blog (1999–2007, still
mothballed &lt;a href="http://doc.weblogs.com"&gt;here&lt;/a&gt;). At its peak, I posted many times per day and had a strong
sense of connection with my readership.
&lt;/p&gt;

&lt;p&gt;
Same went, by the way, for my postings in &lt;em&gt;Linux
Journal&lt;/em&gt;, on our website
and on one of our own blogs, called IT Garage—lots of readers, lots of
engagement.
&lt;/p&gt;

&lt;p&gt;
Most early bloggers were journalists by profession or avocation—good
writers, basically. Some blogs turned into online pubs. BoingBoing,
TechCrunch and TPM all started as blogs.
&lt;/p&gt;

&lt;p&gt;
But blogging began to wane after Twitter and Facebook showed up in 2006.
After that journalism also waned, as "content generation" became the way to
fill online publications. Participating in "social media" also became a
requisite function for journalists still hoping to stay active online (if
not also employed).
&lt;/p&gt;

&lt;p&gt;
These days, I blog only a few times per month, for readers that range in number
from dozens to hundreds. Usually I duplicate those posts in
&lt;em&gt;Medium&lt;/em&gt;, where
they get about the same numbers. Meanwhile, I have 23.7k followers on
Twitter (as @dsearls). Although that's a goodly number, you could say the same
for the average parking space. (Which, if it could speak, might say "Hey, I
had 25k impressions on passing drivers today and engaged 15.") From
what I can tell from counting clicks of shortlinks I produce with Bit.ly,
most of my tweets are clicked on by a few dozen people, tops. I'd gladly
trade all my followers (and my Klout score of 81) for the actual readers I
had in my old blog. But alas, this is now.
&lt;/p&gt;

&lt;p&gt;
Thanks to loyal subscribers, &lt;em&gt;Linux Journal&lt;/em&gt; is still trucking along, proving it is possible to operate a journal that isn't just another sluice for
"content".
&lt;/p&gt;

&lt;p&gt;
But we have to face the facts here: content production has clearly
obsolesced journalism—just like TV obsolesced radio, cars obsolesced
horses and printing obsolesced scribes. All of the obsolesced things do
persist, but in a diminished state relative to what obsolesced
them.
&lt;/p&gt;

&lt;p&gt;
To understand why and how, it helps to raid the works of Marshall McLuhan,
the media scholar best known for saying "the media is the
message" (or "the
massage"—he said both) and coining the term "global
village" decades
before the internet materialized one.
&lt;/p&gt;

&lt;p&gt;
The analytic system McLuhan and his colleagues created for understanding
how one medium obsolesces another is the &lt;em&gt;tetrad&lt;/em&gt; (Greek
for &lt;em&gt;group of four&lt;/em&gt;).
Every medium, he said, does four things. These are discovered in answers to
four questions:
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/will-anything-make-linux-obsolete" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 09 May 2017 11:27:19 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339379 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The Problem with "Content"</title>
  <link>https://www.linuxjournal.com/content/problem-content</link>
  <description>  &lt;div data-history-node-id="1339304" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/typewriter-669353_640.jpg" width="640" height="426" alt="old typewriter" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
Back in the early '00s, &lt;a href="https://en.wikipedia.org/wiki/John_Perry_Barlow"&gt;John Perry Barlow&lt;/a&gt;
said "I didn't start hearing about
'content' until the container business felt threatened." &lt;em&gt;Linux
Journal&lt;/em&gt; was
one of those containers—so was every other magazine, newspaper and
broadcast station. Today, those containers are bobbing around in an ocean of
"content" on the internet. Worse, the stuff inside the containers, which we
used to call "editorial", is now a breed of
"content" too.
&lt;/p&gt;

&lt;p&gt;
In the old days, editorial lived on one side of a "Chinese
wall" between
itself and the publishing side of a newspaper or magazine. The same went for the
programming and advertising sides of a commercial broadcast station or
network. The wall was transparent, meaning it was possible for a writer, a
photographer, a newscaster or a performing artist to see what funded the
operation, but the ethical thing was to ignore what happened on the other
side of that wall. Which was easy to do, because everything on the other
side of that wall was somebody else's job.
&lt;/p&gt;

&lt;p&gt;
Today that wall has been destroyed by the imperatives of "content
production", which is the new job of journalists and everybody else devoted
to "generating content" in maximum volumes, all the better to attract
"programmatic" advertising.
&lt;/p&gt;

&lt;p&gt;
You can see the wreckage of one such wall in a January 2017 &lt;em&gt;The New
York Times&lt;/em&gt; story titled &lt;a href="https://www.nytimes.com/2017/01/03/nyregion/in-new-jersey-only-a-few-media-watchdogs-are-left.html?_r=2"&gt;"In New Jersey, Only a Few Media
Watchdogs Are Left"&lt;/a&gt;,
by David
Chen. In it he writes, "The &lt;em&gt;Star-Ledger&lt;/em&gt;, which almost halved its newsroom
eight years ago, has mutated into a digital media company requiring most
reporters to reach an ever-increasing quota of page views as part of their
compensation."
&lt;/p&gt;

&lt;p&gt;
As I explained in my January 2016 article &lt;a href="http://www.linuxjournal.com/content/what-we-can-do-ad-blockings-leverage"&gt;"What We Can Do with Ad Blocking's
Leverage"&lt;/a&gt;,
the advertising we're talking about here isn't the old Madison
Avenue kind that lived on the other side of journalism's Chinese wall. It's
a new all-digital kind called &lt;em&gt;adtech&lt;/em&gt;. While adtech is
&lt;em&gt;called&lt;/em&gt; advertising,
and &lt;em&gt;looks&lt;/em&gt; like advertising, it is actually a breed of
&lt;a href="https://en.wikipedia.org/wiki/Direct_marketing"&gt;direct
marketing&lt;/a&gt;, a
cousin of spam descended from junk mail.
&lt;/p&gt;

&lt;p&gt;
Like junk mail, adtech is data-driven, wants to get personal, finds success
in tiny-percentage responses and excuses massive negative
externalities.
Those include wanton and unwelcome surveillance, annoying the crap out of
people and filling the world with crap—including fake news and
fraudulent advertising.
&lt;/p&gt;

&lt;p&gt;
Here's one way to tell the difference between real advertising and adtech,
using the &lt;em&gt;Star-Ledger&lt;/em&gt; as an example:
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/problem-content" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 07 Mar 2017 15:23:11 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339304 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Debugging Democracy</title>
  <link>https://www.linuxjournal.com/content/debugging-democracy</link>
  <description>  &lt;div data-history-node-id="1339252" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/12126f3.png" width="625" height="500" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
&lt;em&gt;You had to be a crank to insist on being right. Being right was largely a
matter of explanations. Intellectual man had become an explaining creature.
Fathers to children, wives to husbands, lecturers to listeners, experts to
laymen, colleagues to colleagues, doctors to patients, man to his own soul,
explained. The roots of this, the causes of the other, the source of
events, the history, the structure, the reasons why. For the most part, in
one ear out the other. The soul wanted what it wanted. It had its own
natural knowledge. It sat unhappily on superstructures of explanation, poor
bird, not knowing which way to fly.&lt;/em&gt;—Saul Bellow,
&lt;em&gt;Mr. Sammler's Planet&lt;/em&gt;, 1969.
&lt;/p&gt;

&lt;p&gt;
I began writing this column on November 9, 2016, on the balcony of a hotel
in Istanbul, while a call to prayer echoed through the streets below. I
took that as good advice, because a few hours earlier my country elected an
&lt;a href="http://scripting.com/2016/07/28/dontFeedDjTrump.html"&gt;Internet troll,
Donald Trump&lt;/a&gt;, as its president
Perhaps by now we're
calling this day 11/9, in the mold of 9/11. I'm an optimistic guy, but
color me pessimistic about where my country is now heading, led by a world-class narcissist.
&lt;/p&gt;

&lt;p&gt;
And forgive me for obsessing not only about where this is going, but how we
got here. Our country has been hacked, and that matters.
&lt;/p&gt;

&lt;p&gt;
Disclosure: I'm a political independent, and not a fan of Hillary Clinton,
though I thought she was the only sensible choice, given Trump's
shortcomings, many of which should have disqualified him, flat out. But he
won. Why?
&lt;/p&gt;

&lt;p&gt;
I don't know, though I did see it coming. Mostly I felt it. Polls said one
thing, my senses another. "We know more than we can tell", says Michael
Polanyi. Evidence: most of the time we don't know how we'll end the
sentences we start, or how we started the sentences we end. Yet we know
what we're talking about. And if we succeed, another human being gathers
our meaning, even though they can't repeat it verbatim.
&lt;/p&gt;

&lt;p&gt;
To say something is to express some care about it. We also tend to hear
what we like to hear more than what we don't, even if we welcome what might
disagree with us. Those of us who work with logic (such as &lt;em&gt;Linux
Journal&lt;/em&gt;
readers) have a high regard for the rational. But while logic and reason
sit on the mental board of directors, emotions cast the deciding
votes. As
Bellow says, the soul wants what it wants.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/debugging-democracy" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 05 Jan 2017 16:24:44 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339252 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
