<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <small>
      <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style></style> </small>
    <table class="backgroundTable" cellpadding="0" cellspacing="0"
      bgcolor="#ffffff" width="100%">
      <tbody>
        <tr>
          <td align="left" valign="top">
            <table cellpadding="0" cellspacing="0">
              <tbody>
                <tr>
                  <td style="border-top: 0px solid rgb(0, 0, 0);
                    border-bottom: 1px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 255); text-align:
                    center;" align="center"><span style="font-size:
                      10px; color: rgb(96, 96, 96); line-height: 200%;
                      font-family: verdana; text-decoration: none;">Email
not
                      displaying correctly? <a
                        href="http://www.oplin.org/4cast/"
                        style="font-size: 10px; color: rgb(0, 0, 255);
                        line-height: 200%; font-family: verdana;
                        text-decoration: none;">View
                        it in your browser.</a></span></td>
                </tr>
                <tr>
                  <td style="border-top: 0px solid rgb(51, 51, 51);
                    border-bottom: 0px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 255);">
                    <center><a href=""><img id="editableImg1"
                          src="cid:part2.03020201.01020001@oplin.org"
                          title="OPLIN" alt="OPLIN 4Cast" border="0"
                          align="middle"></a></center>
                  </td>
                </tr>
              </tbody>
            </table>
            <table style="width: 763px; height: 877px;" cellpadding="20"
              cellspacing="0" bgcolor="#ffffff">
              <tbody>
                <tr>
                  <td style="font-size: 12px; color: rgb(0, 0, 0);
                    line-height: 150%; font-family: trebuchet ms;"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
                    bgcolor="#ffffff" valign="top">
                    <p><!-- Make sure you modify the 4Cast title in this section -->
                      <span style="font-size: 20px; font-weight: bold;
                        color: rgb(0, 0, 0); font-family: arial;
                        line-height: 110%;">OPLIN 4cast #399: Chatting
                        gets serious</span><br>
                      <!-- Make sure you modify the date of the 4Cast in this section -->
                      <span style="font-size: 11px; font-weight: normal;
                        color: rgb(102, 102, 102); font-style: italic;
                        font-family: arial;">August 20th, 2014</span></p>
                    <!-- Begin copy of Web Source here  -->
                    <p style="text-align: justify;font-size: 16px;
                      font-family: arial; line-height: 110%;"><img
                        src="cid:part4.07040502.06050205@oplin.org"
                        alt="chat bubbles" align="left" height="114"
                        width="110">Instant messaging is not new.
                      Neither is the online chat room. The CompuServe
                      "CB Simulator" in 1980 was probably the first
                      Internet application that we would recognize now
                      as instant messaging. Internet Relay Chat (IRC),
                      the ancestor of today's chat rooms, dates from
                      1988. Now add the more modern increase in the use
                      of mobile devices, mix in some annoyance with
                      email spam, and suddenly the venerable old chat is
                      a hot business communication application. When you
                      remember that many of the people now entering the
                      workforce grew up using their phones to message
                      friends, that's not really a surprising
                      development.
                    </p>
                    <div> </div>
                    <ul style="text-align: left;">
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://gigaom.com/2014/08/01/why-these-startups-think-chat-apps-are-the-next-big-thing-in-workplace-collaboration/">Why
                          these startups think chat apps are the next
                          big thing in workplace collaboration</a>
                        (GigaOM | Jonathan Vanian) "The idea is that
                        workers are now spending their days immersed in
                        the world of the chat box; a sort of modern-day
                        equivalent of the office water cooler, where
                        ideas and jokes can be shared, but also - thanks
                        to software and the ability to link up to the
                        storage-service providers - the place where
                        documents can be stored, indexed and able to be
                        easily accessed. According to a recent <a
