<?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: PBWiki hits 50,000 wikis</title>
	<atom:link href="http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Mon, 16 Apr 2012 18:32:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<item>
		<title>By: Eric Skiff</title>
		<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/comment-page-1/#comment-2880</link>
		<dc:creator>Eric Skiff</dc:creator>
		<pubDate>Mon, 10 Apr 2006 06:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/#comment-2880</guid>
		<description>oops - forgot to URL encode the &lt;a href=&quot;&quot;&gt; there, so it&#039;s all an empty link after a certain point! Sorry!</description>
		<content:encoded><![CDATA[<p>oops &#8211; forgot to URL encode the &lt;a href=&#8221;"&gt; there, so it&#8217;s all an empty link after a certain point! Sorry!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Skiff</title>
		<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/comment-page-1/#comment-2879</link>
		<dc:creator>Eric Skiff</dc:creator>
		<pubDate>Mon, 10 Apr 2006 06:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/#comment-2879</guid>
		<description>Hey there Chris, I&#039;ve struggled with PBWiki a bit, so please don&#039;t take this as a rant as much as one user&#039;s experience with it.

To be honest, the PBWiki was just barely functional for me when working on the BarCamp stuff and now on the &lt;a href=&quot;http://pinkomarketing.pbwiki.com/&quot; rel=&quot;nofollow&quot;&gt;Pinko Marketing&lt;/a&gt; wiki.

Perhaps it&#039;s because I&#039;m used to the mediawiki syntax. It&#039;s what I used when I edit wikipedia and wikinews. It&#039;s what I&#039;ve set up on our intranet at the nonprofit where I work. 

With PBwiki, it gets too clever sometimes, and it&#039;s too strict others. It makes internal links to words when I didn&#039;t ask it to, and often inappropriately. For instance, FeltUpTV.com becomes a link to the new, empty page FeltUpTV on the PBwiki, and the .com goes unlinked.

To link to the outside world, I either have to use the full web address or link using an &lt;a href rel=&quot;nofollow&quot;&gt; tag? Multi-level unordered lists are still beyond me as well. The multi-star method:

*A
**A.1
*B

doesn&#039;t work. In fact, none of those work, since it has to be
* A 
with the whitespace intact to even show up as a bullet.

Struggling to make my preview look right, I look for the &quot;editing help&quot; link and it&#039;s not available. I save my page, ugly and broken, and generally, I don&#039;t come back.</description>
		<content:encoded><![CDATA[<p>Hey there Chris, I&#8217;ve struggled with PBWiki a bit, so please don&#8217;t take this as a rant as much as one user&#8217;s experience with it.</p>
<p>To be honest, the PBWiki was just barely functional for me when working on the BarCamp stuff and now on the <a href="http://pinkomarketing.pbwiki.com/" rel="nofollow">Pinko Marketing</a> wiki.</p>
<p>Perhaps it&#8217;s because I&#8217;m used to the mediawiki syntax. It&#8217;s what I used when I edit wikipedia and wikinews. It&#8217;s what I&#8217;ve set up on our intranet at the nonprofit where I work. </p>
<p>With PBwiki, it gets too clever sometimes, and it&#8217;s too strict others. It makes internal links to words when I didn&#8217;t ask it to, and often inappropriately. For instance, FeltUpTV.com becomes a link to the new, empty page FeltUpTV on the PBwiki, and the .com goes unlinked.</p>
<p>To link to the outside world, I either have to use the full web address or link using an <a href rel="nofollow"> tag? Multi-level unordered lists are still beyond me as well. The multi-star method:</p>
<p>*A<br />
**A.1<br />
*B</p>
<p>doesn&#8217;t work. In fact, none of those work, since it has to be<br />
* A<br />
with the whitespace intact to even show up as a bullet.</p>
<p>Struggling to make my preview look right, I look for the &#8220;editing help&#8221; link and it&#8217;s not available. I save my page, ugly and broken, and generally, I don&#8217;t come back.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/comment-page-1/#comment-2871</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 09 Apr 2006 19:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/#comment-2871</guid>
		<description>Word-like WYSIWYG</description>
		<content:encoded><![CDATA[<p>Word-like WYSIWYG</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan</title>
		<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/comment-page-1/#comment-2863</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Sun, 09 Apr 2006 10:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/#comment-2863</guid>
		<description>Per person RSS feeds!  I want to be able to track a user to see what they&#039;re interested in and what changes they make.  I&#039;m all about user-centric; so people can mix/match communities, but not everyone is on board the blogging bandwagon yet...

Most Wiki&#039;s lack this feature (although MediaWiki has a few hacks).</description>
		<content:encoded><![CDATA[<p>Per person RSS feeds!  I want to be able to track a user to see what they&#8217;re interested in and what changes they make.  I&#8217;m all about user-centric; so people can mix/match communities, but not everyone is on board the blogging bandwagon yet&#8230;</p>
<p>Most Wiki&#8217;s lack this feature (although MediaWiki has a few hacks).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/comment-page-1/#comment-2860</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Sun, 09 Apr 2006 02:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2006/04/08/pbwiki-hits-50000-wikis/#comment-2860</guid>
		<description>&quot;what features do you look for in a wiki?&quot;

I&#039;m not a big Wiki user, but I use a few at work for documentation purposes and it works great. It&#039;s not PBWiki - although now that&#039;s a consideration - but one thing I find frustrating with wikis is the styling.

I can highlight a word and click the Bold in the toolbar and it does the ** around the word , which is perfect. But if I goofed and want to un-bold the word, I can&#039;t highlight the word and click the toolbar Bold again - it just double-bolds it with another set of **

This behavior is what I expect thanks to Word and other editors but not what I get in wikis. And because the toolbar is there, I typically don&#039;t (have to) remember the actual &#039;code&#039; to make a word bold - is it two asterisks? Or three? Or was it one? Because of that (and because it&#039;s there) I use the toolbar - but when I goof I have to do a lot of manual editing to get it back to its original state so I can re-click the toolbar option, or try to remember and type the styling in by hand.

And in the specific &quot;it would be cool to have&quot; category, a styling button for the PRE or CODE tag would be cool - or a customizable toolbar? Since my experience with wikis is for documentation of source code, I have to type in the preformatting tags by hand, which is easy - but hey, if there&#039;s button for it, all the better.

And as my first look at PBWiki, I must say it is far better than the one I am used to using (I don&#039;t remember which one it is). I will certainly suggest using it as an alternative and for future needs. Keep up the great work!</description>
		<content:encoded><![CDATA[<p>&#8220;what features do you look for in a wiki?&#8221;</p>
<p>I&#8217;m not a big Wiki user, but I use a few at work for documentation purposes and it works great. It&#8217;s not PBWiki &#8211; although now that&#8217;s a consideration &#8211; but one thing I find frustrating with wikis is the styling.</p>
<p>I can highlight a word and click the Bold in the toolbar and it does the ** around the word , which is perfect. But if I goofed and want to un-bold the word, I can&#8217;t highlight the word and click the toolbar Bold again &#8211; it just double-bolds it with another set of **</p>
<p>This behavior is what I expect thanks to Word and other editors but not what I get in wikis. And because the toolbar is there, I typically don&#8217;t (have to) remember the actual &#8216;code&#8217; to make a word bold &#8211; is it two asterisks? Or three? Or was it one? Because of that (and because it&#8217;s there) I use the toolbar &#8211; but when I goof I have to do a lot of manual editing to get it back to its original state so I can re-click the toolbar option, or try to remember and type the styling in by hand.</p>
<p>And in the specific &#8220;it would be cool to have&#8221; category, a styling button for the PRE or CODE tag would be cool &#8211; or a customizable toolbar? Since my experience with wikis is for documentation of source code, I have to type in the preformatting tags by hand, which is easy &#8211; but hey, if there&#8217;s button for it, all the better.</p>
<p>And as my first look at PBWiki, I must say it is far better than the one I am used to using (I don&#8217;t remember which one it is). I will certainly suggest using it as an alternative and for future needs. Keep up the great work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

