<?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"
	>
<channel>
	<title>Comments on: Postslurlblogging</title>
	<atom:link href="http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/feed/" rel="self" type="application/rss+xml" />
	<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/</link>
	<description>The experiences in Second Life of Ordinal Malaprop. Scripting, design, observations, notes.</description>
	<pubDate>Thu, 20 Nov 2008 21:53:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Beyond the &#8220;Slurlblogger&#8221; &#171; A Second Blog</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-490</link>
		<dc:creator>Beyond the &#8220;Slurlblogger&#8221; &#171; A Second Blog</dc:creator>
		<pubDate>Fri, 25 Aug 2006 14:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-490</guid>
		<description>[...] From An Engine Fit For My Proceeding BlogHUD works via a central site and allows many people to post to one blog. I am interested more in allowing many people to post to their own Journals, wherever they are. Ideally I would like to have a device which allows automatic posting to Journals of all stripes. This is something of a long-term project however, as many are very different. [...]</description>
		<content:encoded><![CDATA[<p>[...] From An Engine Fit For My Proceeding BlogHUD works via a central site and allows many people to post to one blog. I am interested more in allowing many people to post to their own Journals, wherever they are. Ideally I would like to have a device which allows automatic posting to Journals of all stripes. This is something of a long-term project however, as many are very different. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ordinal.malaprop</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-486</link>
		<dc:creator>ordinal.malaprop</dc:creator>
		<pubDate>Fri, 25 Aug 2006 09:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-486</guid>
		<description>Your English is perfect, sir, and keep watching this Journal for further developments... I have been somewhat busy of late but should have time to spare this coming weekend.</description>
		<content:encoded><![CDATA[<p>Your English is perfect, sir, and keep watching this Journal for further developments&#8230; I have been somewhat busy of late but should have time to spare this coming weekend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Signore Iredell</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-485</link>
		<dc:creator>Signore Iredell</dc:creator>
		<pubDate>Fri, 25 Aug 2006 08:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-485</guid>
		<description>I think this kind of tools could achieve a great success between SL players. Please keep on with you efforts, guys, because they will pay. 

I really would be happy to help coders working on blogging-from-SL-tools (I'm totally for individual-blog-tools, not for a centralized approach) - I'm not a coder myself, but I've got basic knowledge of some blogging frameworks and I'm quite "into the blogosphere", so feel free to contact me if you need some help in testing, promoting and/or documenting your tools.

Sorry for my english, BTW :)</description>
		<content:encoded><![CDATA[<p>I think this kind of tools could achieve a great success between SL players. Please keep on with you efforts, guys, because they will pay. </p>
<p>I really would be happy to help coders working on blogging-from-SL-tools (I&#8217;m totally for individual-blog-tools, not for a centralized approach) - I&#8217;m not a coder myself, but I&#8217;ve got basic knowledge of some blogging frameworks and I&#8217;m quite &#8220;into the blogosphere&#8221;, so feel free to contact me if you need some help in testing, promoting and/or documenting your tools.</p>
<p>Sorry for my english, BTW :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chance Takashi</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-461</link>
		<dc:creator>Chance Takashi</dc:creator>
		<pubDate>Tue, 22 Aug 2006 14:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-461</guid>
		<description>I actually wrote a blog hud that had quite a few nifty features, (SLUrls not being one of them... should've thought of that), but it used the e-mail -&#62; Blogger tool which is, I find out, nearly always broken. I was too disheartened to rewrite it using the blogger API, although I'd love to be able to actually use the thing. I chose the e-mail route initially because you can fit more text into an e-mail (4k?). My HUD would listen on channel 0 only when active and only for you. Changing the channel was one of the options as was having it log all chat, add timestamps, etc. If the blog entry got too big for one e-mail, it'd chunk it into multiples and add a "part x" to the subject line.

I figured the best way to go about changing it to use the various blog APIs would be to set up an SL-&#62;Blog gateway but instead of how blogHUD sends all of its blogs to a central place, have the gateway post to individual people's blogs after reintegrating the chunked posts. But that sounded like more work than I was willing to do.

I suppose that was a long way of saying  that I can't wait until your blogging HUD is done as I'll be the first to line up to buy it!</description>
		<content:encoded><![CDATA[<p>I actually wrote a blog hud that had quite a few nifty features, (SLUrls not being one of them&#8230; should&#8217;ve thought of that), but it used the e-mail -&gt; Blogger tool which is, I find out, nearly always broken. I was too disheartened to rewrite it using the blogger API, although I&#8217;d love to be able to actually use the thing. I chose the e-mail route initially because you can fit more text into an e-mail (4k?). My HUD would listen on channel 0 only when active and only for you. Changing the channel was one of the options as was having it log all chat, add timestamps, etc. If the blog entry got too big for one e-mail, it&#8217;d chunk it into multiples and add a &#8220;part x&#8221; to the subject line.</p>
<p>I figured the best way to go about changing it to use the various blog APIs would be to set up an SL-&gt;Blog gateway but instead of how blogHUD sends all of its blogs to a central place, have the gateway post to individual people&#8217;s blogs after reintegrating the chunked posts. But that sounded like more work than I was willing to do.</p>
<p>I suppose that was a long way of saying  that I can&#8217;t wait until your blogging HUD is done as I&#8217;ll be the first to line up to buy it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Malthus</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-456</link>
		<dc:creator>Jesse Malthus</dc:creator>
		<pubDate>Mon, 21 Aug 2006 22:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-456</guid>
		<description>Ordinal,
SLStats has the power to turn your LiveBlogs (with an affixed SLURL) into posts via the metaweblog or Blogger API.</description>
		<content:encoded><![CDATA[<p>Ordinal,<br />
SLStats has the power to turn your LiveBlogs (with an affixed SLURL) into posts via the metaweblog or Blogger API.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ordinal.malaprop</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-453</link>
		<dc:creator>ordinal.malaprop</dc:creator>
		<pubDate>Mon, 21 Aug 2006 14:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-453</guid>
		<description>With the existing Slurlblogger one can just set the email address to be the one used for email posting, but unfortunately LSL will always include a three line header in the email, which would have to be removed from the post manually later. (Nothing I can do about this I'm afraid.) A more direct interface would stop that happening.</description>
		<content:encoded><![CDATA[<p>With the existing Slurlblogger one can just set the email address to be the one used for email posting, but unfortunately LSL will always include a three line header in the email, which would have to be removed from the post manually later. (Nothing I can do about this I&#8217;m afraid.) A more direct interface would stop that happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Shaftoe</title>
		<link>http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-452</link>
		<dc:creator>Nicholas Shaftoe</dc:creator>
		<pubDate>Mon, 21 Aug 2006 14:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://ordinalmalaprop.com/engine/2006/08/21/postslurlblogging/#comment-452</guid>
		<description>I would love to see this for WordPress, which seems easy since it has email posting.  Including a SLURL would be tremendous.</description>
		<content:encoded><![CDATA[<p>I would love to see this for WordPress, which seems easy since it has email posting.  Including a SLURL would be tremendous.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
