I looked into this the last time someone posted about it here:<p><a href="https://news.ycombinator.com/item?id=27551619" rel="nofollow">https://news.ycombinator.com/item?id=27551619</a><p>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<p>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't even know what HTTP is.<p>And while it can still be accessed over HTTP, the bottlenecks become the same companies that might comply with censorship requests.
Nice post.<p>For permanent storage you should check out <a href="https://www.arweave.org/" rel="nofollow">https://www.arweave.org/</a> rather than IPFS + centralised pinning services like Pinata. With Arweave you pay a small upfront fee to have the network store your file forever.<p>It's the promise of IPFS+Filecoin but actually live and being used (eg by the Internet Archive). There's some decent tooling & docs for it too: <a href="https://github.com/ArweaveTeam/arweave-deploy" rel="nofollow">https://github.com/ArweaveTeam/arweave-deploy</a><p>Edit: Filecoin is also live and being used, I was out of date. <a href="https://docs.filecoin.io/store/" rel="nofollow">https://docs.filecoin.io/store/</a>
Nice post, thanks for making it :)<p>I'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'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?
I would rather be interested in a database system over IPFS or similar where you can update data, with both public and private encrypted data. Freenet is good, but it's not a database system, and it's pretty complex.<p>Bitmessage is also pretty awesome already...
Anyone know of any commenting systems that work on IPFS? In theory how would this work? Could there be some distributed application that stores individual comments on ipfs and serves as some type of routing mechanism or lambda function to aggregate comments into a master thread which can be continuously updated as a static files stored on ipfs?
The most censorship resistent blog is one that doesn't use any resources owned by a third party. Unless you're rich that generally means hosting from your home computer.<p>It's simple, It's effective (for most non "web scale"/commercial use cases), and it's legally safe.
I did something similar using <a href="https://fleek.co/" rel="nofollow">https://fleek.co/</a> using a nuxtjs template I edited in my GitHub repository: <a href="https://github.com/klaudioz/klaudioz.eth" rel="nofollow">https://github.com/klaudioz/klaudioz.eth</a><p>It was very easy to set. No code. My site is: <a href="https://klaudioz.eth.link/" rel="nofollow">https://klaudioz.eth.link/</a><p>Also i bought the eth domain when the gas was a very low price.
We need an open standard for blogs, like email or news servers. Everyone publishes on their own server of choice and it gets fully replicated through API from server to server -- who ever subscribe to whom.<p>Banned from a server? Post on another one or your own server from where subscribers will pull your posts. Digital signatures for validation.<p>Publishing the specs will suffice. As developers can come up with various implementations based on it.
It would be much better to store the blog content directly on the blockchain. This is very expensive to do on Ethereum, but should hopefully get cheaper over time.<p>Is IPFS really resistant to censorship? It seems like any state-based actor could easily block access to IPFS nodes if they were serving a specific CID.
You have to renew .eth domains yearly and they are a ripoff... IPFS is about as permanent as a .torrent file imho until proven otherwise. Like if you really wanted to accomplish this in the blockchain, everything's there for you without using some DNS abstraction (use a smart contract address, it won't change or expire) and without using IPFS, you can store on the blockchain. IPFS and ENS aren't necessary, and could be fads.
> On Firefox and Chrome, you can add support for eth domains via a Metamask extension<p>This has never worked for me<p>Is there supposed to be some advanced setting not on by default in Metamask that allows .eth domains to resolve?
People have been adding censorship-resistant data to the Bitcoin blockchain too.<p><a href="https://internetofbusiness.com/bitcoin-blockchain-contains-illegal-porn-say-researchers/" rel="nofollow">https://internetofbusiness.com/bitcoin-blockchain-contains-i...</a>