<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: When re-purposing email is difficult</title>
	<link>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/</link>
	<description>sharing ideas thoughts and feedback</description>
	<pubDate>Thu, 10 Dec 2009 12:18:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Johnt</title>
		<link>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32489</link>
		<pubDate>Sun, 18 May 2008 02:30:20 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32489</guid>
					<description>I suppose a podcast is an example of an RSS with attachments (enclosure), but the attachment lives at a URL.

I like your point about RSS is an enabler of distribution, whereas email can control distribution...basically the pull (RSS) vs push (email) model.

Like you say email could be mostly used for notifications, or an RSS Reader.

At my work I'm a member of numerous communities, and it's great that all announcements (blog/comments), discussion (forum/replies), collaboration (wiki/comments) are done in the open archive...rather than using email.

I basically get lots of notifications and I can also action them via email without having to visit the communities.
I could get these notifications in an RSS Reader, but just the same I'd like to action them within the RSS Reader.

Fuser is a consumer product that plans to be a universal inbox and send box.

Like Luis the only type of email I hope to get is one-to-one discussion, this only happens because we yet don't have private messaging in each of our communities.

In the future I see myself having a private inbox for each community, with my email inbox being the notifier (well it actually delivers the content and I can action back).

The good thing here is that all my private messages about KM would live in the KM CoP, all my private messages about DMS would live in the DMS CoP, and so on.

This would be ideal, rather than like now, where all my private messages about any CoP are only in my email inbox. I'd rather the messages be kept in context. 
If I want to check back on some KM private messages, I don't want to hack through my email inbox, where they are mixed up with emails from all different topics. I'd rather just go to my KM CoP to find them.
Or I could search all my CoP inboxes from a dashboard.

I also like the idea of the public comment wall. If I want to send a friend a link, I'd send it to their wall (perhaps others may like to see this as well...they'd see it in their newsfeed as well).

Let's not forget the 3rd alternative to email and an RSS Reader is a watchlist newsfeed type page.

</description>
		<content:encoded><![CDATA[	<p>I suppose a podcast is an example of an RSS with attachments (enclosure), but the attachment lives at a URL.</p>
	<p>I like your point about RSS is an enabler of distribution, whereas email can control distribution&#8230;basically the pull (RSS) vs push (email) model.</p>
	<p>Like you say email could be mostly used for notifications, or an RSS Reader.</p>
	<p>At my work I&#8217;m a member of numerous communities, and it&#8217;s great that all announcements (blog/comments), discussion (forum/replies), collaboration (wiki/comments) are done in the open archive&#8230;rather than using email.</p>
	<p>I basically get lots of notifications and I can also action them via email without having to visit the communities.<br />
I could get these notifications in an RSS Reader, but just the same I&#8217;d like to action them within the RSS Reader.</p>
	<p>Fuser is a consumer product that plans to be a universal inbox and send box.</p>
	<p>Like Luis the only type of email I hope to get is one-to-one discussion, this only happens because we yet don&#8217;t have private messaging in each of our communities.</p>
	<p>In the future I see myself having a private inbox for each community, with my email inbox being the notifier (well it actually delivers the content and I can action back).</p>
	<p>The good thing here is that all my private messages about KM would live in the KM CoP, all my private messages about DMS would live in the DMS CoP, and so on.</p>
	<p>This would be ideal, rather than like now, where all my private messages about any CoP are only in my email inbox. I&#8217;d rather the messages be kept in context.<br />
If I want to check back on some KM private messages, I don&#8217;t want to hack through my email inbox, where they are mixed up with emails from all different topics. I&#8217;d rather just go to my KM CoP to find them.<br />
Or I could search all my CoP inboxes from a dashboard.</p>
	<p>I also like the idea of the public comment wall. If I want to send a friend a link, I&#8217;d send it to their wall (perhaps others may like to see this as well&#8230;they&#8217;d see it in their newsfeed as well).</p>
	<p>Let&#8217;s not forget the 3rd alternative to email and an RSS Reader is a watchlist newsfeed type page.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Doug Cornelius</title>
		<link>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32488</link>
		<pubDate>Sat, 17 May 2008 04:42:46 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32488</guid>
					<description>Of course, RSS is better.  Essentially, it is email without attachments and with the content stored in a central place.

With email you control the distribution. With RSS you just enable distribution.</description>
		<content:encoded><![CDATA[	<p>Of course, RSS is better.  Essentially, it is email without attachments and with the content stored in a central place.</p>
	<p>With email you control the distribution. With RSS you just enable distribution.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Johnt</title>
		<link>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32487</link>
		<pubDate>Sat, 17 May 2008 02:35:34 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32487</guid>
					<description>Hi Doug,

Great point in trying to avoid emails being a CMS.

It seems you don't mind email being your notifier dashboard, another choice is an RSS Reader.

I mention a few other notifier streams in an earlier post

- On to others
- On to me
- Me to others

http://libraryclips.blogsome.com/2008/04/10/email-is-not-the-centre-of-my-universe/</description>
		<content:encoded><![CDATA[	<p>Hi Doug,</p>
	<p>Great point in trying to avoid emails being a CMS.</p>
	<p>It seems you don&#8217;t mind email being your notifier dashboard, another choice is an RSS Reader.</p>
	<p>I mention a few other notifier streams in an earlier post</p>
	<p>- On to others<br />
- On to me<br />
- Me to others</p>
	<p><a href='http://libraryclips.blogsome.com/2008/04/10/email-is-not-the-centre-of-my-universe/' rel='nofollow'>http://libraryclips.blogsome.com/2008/04/10/email-is-not-the-centre-of-my-universe/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Doug Cornelius</title>
		<link>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32486</link>
		<pubDate>Fri, 16 May 2008 15:53:03 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/05/16/when-re-purposing-email-is-difficult/#comment-32486</guid>
					<description>Email is a good tool for messaging and notifying people.  The problem is that email has turned into a content storage system.

I would be happy to get hundreds of email each day, notifying me of new information.  I do not want to have to store the emails because the important information lives solely in the email.
</description>
		<content:encoded><![CDATA[	<p>Email is a good tool for messaging and notifying people.  The problem is that email has turned into a content storage system.</p>
	<p>I would be happy to get hundreds of email each day, notifying me of new information.  I do not want to have to store the emails because the important information lives solely in the email.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
