<?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/irc">
  <channel>
    <title>IRC</title>
    <link>https://www.linuxjournal.com/tag/irc</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>What Really IRCs Me: Mastodon</title>
  <link>https://www.linuxjournal.com/content/what-really-ircs-me-mastodon</link>
  <description>  &lt;div data-history-node-id="1340655" 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/bigstock-People-chatting-through-the-in-15779303.jpg" width="1000" height="780" 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/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&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;Learn how to use the Mastodon social network platform from the comfort
of your regular IRC client.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
When it comes to sending text between people, I've found IRC (in
particular, a text-based IRC client) works best. I've been using it to chat
for decades while other chat protocols and clients come and go. When my
friends have picked other chat clients through the years, I've used the amazing
IRC gateway Bitlbee to connect with them on their chat client using the same
IRC interface I've always used. Bitlbee provides an IRC gateway to many
different chat protocols, so you can connect to Bitlbee using your IRC
client, and it will handle any translation necessary to connect you to the
remote chat clients it supports. I've written about Bitlbee a number of times
in the past, and I've used it to connect to other instant messengers, Twitter and
Slack. In this article, I describe how I use it to connect to yet another
service on the internet: Mastodon.
&lt;/p&gt;

&lt;p&gt;
Like Twitter, Mastodon is a social network platform, but unlike Twitter,
Mastodon runs on free software and is decentralized, much like IRC or email.
Being decentralized means it works similar to email, and you can create your
own instance or create an account on any number of existing Mastodon networks
and then follow people either on the same Mastodon network or any other
instance, as long as you know the person's user name (which behaves much like
an email address).
&lt;/p&gt;

&lt;p&gt;
I've found Bitlbee to be a great interface for keeping track of social media on
Twitter, because I treat reading Twitter like I was the operator for a
specific IRC room. The people I follow are like those I've invited and given
voice to, and I can read what they say chronologically in my IRC room. Since
I keep my IRC instance running at all times, I can reconnect to it and catch
up with the backlog whenever I want. Since I'm reading Twitter over a purely
text-based IRC client, this does mean that instead of animated gifs, I just
see URLs that point to the image, but honestly, I consider that a feature!
&lt;/p&gt;

