<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>marssaxman</author><text>Much value is created by people who don&amp;#x27;t want to be bothered with payment because they are motivated by the social capital accruing from contribution to a community. Trying to pay for such gifts actually drives these contributors away, by devaluing their efforts - as though they were only doing it for the money. There is labor you literally cannot buy.</text><parent_chain><item><author>stuartaxelowen</author><text>Core problem is that creators of value want to be paid for it.  The delivery medium doesn&amp;#x27;t change that.</text></item><item><author>davb</author><text>I&amp;#x27;d love to go back to the days where I didn&amp;#x27;t have to endure the 20+ external scripts (mostly ads, analytics, social and &amp;quot;optimization&amp;quot;) that some crappy dev has crammed into their markup, just to read an article or browse a store.&lt;p&gt;Maybe we need a content oriented alternative to the web browser.&lt;p&gt;Maybe a modern Gopher.&lt;p&gt;Display preferences are handled by the client. Sure, support video and audio. Support tables. But keep it minimal. Put all the scripting on the server side, as it should be. Lock down the specification - do everything to stop it becoming web browser 2.0.&lt;p&gt;Then we wouldn&amp;#x27;t need junk like AMP.&lt;p&gt;Maybe it would take off well in some nice to start with.</text></item></parent_chain></comment><story><title>After fifteen years of downtime, the MetaFilter gopher server is back</title><url>http://metatalk.metafilter.com/24019/Direct-your-gopher-client-to-gopher-gophermetafiltercom?utm_content=bufferaa556&amp;utm_medium=social&amp;utm_source=facebook.com&amp;utm_campaign=buffer</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>themodelplumber</author><text>&amp;gt; Core problem is that&lt;p&gt;[some]&lt;p&gt;&amp;gt; creators of value want to be paid for it.&lt;p&gt;The WWW has been a proof of concept of how much people will do _without_ direct monetary compensation. If you&amp;#x27;re thinking who&amp;#x27;s going to build Kayak on a glorified Gopher though, maybe you should start by asking where audiences will go when they find something that provides a better experience than Chrome.</text><parent_chain><item><author>stuartaxelowen</author><text>Core problem is that creators of value want to be paid for it.  The delivery medium doesn&amp;#x27;t change that.</text></item><item><author>davb</author><text>I&amp;#x27;d love to go back to the days where I didn&amp;#x27;t have to endure the 20+ external scripts (mostly ads, analytics, social and &amp;quot;optimization&amp;quot;) that some crappy dev has crammed into their markup, just to read an article or browse a store.&lt;p&gt;Maybe we need a content oriented alternative to the web browser.&lt;p&gt;Maybe a modern Gopher.&lt;p&gt;Display preferences are handled by the client. Sure, support video and audio. Support tables. But keep it minimal. Put all the scripting on the server side, as it should be. Lock down the specification - do everything to stop it becoming web browser 2.0.&lt;p&gt;Then we wouldn&amp;#x27;t need junk like AMP.&lt;p&gt;Maybe it would take off well in some nice to start with.</text></item></parent_chain></comment><story><title>After fifteen years of downtime, the MetaFilter gopher server is back</title><url>http://metatalk.metafilter.com/24019/Direct-your-gopher-client-to-gopher-gophermetafiltercom?utm_content=bufferaa556&amp;utm_medium=social&amp;utm_source=facebook.com&amp;utm_campaign=buffer</url></story>