<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://myst-technology.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://myst-technology.com/public/?>

<MySmartChannels Public="true" UserID="125119" dT="102" t0="1268718473140">
     <GetChannel_Result>
      <ChannelDomain>
       <Domain>
        <ObjectID>192423</ObjectID>
        <ObjectClass>Domain</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="MyST Technology Partners, Inc. Channels">125122</OwnerID>
        <CreatedByID ObjectClass="User" Title="$MySTHome">125116</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="$MySTHome">125116</ModifiedByID>
        <CreateTime Title="2007-12-13 20:37:30 EST">1197596250154</CreateTime>
        <ModifyTime Title="2009-07-05 18:53:29 EDT">1246834409267</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>[Public] What's New</Name>
        <Summary>The Latest Postings for MyST Technology Partners, Inc.</Summary>
        <Description/>
       </Domain>
       <ObjectCounts OwnerID="192423"/>
       <UserPermissions>
        <CanCreateChannelItem>false</CanCreateChannelItem>
        <CanDelete>false</CanDelete>
        <CanDiscover>true</CanDiscover>
        <CanEdit>false</CanEdit>
        <CanEditPermissions>false</CanEditPermissions>
        <CanPublish>false</CanPublish>
        <CanRead>true</CanRead>
       </UserPermissions>
      </ChannelDomain>
      <ChannelProperties>
            <Copyright>2009 MyST Technology Partners, Inc.--All Rights Reserved</Copyright>

            <Legal>This channel is part of the MyST Technology Partners, Inc. blogsite--Powered by MyST Blogsite®.</Legal>

            <Views>
             <View>
              <Name>blog</Name>

              <Model>blogsite/MySTHome/whatsnew</Model>

              <Style/>

              <Scheme/>

       </View>

             <View>
              <Name>edit-item</Name>

              <Model>blogsite/MySTHome/web</Model>

              <Style/>

              <Scheme/>

       </View>

             <View>
              <Name>left</Name>

              <Model>blogsite/MySTHome/left-content</Model>

              <Style/>

              <Scheme/>

       </View>

             <View>
              <Name>right</Name>

              <Model>blogsite/MySTHome/right-content</Model>

              <Style/>

              <Scheme/>

       </View>

             <View>
              <Name>wide</Name>

              <Model>blogsite/MySTHome/wide-content</Model>

              <Style/>

              <Scheme/>

       </View>

      </Views>

            <Keywords>
             <Keyword>latest news</Keyword>

             <Keyword>recent posts</Keyword>

             <Keyword>MyST Technology Partners, Inc.</Keyword>

             <Keyword>archive.blog:Daily 0 1 2 3 4 5 6 7 8 9 10 11 12 13</Keyword>

             <Keyword>image.description:Web site for MyST Technology Partners, Inc.</Keyword>

             <Keyword>image.height:24</Keyword>

             <Keyword>image.link.url:http://myst-technology.com</Keyword>

             <Keyword>image.title:MyST Technology Partners, Inc.</Keyword>

             <Keyword>image.url:http://myst-technology.com/styles/blogsite/MySTHome/images/rss.jpg</Keyword>

             <Keyword>image.width:136</Keyword>

             <Keyword>lang:en-us</Keyword>

             <Keyword>rss.description:full</Keyword>

             <Keyword>rss.limit:15</Keyword>

             <Keyword>captyx-hook._top:whatsnew-top</Keyword>

             <Keyword>captyx-hook._bottom:whatsnew-bottom</Keyword>

      </Keywords>

            <Refresh>1440</Refresh>

     </ChannelProperties>
      <Items>
       <Item>
        <Resource>
         <ObjectID>250165</ObjectID>
         <ObjectClass>Resource</ObjectClass>
         <OwnerID ObjectClass="Domain" Title="[Weblog] Into the MyST">214</OwnerID>
         <CreatedByID ObjectClass="User" Title="$Admin">1</CreatedByID>
         <ModifiedByID ObjectClass="User" Title="$Admin">1</ModifiedByID>
         <CreateTime Title="2010-02-12 15:16:56 EST">1266005816309</CreateTime>
         <ModifyTime Title="2010-02-15 00:16:32 EST">1266210992730</ModifyTime>
         <SecurityModel>Controlled</SecurityModel>
         <Name>Google Buzz: It Will Change The Future</Name>
         <Summary>The pundits have missed a key point - most have failed to recognize that Buzz [1.0] was built for GMail's 200+ million active users.</Summary>
         <Description>&lt;div&gt; 
    &lt;p&gt;Many have said that the core value in Google Buzz&amp;nbsp;is that it aggregates disparate (and relevant) social information into one place. The reaction to this has been lukewarm and few experts believe it will be successful in winning over the hearts and minds of seemingly happy Twitter, FriendFeed and Facebook users. &lt;/p&gt; 
  &lt;/div&gt; 
  &lt;div&gt;I agree with this assertion only to the extent that we assume Buzz is feature-complete and unlikely to change dramatically in the next five quarters. I have a sense that those of us evaluating it have failed to recognize that Buzz [1.0] was built for GMail's 200+ million active users. Once these users get accustomed to it and they provide feedback, you'll see Buzz 2.0 (Q1, 2011 I suspect).&amp;nbsp;&lt;/div&gt; 
  &lt;div&gt;&lt;br /&gt;&lt;/div&gt; 
  &lt;div&gt;By then a significant number of the 200 million GMail users will have well-established social networks that have been slowly chipping away at Twitter, FriendFeed, and Facebook users, causing user-base erosion at the edges of these services. The GMail/Buzz community who are magically being enticed by this new ability to share quickly and without friction, will slowly tug at friends who don't use GMail, and over time many of those folks will become Buzz-converts.&lt;/div&gt; 
  &lt;div&gt;&lt;br /&gt;&lt;/div&gt; 
  &lt;div&gt;When Buzz 2.0 emerges in 2011 with seamless integration to Outlook and other email services, Google will have a head of steam, 275 million GMail users, and most will be comfortable sharing micro-posts and other information artifacts through Buzz. It will only be a matter of time before the features of Wave and other Google business apps creep into the feature set, possibly as soon as Q3 2010. By 2012 Twitter, FriendFeed, and Facebook will have a real tiger by the tail trying to maintain market share for Facebook activity that involves communication and sharing - their core benefits.&lt;/div&gt; 
  &lt;div&gt;&lt;br /&gt;&lt;/div&gt; 
  &lt;div&gt;Indeed, Facebook is not the new MySpace as [some] pundits have claimed. Instead, it will emerge as one of the first meso-scale SENs (social entertainment network). FriendFeed will go away not because there are better alternatives, but because it will be off-message and out of context for the Facebook that will emerge in 2012. Twitter and other 140 character systems will become quasi-protocols because they're useful infrastructure elements for the greater segment known as micro-posts and they'll continue to meet real-time information awareness requirements.&lt;/div&gt; 
  &lt;div&gt;&lt;br /&gt;&lt;/div&gt; 
  &lt;div&gt; 
    &lt;p&gt;I've always thought that there was healthy demand for mini-posts -- i.e., longer than 140 characters and shorter (and more casual) information objects than a 600 word blog post. &lt;/p&gt; 
    &lt;p&gt;A conversation thread in Buzz is a good example of mini-posts; brief buzzes become deeper conversations; some comments transition into new posts; some emerge as macro-posts in other blogs (this blog post began its existence as a comment). Ergo, my intent was to write a quick comment, but I ended up with an article. But more important, Buzz can capture both small and large artifacts.&lt;/p&gt; 
  &lt;/div&gt; 
  &lt;div&gt;While Twitter meets real-time awareness requirements, Buzz provides a medium for real-time conversations that may (or may not) stem from three forms of communication; (i) micro-posts, (ii) macro-posts, or (iii) email threads.&lt;/div&gt; 
  &lt;div&gt;&lt;br /&gt;&lt;/div&gt; 
  &lt;div&gt; 
    &lt;p&gt;Google has brilliantly positioned a fraction of Wave's functionality (AKA Buzz) in the center of the publishing triangle. Other features of Wave will be slowly blended into the infrastructure in a manner that will transform the triangle into a square (i.e., adding another cornerstone). &lt;/p&gt; 
    &lt;p&gt;Imagine a rinse-repeat strategy that (over time) continues to add more cornerstones of communication, sharing, new information object types, search, identity, security, private spaces, etc. The strategy seems clear - Google is building a circle that encompasses a comprehensive topology of all information artifacts people create, share, and consume.&lt;/p&gt; 
    &lt;p&gt;Brilliant.&amp;nbsp;&lt;/p&gt; 
  &lt;/div&gt;</Description>
         <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
         <ContentType>application/xml</ContentType>
         <ContentDocument>
          <ItemProperties>
                <CommonProperties>
                 <Hidden>false</Hidden>

                 <Keywords>
                  <Keyword>Facebook</Keyword>

                  <Keyword>FriendFeed</Keyword>

                  <Keyword>Google Buzz</Keyword>

                  <Keyword>macro-post</Keyword>

                  <Keyword>micro-post</Keyword>

                  <Keyword>mini-post</Keyword>

                  <Keyword>SEN</Keyword>

                  <Keyword>social entertainment network</Keyword>

                  <Keyword>Twitter</Keyword>

       </Keywords>

                 <Links>
                  <Link>
                   <Title>Google Buzz</Title>

                   <Synopsis>Start conversations about the things you find interesting. Share updates, photos, videos and more with your friends.</Synopsis>

                   <URL>http://buzz.google.com</URL>

        </Link>

                  <Link>
                   <Title>Buzz by Jason Calacanis from Twitter</Title>

                   <Synopsis>Twitter MUST respond to Google Buzz with a) enclosures and b) longer posts and c) threaded messages. @ev @biz @fredwilson @bijan #googlebuzz</Synopsis>

                   <URL>http://www.google.com/buzz/jasoncalacanis/dzz1VZhpdrZ/Twitter-MUST-respond-to-Google-Buzz-with-a</URL>

        </Link>

       </Links>

      </CommonProperties>

                <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                 <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                  <ns3:Attribute name="Quote" type="large-text">
                   <ns3:Value>By Q1, 2011 a significant number of the 200 million GMail users will have well-established [Buzz-based] social networks that have been slowly chipping away at Twitter, FriendFeed, and Facebook users, causing noticeable user-base erosion at the edges of these services.</ns3:Value>

        </ns3:Attribute>

                  <ns3:Attribute name="Name" type="text" value="Bill French"/>

                  <ns3:Attribute name="Blog" type="url"/>

                  <ns3:Attribute name="Title" type="text"/>

                  <ns3:Attribute name="Company" type="text" value="MyST Technology Partners"/>

                  <ns3:Attribute name="Web" type="url" value="http://www.google.com/profiles/bill.french"/>

                  <ns3:Attribute name="Icon" type="checkbox" value="true"/>

                  <ns3:Attribute name="Frame" type="text" value="bars"/>

                  <ns3:Attribute name="HTML" type="checkbox" value="false"/>

                  <ns3:Attribute name="Alignment" type="text" value="right"/>

                  <ns3:Attribute name="Text Size" type="text" value="medium"/>

                  <ns3:Attribute name="Container" type="text" value="div"/>

                  <ns3:Attribute name="Container ID" type="text"/>

                  <ns3:Attribute name="Container Class" type="text" value="Quote"/>

                  <ns3:Attribute name="Container Style" type="text"/>

                  <ns3:Attribute name="_captyx.position" type="text" value="_top"/>

                  <ns3:Attribute name="_captyx.embargo" type="checkbox" value="false"/>

                  <ns3:Attribute name="_captyx.scope" type="text"/>

                  <ns3:Attribute name="_captyx.sortkey" type="text"/>

       </ns3:Collection>

                 <ns3:Collection name="Bill French" type="urn:MyST-Technology.Structured.Collection.Contact">
                  <ns3:Attribute name="Company" type="text"/>

                  <ns3:Attribute name="Title" type="text"/>

                  <ns3:Attribute name="Address" type="location"/>

                  <ns3:Attribute name="EMail" type="email"/>

                  <ns3:Attribute name="EMail2" type="email"/>

                  <ns3:Attribute name="Work" type="phone"/>

                  <ns3:Attribute name="Mobile" type="phone"/>

                  <ns3:Attribute name="Home" type="phone"/>

                  <ns3:Attribute name="Skype" type="skype"/>

                  <ns3:Attribute name="Web" type="url"/>

                  <ns3:Attribute name="Blog" type="url"/>

                  <ns3:Attribute name="Twitter" type="twitter" value="bfrench"/>

                  <ns3:Attribute name="Photo (L)" type="url:image"/>

                  <ns3:Attribute name="Photo (M)" type="url:image"/>

                  <ns3:Attribute name="Photo (S)" type="url:image"/>

                  <ns3:Attribute name="Notes" type="large-text"/>

       </ns3:Collection>

      </ns3:Details>

                <RemoteInfo>
                 <UserAgent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.89 Safari/532.5</UserAgent>

                 <RemoteHost>127.0.0.1</RemoteHost>

                 <RemoteAddr>127.0.0.1</RemoteAddr>

                 <RemoteUser>$Admin</RemoteUser>

                 <ForwardedFor>173.160.40.189</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
         </ContentDocument>
        </Resource>
        <Shares/>
        <Subjects/>
        <UserPermissions>
         <CanDelete>false</CanDelete>
         <CanDiscover>true</CanDiscover>
         <CanEdit>false</CanEdit>
         <CanEditPermissions>false</CanEditPermissions>
         <CanRead>true</CanRead>
        </UserPermissions>
        <CommentInfo>
         <CommentChannelRef AllowAnonymous="true" Inherited="true">
          <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">190014</ChannelID>
          <UserPermissions>
           <CanCreateChannelItem>false</CanCreateChannelItem>
           <CanDelete>false</CanDelete>
           <CanDiscover>true</CanDiscover>
           <CanEdit>false</CanEdit>
           <CanEditPermissions>false</CanEditPermissions>
           <CanPublish>false</CanPublish>
           <CanRead>true</CanRead>
          </UserPermissions>
         </CommentChannelRef>
         <CommentCount>0</CommentCount>
        </CommentInfo>
       </Item>
      </Items>
      <Filter>
       <ns3:Archive xmlns:ns3="urn:MyST-Technology.NodeFilter">
        <ns3:ConfigSpec>Daily 0 1 2 3 4 5 6 7 8 9 10 11 12 13</ns3:ConfigSpec>
       </ns3:Archive>
      </Filter>
      <Archive>
       <ConfigSpec>Daily 0 1 2 3 4 5 6 7 8 9 10 11 12 13</ConfigSpec>
       <ConfigSpecBase>Daily</ConfigSpecBase>
       <Name>Daily</Name>
       <Threshold>0</Threshold>
       <Count>1</Count>
       <Periods>
        <Period>
         <Timestamp Title="2010-02-12 00:00:00 EST">1265950800173</Timestamp>
         <PeriodID>2010-02-12</PeriodID>
         <Label>February 12, 2010</Label>
         <Count>1</Count>
        </Period>
       </Periods>
      </Archive>
     </GetChannel_Result>
    </MySmartChannels>