&lt;p&gt;
Since Mastodon behaves in many ways like Twitter, using it with Bitlbee works
just as well. Like with Twitter over Bitlbee, it does mean you'll need to
learn some extra commands so that you can perform Mastodon-specific
functions,
like boosting a post (Mastodon's version of retweet) or replying to a post so
that your comment goes into the proper thread. I'll cover those commands in a
bit.
&lt;/p&gt;

&lt;h3&gt;
Installing the Mastodon Bitlbee Plugin&lt;/h3&gt;

&lt;p&gt;
The first step is to install the Mastodon Bitlbee Plugin. This plugin is
already packaged for Debian and other distributions—look for the
&lt;code&gt;bitlbee-mastodon&lt;/code&gt; package. In that case, you can just install it with your
package manager. Otherwise, you'll need to clone the source code from the
plugin's git repo and build it from source:

&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/what-really-ircs-me-mastodon" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 09 Jul 2019 12:00:00 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1340655 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>What Really IRCs Me: Slack</title>
  <link>https://www.linuxjournal.com/content/what-really-ircs-me-slack</link>
  <description>  &lt;div data-history-node-id="1339928" 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/bigstock-Speech-bubble-illustration-of--98311322.jpg" width="739" height="600" 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/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&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;Find out how to reconnect to Slack over IRC using a Bitlbee libpurple
plugin.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
I'm an IRC kind of guy. I appreciate the simplicity of pure text chat,
emoticons instead of emojis, and the vast array of IRC clients and servers to
choose from, including the option to host your own. All of my interactive
communication happens over IRC either through native IRC channels (like
#linuxjournal on Freenode) or using a local instance of Bitlbee to act as an
IRC gateway to other chat protocols. Because my IRC client supports
connecting to multiple networks at the same time, I've been able to manage
all of my personal chat, group chat and work chat from a single window that
I can connect to from any of my computers.
&lt;/p&gt;

&lt;p&gt;
Before I upgraded to IRC, my very first chat experience was in the late 1990s
on a web-based Java chat applet, and although I hold some nostalgia for web-based
chat because I met my wife on that network, chatting via a web browser just
seems like a slow and painful way to send text across the internet. Also,
shortly after we met, the maintainers of that network decided to shut down the
whole thing, and since it was a proprietary network with proprietary
servers and clients, when they shut it down, all those chat rooms and groups
were lost.
&lt;/p&gt;

&lt;p&gt;
What's old is new again. Instead of Java, we have JavaScript, and kids these
days like to treat their web browsers like Emacs, and so every application has
to run as a web app. This leads to the latest trend in chat: Slack. I say the
&lt;em&gt;latest&lt;/em&gt; trend, because it wasn't very long ago that Hipchat was hip, and before
that, even Yammer had a brief day in the sun. In the past, a software project
might set up a channel on one of the many public or private IRC servers, but
nowadays, everyone seems to want to consolidate their projects under Slack's
infrastructure. This means if you joined a company or a software
project that started during the past few years, more likely than not, you'll
need to use Slack.
&lt;/p&gt;

&lt;p&gt;
I'm part of a few Slack networks, and up until recently, I honestly didn't
think all that much about Slack, because unlike some other proprietary chat
networks, Slack had the sense to offer IRC and XMPP gateways. This meant that
you weren't required to use its heavy web app, but instead, you could use
whatever client you preferred yet still connect to Slack networks. Sure, my
text-based IRC client didn't show animated Giphy images or the 20
party-parrot gifs in a row, but to me, that was a feature. Unfortunately, Slack could
no longer justify the engineering effort to backport web chat features to IRC
and XMPP, so the company announced it was shutting down its IRC and XMPP
gateways.
&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/what-really-ircs-me-slack" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 30 Jul 2018 15:15:38 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1339928 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Now Slack-ing Off Is Encouraged!</title>
  <link>https://www.linuxjournal.com/content/now-slack-ing-encouraged</link>
  <description>  &lt;div data-history-node-id="1339373" 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/12088slackf1.png" width="790" height="600" 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/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&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;
If your company hasn't already chosen to utilize &lt;a href="https://slack.com"&gt;Slack&lt;/a&gt;, it's probably
only a matter of time. For anyone who has been around IRC before,
Slack might seem like a total ripoff. I'll be honest, when one of the
companies I work for starting using it, I wasn't impressed, because I
could do all the same things with IRC.
&lt;/p&gt;


&lt;p&gt;
I was wrong—at least partially. Slack is certainly an IRC-like
communication tool that is perfect for communicating with other people in
an organization. What makes it special is its ability to integrate with
other services so well. Things like Google-based authentication for single-sign-in is simple to configure. It also has a very robust API, so you can
integrate countless third-party tools into your Slack environment. Some
of them are silly (like adding GIPHY so you can insert animated GIF
files into your conversations), and some are incredibly useful (like
triggering remote scripts to give you real-time feedback in a chat window).
&lt;/p&gt;
&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1000009/12088slackf1.png" alt="" title="" class="imagecache-large-550px-centered" /&gt;&lt;p&gt;
Plus, if you're like me and you can't do without IRC, it's possible
to integrate IRC into your Slack experience using &lt;a href="https://sameroom.io"&gt;Sameroom&lt;/a&gt;.
Truly
it's the ability to integrate with other services that makes Slack so
powerful, and its ease of use makes it popular for companies, even when
the employees aren't all IT folks. Check it out today if you're looking
for a great way to communicate with groups of people in your life that
might not appreciate the nuances of IRC!
&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/now-slack-ing-encouraged" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 02 May 2017 15:22:28 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1339373 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Bounce Around IRC with ZNC</title>
  <link>https://www.linuxjournal.com/content/bounce-around-irc-znc</link>
  <description>  &lt;div data-history-node-id="1338799" 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/11887zncf1.png" width="426" height="459" 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/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&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;
In my discussion on IRC with "bkidwell" (see the Non-Linux FOSS article
for more on our talk), we were discussing how we connect to IRC. My main
method is to SSH in to my co-located Raspberry Pi in Austria and connect
to a screen session I have running that is constantly connected to IRC
with Irssi. This works really well for me, and I never miss messages
when I'm away. The big problem I have is occasionally I'm away from
a laptop, and so I can't efficiently use the terminal to chat. It might
be technically possible to IRC chat via an SSH app on my phone, but it
would mean super-tiny text and awkward keyboard shortcuts.
&lt;/p&gt;

&lt;p&gt;
That's where ZNC comes into play. I've never used an IRC bouncer before,
but the concept is that it stays connected to IRC using your credentials,
and it allows you to connect to it with your IRC app and pick up where
you left off. Functionally, it's like a screen session, but instead of
connecting via SSH, you connect with an IRC client. Since it keeps you
logged in, when you connect, you have access to the chats and personal
queries that have occurred while you were disconnected. Plus, it allows
you to connect from multiple locations at once and use whatever IRC
client you want—there's no "client" application you have to use!
&lt;/p&gt;

&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1002061/11887zncf1.png" alt="" title="" class="imagecache-large-550px-centered" /&gt;&lt;p&gt;
(Image from &lt;a href="http://znc.in"&gt;ttp://znc.in&lt;/a&gt;)
&lt;/p&gt;

&lt;p&gt;
ZNC is really an awesome way to use IRC. It allows me to keep using
Irssi too, because I just point Irssi at the ZNC bouncer, and never
miss a beat even when I'm remote on my phone. If you use IRC regularly
or are hesitant because of the issues I've highlighted here, I urge
you to check out ZNC. It's at &lt;a href="http://znc.in"&gt;http://znc.in&lt;/a&gt; and is available
for most platforms.
&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/bounce-around-irc-znc" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 12 Aug 2015 19:43:12 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1338799 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Weechat, Irssi's Little Brother</title>
  <link>https://www.linuxjournal.com/content/weechat-irssis-little-brother</link>
  <description>  &lt;div data-history-node-id="1086161" 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/11500weef1.png" width="592" height="385" 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/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&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;
It may not be fair to call Weechat the little brother of Irssi, but in
my short introduction to it, that's what it felt like. If Weechat didn't
seem quite as powerful as Irssi to me, I definitely can say that it is
better-looking out of the box. So, little brother has one thing going for him!
&lt;/p&gt;

&lt;p&gt;
The other day, I was tweeting with Janne Jokitalo about the sorts of
things two nerds tweet about: command-line editors and command-line chat
clients. I mentioned Irssi in a screen, and he mentioned Weechat. I'm
glad he did! Right out of the box, Weechat does some things I've never
been able to get Irssi to do well. First off, it has a list of users
docked to the right side of the terminal (Figure 1). I always liked
that feature in the GUI client X-Chat, but I couldn't get it to work well
in Irssi. I also think the look and feel is far more friendly 
than that of Irssi. Yes, with the help of Kyle Rankin, I've been able to
tweak Irssi into the perfect chatting machine, but Weechat seems to
have a more gentle learning curve.
&lt;/p&gt;

&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1002061/11500weef1.png" alt="" title="" class="imagecache-large-550px-centered" /&gt;&lt;p&gt;
Figure 1. The &lt;em&gt;Linux Journal&lt;/em&gt; IRC bot works in Weechat,
so I was happy.
&lt;/p&gt;
&lt;p&gt;
It supports IRC and Jabber right now, but the Web site claims more
protocols are coming. Weechat is probably already in your distro's
repository,
so install it, and give it a whirl. You'll get all the
geek creed of Irssi with some fancy interface additions! Due to its
focus on usability and its roots in hard-core nerd-dom on the command
line, Weechat is this month's Editors' Choice selection. Check it out at
&lt;a href="http://www.weechat.org"&gt;http://www.weechat.org&lt;/a&gt;.
&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/weechat-irssis-little-brother" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 11 Jun 2013 15:58:31 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1086161 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>IRC, Still the Best Support Around</title>
  <link>https://www.linuxjournal.com/content/irc-still-best-support-around</link>
  <description>  &lt;div data-history-node-id="1012768" 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/irc.png" width="500" height="349" alt="IRC chat room" title="#linuxjournal on freenode.net" 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/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&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;If you haven't gotten our subtle hints during the past year or so, IRC certainly is not dead. It really is the best way to get knowledgeable support from the folks who know best. There are a few caveats, however, that may not be obvious to people new to this old-school chat protocol.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Get a Good Client&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If you just want to stop into the #linuxjournal channel for some quick banality, a Web-based client like the one at &lt;a href="https://www.linuxjournal.com/irc"&gt;linuxjournal.com/irc&lt;/a&gt; is fine. You can drop in, request a !coffee from JustinBot, and chitchat with fellow geeks. If you're looking for something a bit more useful for the long haul, a native client makes more sense. Many people (myself included) like &lt;a href="http://xchat.org/"&gt;X-Chat&lt;/a&gt;. There are plenty of other options, like the command-line-only &lt;a href="http://www.irssi.org/"&gt;Irssi&lt;/a&gt;, but X-Chat offers a nice balance between features and usability.&lt;/p&gt;
&lt;p&gt;If you look back at Kyle Rankin's &lt;a href="https://www.linuxjournal.com/googlesearch?cx=014164207538395607518%3Aw82fvojcgcu&amp;cof=FORID%3A11&amp;as_q=Hack+and+%2F&amp;sa=Search#1150"&gt;Hack and / articles&lt;/a&gt; from the past year or so, you'll find easy ways to integrate your entire lifestyle into IRC. Kyle does everything from chatting to twittering inside his terminal window, and he shows us all how to do the same.&lt;/p&gt;
&lt;p&gt;The opposite approach, which is actually what I do, is to add IRC as another instant-messaging protocol on my IM client. Although Kopete and Empathy may be slick-looking for instant messaging, none come close to &lt;a href="http://www.pidgin.im/"&gt;Pidgin&lt;/a&gt;'s elegance with IRC. Check out my video tech tip on how to set up IRC inside Pidgin if that makes more sense to the way you work during the day: &lt;a href="https://www.linuxjournal.com/video/irc-chats-pidgin"&gt;linuxjournal.com/video/irc-chats-pidgin&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;IRC Etiquette&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Every channel you visit will have a different "personality" to it. The #linuxjournal channel on Freenode, for example, is really a goofy, easy-going channel full of geeks having fun. If you come visit us and say “Garble bargle, loopity loo”, no one will find you odd. In fact, you'll fit in quite nicely. On other channels, specifically channels where developers hang out related to a specific application, the atmosphere might be a bit more stuffy. My suggestion: hang out in a room for a while before you post questions. There may be links in the channel pointing to FAQs or information about how to conduct yourself without making anyone angry.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Be Patient&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;IRC is the sort of thing most geeks leave running but don't monitor constantly. If you pose a question, but don't get a response for a while, just wait. If you have a question for a specific person, typing his or her name in the channel often will alert the person (I have Pidgin set up to do that, and many folks do the same with their IRC clients). And finally, don't forget, it's a community. If you see a question you can answer, do it! &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/irc-still-best-support-around" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 09 Jul 2010 13:00:00 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1012768 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
