<?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: The Internet, now with more noise</title>
	<atom:link href="http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/</link>
	<description>Thoughts on small business, the web industry and more, from Miles Burke, Author, Speaker, Entrepreneur &#38; Geek.</description>
	<pubDate>Tue, 06 Jan 2009 23:38:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Nathanael</title>
		<link>http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/#comment-25399</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Sun, 05 Nov 2006 02:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=108#comment-25399</guid>
		<description>Well we already have the XFN thing happening; why can't we just hook into that? And you can specify how far out you want relationships to be classified as "trusted" - so perhaps 4 levels: friends of friends of friends of friends of Miles can post or send emails. Once we get good XFN-like networks happening then these relationships will be exhaustively configured - so you can just say "Web developers" are "trusted" and that could include 2 million people; so you specify the branch you want to categorise and then everyone linked to that is included in that classification ??</description>
		<content:encoded><![CDATA[<p>Well we already have the XFN thing happening; why can&#8217;t we just hook into that? And you can specify how far out you want relationships to be classified as &#8220;trusted&#8221; - so perhaps 4 levels: friends of friends of friends of friends of Miles can post or send emails. Once we get good XFN-like networks happening then these relationships will be exhaustively configured - so you can just say &#8220;Web developers&#8221; are &#8220;trusted&#8221; and that could include 2 million people; so you specify the branch you want to categorise and then everyone linked to that is included in that classification ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Royce Townsend</title>
		<link>http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/#comment-24574</link>
		<dc:creator>Royce Townsend</dc:creator>
		<pubDate>Fri, 03 Nov 2006 07:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=108#comment-24574</guid>
		<description>I was thinking about what Nathanael said, and it's a great idea. Everyone is registered (just once) with a trusted 'place where you register'... sounds great.

But who do you trust? (Maybe the government... but what about other governments?) Does it cost money to register. If it costs money can you convince everyone to do it. (And use the same protocol??).

Before I read Nathanael's comments I was thinking of a trust network. I trust Miles, Miles trusts someone else etc. But that probably just too hard.

Sigh</description>
		<content:encoded><![CDATA[<p>I was thinking about what Nathanael said, and it&#8217;s a great idea. Everyone is registered (just once) with a trusted &#8216;place where you register&#8217;&#8230; sounds great.</p>
<p>But who do you trust? (Maybe the government&#8230; but what about other governments?) Does it cost money to register. If it costs money can you convince everyone to do it. (And use the same protocol??).</p>
<p>Before I read Nathanael&#8217;s comments I was thinking of a trust network. I trust Miles, Miles trusts someone else etc. But that probably just too hard.</p>
<p>Sigh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/#comment-23967</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Thu, 02 Nov 2006 06:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=108#comment-23967</guid>
		<description>Miles - I'd really like to see some research in the area I briefly mentioned in my WD06 wrap-up post (http://www.purecaffeine.com/2006/09/web-directions-is-over) which hopefully I might expand on if I get time to look into the feasibility a bit more;

Basically the idea is that in Email 2.0 there won't be such a thing as anonymous emails or email addresses using nicknames or whatever. In fact, there won't be email addresses - you can send an email to a person or a legally registered entity such as a company - but not to an email address. There'll be physical authentication protocols in place and the addressing will take place in the background.

So instead of writing to blahblah@blahblah.com, you will write to Miles Burke, with whatever extra bits are needed to narrow it down to the correct person. And that email will need to come from a person, ie Nathanael Boehm, not an email address.

If this were possible, then it would eliminate comment spam and email spam, except where you invite users to comment anonymously through a web form. Otherwise your comments and email will be tied directly to your identity.</description>
		<content:encoded><![CDATA[<p>Miles - I&#8217;d really like to see some research in the area I briefly mentioned in my WD06 wrap-up post (http://www.purecaffeine.com/2006/09/web-directions-is-over) which hopefully I might expand on if I get time to look into the feasibility a bit more;</p>
<p>Basically the idea is that in Email 2.0 there won&#8217;t be such a thing as anonymous emails or email addresses using nicknames or whatever. In fact, there won&#8217;t be email addresses - you can send an email to a person or a legally registered entity such as a company - but not to an email address. There&#8217;ll be physical authentication protocols in place and the addressing will take place in the background.</p>
<p>So instead of writing to <a href="mailto:blahblah@blahblah.com">blahblah@blahblah.com</a>, you will write to Miles Burke, with whatever extra bits are needed to narrow it down to the correct person. And that email will need to come from a person, ie Nathanael Boehm, not an email address.</p>
<p>If this were possible, then it would eliminate comment spam and email spam, except where you invite users to comment anonymously through a web form. Otherwise your comments and email will be tied directly to your identity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tuna</title>
		<link>http://www.milesburke.com.au/blog/2006/11/02/the-internet-now-with-more-noise/#comment-23953</link>
		<dc:creator>Tuna</dc:creator>
		<pubDate>Thu, 02 Nov 2006 05:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=108#comment-23953</guid>
		<description>Miles your just too popular.. But what do we replace email, page searching or blog comments etc with.. whats the solution.  Point to Point message / information certified validation?</description>
		<content:encoded><![CDATA[<p>Miles your just too popular.. But what do we replace email, page searching or blog comments etc with.. whats the solution.  Point to Point message / information certified validation?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
