<story><title>Building Permanent and Censorship-Resistant Blog with Ethereum ENS and IPFS</title><url>https://pawelurbanek.com/ipfs-ethereum-blog</url></story><parent_chain></parent_chain><comment><author>phantom_oracle</author><text>I looked into this the last time someone posted about it here:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=27551619&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=27551619&lt;/a&gt;&lt;p&gt;One thing I realized is how expensive Ethereum domains are. The domain price is equivalent to a regular domain and then you still have to pay the gas fee, which makes it more expensive than a casual .org or .net&lt;p&gt;The other drawback of these censorship-resistant blogs is that they all require plugins to access the non-HTTP domain, which all but rules out most non-technical people who don&amp;#x27;t even know what HTTP is.&lt;p&gt;And while it can still be accessed over HTTP, the bottlenecks become the same companies that might comply with censorship requests.</text></comment>
<story><title>Building Permanent and Censorship-Resistant Blog with Ethereum ENS and IPFS</title><url>https://pawelurbanek.com/ipfs-ethereum-blog</url></story><parent_chain></parent_chain><comment><author>marcus_holmes</author><text>Nice post, thanks for making it :)&lt;p&gt;I&amp;#x27;m always curious, though - there are some things that we want to censor for good reasons. The usual poster child (sorry) for this is kiddie porn. But there&amp;#x27;s other stuff - revenge porn, libel, etc that we as a society might want to censor. How do we do this on infrastructure like IPFS?</text></comment>