<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Om Malik&#8217;s new Network uses PublicSquare, a new Webzine Platform</title>
	<atom:link href="http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/</link>
	<description>Jeremiah Owyang discusses how web tools and social media enable companies to connect with customers</description>
	<lastBuildDate>Thu, 18 Mar 2010 00:18:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Web Strategy by Jeremiah &#187; GigaOm and The Ladders at SF</title>
		<link>http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/comment-page-1/#comment-31431</link>
		<dc:creator>Web Strategy by Jeremiah &#187; GigaOm and The Ladders at SF</dc:creator>
		<pubDate>Fri, 11 May 2007 22:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/#comment-31431</guid>
		<description>[...] A six figure salary is pretty common for any median homeowner in the SF bay area. But for many, a six figure salary is still a benchmark into management. That&#8217;s why the ladders (a premiere recruiting site) helps employers and job seekers connect for a small fee. With the launch of Om&#8217;s recent entrepreneur webzine powered by PublicSquare has launched, I can see the need to connect with the highly qualified. [...]</description>
		<content:encoded><![CDATA[<div style="">
<p>[...] A six figure salary is pretty common for any median homeowner in the SF bay area. But for many, a six figure salary is still a benchmark into management. That&#8217;s why the ladders (a premiere recruiting site) helps employers and job seekers connect for a small fee. With the launch of Om&#8217;s recent entrepreneur webzine powered by PublicSquare has launched, I can see the need to connect with the highly qualified. [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christina</title>
		<link>http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/comment-page-1/#comment-30784</link>
		<dc:creator>Christina</dc:creator>
		<pubDate>Wed, 09 May 2007 19:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/#comment-30784</guid>
		<description>Hi 

I can&#039;t comment on Jerimiah&#039;s insights so much, since I&#039;m not inside his brain, but what *we* find is blog tools don&#039;t scale to multiple authors and workflows. Pageview wise, we&#039;re all the same.  Just drop us a note and we can cover your bandwidth in a seperate agreement if it&#039;s way higher than our plans. We are on engineyard, and can handle what you throw at us. 

The question of scaling is found in what you alluded to in your comment &quot;This is a very large university system, with potentially many different content input streams. &quot;  

When Boxesandarrows was on Movabletype, we had four blogs to manage content, a wiki and a basecamp, as well as mailing lists. Now we have PublicSquare. When we had multi-authors, we had to create a new author with the name &quot;joe smith and fred lise.&quot; Authors and editors communicated via email, stories were lost, authors would occasionally write me asking if their sotry was every going to go live. Our managing editors HATED movabletype -- not because it&#039;s a bad tool, because it was the WRONG tool. Now everything is under one roof, and if an editor or author goes awol, we know, and we can reassign. 

If CMS means conversation managmeent system, that&#039;s what we are. We&#039;re kind a wordpress/basecamp mashup, and if you have more than two people in your system, we are a better choice. 

Our documentation sucks (I admit freely, and we are working to fix) so please email me if you have any questions. I&#039;m happy to help. I can also give you more details on Boxes and Arrows&#039; experience, or give you contact for the editorial staff there.</description>
		<content:encoded><![CDATA[<p>Hi </p>
<p>I can&#8217;t comment on Jerimiah&#8217;s insights so much, since I&#8217;m not inside his brain, but what *we* find is blog tools don&#8217;t scale to multiple authors and workflows. Pageview wise, we&#8217;re all the same.  Just drop us a note and we can cover your bandwidth in a seperate agreement if it&#8217;s way higher than our plans. We are on engineyard, and can handle what you throw at us. </p>
<p>The question of scaling is found in what you alluded to in your comment &#8220;This is a very large university system, with potentially many different content input streams. &#8221;  </p>
<p>When Boxesandarrows was on Movabletype, we had four blogs to manage content, a wiki and a basecamp, as well as mailing lists. Now we have PublicSquare. When we had multi-authors, we had to create a new author with the name &#8220;joe smith and fred lise.&#8221; Authors and editors communicated via email, stories were lost, authors would occasionally write me asking if their sotry was every going to go live. Our managing editors HATED movabletype &#8212; not because it&#8217;s a bad tool, because it was the WRONG tool. Now everything is under one roof, and if an editor or author goes awol, we know, and we can reassign. </p>
<p>If CMS means conversation managmeent system, that&#8217;s what we are. We&#8217;re kind a wordpress/basecamp mashup, and if you have more than two people in your system, we are a better choice. </p>
<p>Our documentation sucks (I admit freely, and we are working to fix) so please email me if you have any questions. I&#8217;m happy to help. I can also give you more details on Boxes and Arrows&#8217; experience, or give you contact for the editorial staff there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ed</title>
		<link>http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/comment-page-1/#comment-30271</link>
		<dc:creator>ed</dc:creator>
		<pubDate>Mon, 07 May 2007 19:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-strategist.com/blog/2007/04/14/om-maliks-new-network-uses-public-square-webzine-platform/#comment-30271</guid>
		<description>Thank you for your insights.  I work for a university which is rushing headlong into selecting a blog application in order to address what seem more to me like a robust webzine type problem.  Can you put a finer point on your observations that blogs become UN-scalable for real webzines.  What are some of the typical problems, and how does PublisSquare address them?  Even their most expensive plan claims to be able to support only &quot;about 139,810 page views&quot; per month.  The site where we would like to launch the blog/zine already triples that as a loose collection of infrequently updated pages.  This is a very large university system, with potentially many different content input streams.  I have two public square accounts with which I am trying out proofs of concept.  I apologize for asking what are perhaps obvious questions, but I have read through much of the documentation for PublicSquare as well as for Wordpress and some other blogging software.  Can you point me to a resource (a case study would be ideal) that might help me to step in front of this moving train, before I allow my university to sign on to the wrong track?</description>
		<content:encoded><![CDATA[<p>Thank you for your insights.  I work for a university which is rushing headlong into selecting a blog application in order to address what seem more to me like a robust webzine type problem.  Can you put a finer point on your observations that blogs become UN-scalable for real webzines.  What are some of the typical problems, and how does PublisSquare address them?  Even their most expensive plan claims to be able to support only &#8220;about 139,810 page views&#8221; per month.  The site where we would like to launch the blog/zine already triples that as a loose collection of infrequently updated pages.  This is a very large university system, with potentially many different content input streams.  I have two public square accounts with which I am trying out proofs of concept.  I apologize for asking what are perhaps obvious questions, but I have read through much of the documentation for PublicSquare as well as for Wordpress and some other blogging software.  Can you point me to a resource (a case study would be ideal) that might help me to step in front of this moving train, before I allow my university to sign on to the wrong track?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