href="http://research.gigaom.com/report/contextual-conversation-work-chat-will-dominate-collaboration/">Gigaom
                          Research report</a> by Stowe Boyd, this idea
                        of contextual conversation 'is likely to become
                        the dominant social motif of the next generation
                        of work-technology applications.'"</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://www.citeworld.com/article/2115224/mobile-byod/enterprise-mobile-messaging-overview.html">Why
                          enterprise mobile messaging is the latest
                          startup craze</a> (CITEworld | Matt
                        Weinberger) "In libraries, coffee shops, and
                        anywhere else where workers are not in front of
                        a computer all day, text and IM is the
                        smartphone-friendly mode of communication of
                        choice. That means that coworkers need to
                        befriend each other on their personal social
                        networks, or else swap phone numbers, neither of
                        which makes for a healthy or comfortable
                        life-work balance. It's a lot easier when you
                        empower those same front-office workers with a
                        tool where they don't need to know the phone
                        number of the person they need to talk to."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://highspeedinternet.com/blog/technology/beyond-google-hangouts-what-these-chat-apps-are-doing-differently">Beyond
                          Google Hangouts: What these chat apps are
                          doing differently</a> (HSI blog | Ryann
                        Rasmussen) "Many of the chat startups mentioned
                        here [Slack, HipChat, Flowdock, and Convo] are
                        still in their infancy, but they're already
                        making a splash. Inspired by everything from
                        small businesses to giants, these chat startups
                        are looking at the workplace from every angle.
                        Larger companies like Rally, Atlassian and
                        Microsoft are purchasing these startups, a
                        testament to their potential in offices around
                        the globe."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://www.theverge.com/2014/8/12/5991005/slack-is-killing-email-yes-really">Slack
                          is killing email</a> (The Verge | Ellis
                        Hamburger) "There's something intrinsic to
                        communicating with a larger number of people
                        that's going to be difficult to manage,
                        especially given the amount of information we
                        get. Email has gotten worse over the last 10
                        years or so. Ten years ago, 50 to 60 percent of
                        email was from another person, and now it's 8 to
                        10 percent. The other 90 percent is from a
                        machine - email marketing, receipts, new Twitter
                        followers, Facebook comments, check-ins, monthly
                        statements, blah blah blah."</li>
                    </ul>
                    <div style="text-align: left;"> </div>
                    <p style="text-align: left; font-size: 20px;
                      font-family: arial; line-height: 110%;"><small><strong><em>Articles
                            from <a href="http://ohioweblibrary.org">Ohio
                              Web Library</a>:</em></strong></small><br>
                    </p>
                    <div style="text-align: justify; font-size: 16px;
                      font-family: arial; line-height: 110%;">
                      <ul>
                        <li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/pov/detail/detail?sid=405ea30a-035d-41a0-be9a-5651a1a65009%40sessionmgr4001&vid=0&hid=4201&bdata=JnNpdGU9cG92LWxpdmU%3d#db=pwh&AN=33627232">Instant
                            messaging cuts workplace interruption.</a> (<em>USA
                            Today Magazine</em>, August 2008, p1-2)</li>
                        <li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=1106555b-5f3f-4064-a258-edec5c4efd93%40sessionmgr4004&vid=0&hid=4201&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=83789954">Instant
                            messaging as a task-support tool in
                            information technology organizations.</a> (<em>Journal
                            of Business Communication</em>, January
                          2013, p68-86 | Pilar Pazos, Jennifer M. Chung,
                          and Marina Micari)</li>
                        <li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=dc90e6e2-2827-4588-87db-8620b35b8733%40sessionmgr4002&vid=0&hid=4201&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=95753995">Nature
                            and nurture: The impact of automaticity and
                            the structuration of communication on
                            virtual team behavior and performance.</a>(<em>MIS
                            Quarterly</em>, June 2014, p521-A4 | Valerie
                          L. Bartelt and Alan R. Dennis)</li>
                      </ul>
                    </div>
                    <div style="text-align: left;"> </div>
                    <!-- End paste of web source here --> </td>
                </tr>
                <tr>
                  <td style="" solid="" background-color:="" rgb(255,=""
                    255,="" 255);="" >=""
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
                    valign="top" width="760"><span style="font-size:
                      10px; color: rgb(96, 96, 96); line-height: 100%;
                      font-family: verdana;">
                      <hr><!-- Begin standard subscription verbiage -->
                      <div style="text-align: justify;">The <strong><em>OPLIN
                            4cast</em></strong>
                        is a weekly compilation of
                        recent headlines, topics, and trends that could
                        impact public
                        libraries. You can subscribe to it in a variety
                        of ways, such as: <br>
                      </div>
                      <div style="text-align: left;"> </div>
                      <ul>
                        <li style="text-align: justify;"><strong>RSS
                            feed.</strong>
                          You
                          can receive the OPLIN 4cast
                          via RSS feed by subscribing to the following
                          URL:
                          <a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/index.php/?feed=rss2">http://www.oplin.org/4cast/index.php/?feed=rss2</a>.
                        </li>
                        <li style="text-align: justify;"><strong>Live
                            Bookmark.</strong>
                          If you're using the Firefox
                          web browser, you can go to the 4cast website
                          (<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/">http://www.oplin.org/4cast/</a>) and click on the
                          orange "radio wave" icon
                          on the right side of the address bar. In
                          Internet Explorer 7, click on
                          the same icon to view or subscribe to the
                          4cast RSS feed. </li>
                        <li style="text-align: justify;"><strong>E-mail.</strong>
                          You
                          can have the OPLIN 4cast
                          delivered via e-mail (a'la OPLINlist and
                          OPLINtech) by subscribing to
                          the 4cast mailing list at
                          <a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/OPLIN4cast">http://mail.oplin.org/mailman/listinfo/OPLIN4cast</a>.
                        </li>
                      </ul>
                    </span> </td>
                </tr>
                <tr>
                  <td style="border-top: 0px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 204);"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg"
                    valign="top" width="760"> <br>
                  </td>
                </tr>
              </tbody>
            </table>
          </td>
        </tr>
      </tbody>
    </table>
    <small>
      <title>OPLIN 4Cast</title>
      <style>
 .headerTop { background-color:#FFFFFF; border-top:0px solid #000000; border-bottom:1px solid #FFFFFF; text-align:center; }
 .adminText { font-size:16px; color:#0000FF; line-height:200%; font-family:verdana; text-decoration:none; }
 .headerBar { background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:0px solid #FFFFFF; }
 .title { font-size:20px; font-weight:bold; color:#000000; font-family:arial; line-height:110%; }
 .subTitle { font-size:11px; font-weight:normal; color:#000000; font-style:italic; font-family:arial; }
 .defaultText { font-size:12px; color:#000000; line-height:150%; font-family:trebuchet ms; }
 .footerRow { background-color:#FFFFCC; border-top:0px solid #FFFFFF; }
 .footerText { font-size:10px; color:#996600; line-height:100%; font-family:verdana; }
 a { color:#0000FF; color:#0000FF; color:#0000FF; }
  </style>
    </small>
  </body>
</html>