<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>At least 2 years in the making since first public commit and 483 open issues. The project has definitely moved past the technology triggers stage and has done well moving in to the peak of inflated expectations by garnering a NYT article. How it will survive
through its <a href="https://en.wikipedia.org/wiki/Hype_cycle" class="x_OWAAutoLink" id="LPlnk799168" title="https://en.wikipedia.org/wiki/Hype_cycle
Ctrl+Click or tap to follow the link">https://en.wikipedia.org/wiki/Hype_cycle</a> will be interesting to
watch.</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> kf4hcw <kf4hcw@lifeatwarp9.com><br>
<b>Sent:</b> Thursday, June 9, 2016 11:48:49 PM<br>
<b>To:</b> Ethan Waldo; tacos@amrad.org<br>
<b>Subject:</b> Re: Re-inventing the web</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 06/09/2016 10:58 PM, Ethan Waldo wrote:<br>
> I was rolling my eyes until<br>
<br>
It still has a long way to go I think, but it is picking up steam and <br>
it's solid enough right now for a lot of experimentation... maybe just <br>
shy of production _IF_ you can implement what you want with what is <br>
already baked in.<br>
<br>
The biggest problems I see with it at the moment is that there's no good <br>
ways to deal with:<br>
<br>
* Dynamic data and/or revocation. (It's technically possible with IPNS, <br>
but not nearly good enough yet)<br>
<br>
* Search. There simply is no mechanism searching IPFS for content right <br>
now. I remember the days before search engines. Search engines are _the <br>
killer app_ for the web ... be it old broken joint http or new IPFS hotness.<br>
<br>
I'm sure these things are coming ... there are a lot of folks out there <br>
who _REALLY_ want this to work for lots of good reasons.<br>
<br>
_M<br>
<br>
-- <br>
kf4hcw<br>
Pete McNeil<br>
lifeatwarp9.com/kf4hcw<br>
<br>
</div>
</span></font>
</body>
</html>