Original Writing
When I first saw people using .eth in their nicknames on Twitter, I wondered, it looks like a domain name, so can I have a website running on it?
Then I started a little research, and it turned out, yes, I can have a website on the .eth domain. They have a standard called EIP 1577, which makes it possible to set a content source for a domain.
But it is different from A records for traditional DNS. With traditional DNS, A record set on a domain tells the user which server is responsible for serving the content. With ENS' EIP 1577, two supported content sources are IPFS and Swarm, and both are decentralized storage technologies.
I have played with IPFS before. First, you download and install a program on your computer. Then you can use it to add and publish files to the IPFS peer-to-peer network. Publishing here does not mean uploading your files to the cloud. Instead, the program adds your files to its local repository and assigns a unique content ID to each file. Then, if someone else needs to download a file, they can request the content ID, and the IPFS network has a mechanism to locate it from the network.
But if you google how to publish a website on IPFS, you will most likely see a page full of commands to be typed in a Terminal, which could be too hard for many users.
So I was thinking, what if I can create a native macOS app to make those things easier? First, it should have a three-column UI like the Mail app, great for following and reading many different websites.
When writing, it should have a two-column Markdown editor, loved by many, including me. With an easy way to attach video and audio.
And this app can generate and host websites with a local IPFS node. So users can use their Mac as servers, and third-party services or cloud are optional.
Websites hosted with IPFS can be set as the content source for ENS domains. Since IPFS and ENS are not controlled by any corporate, your content is controlled by your private keys. It is a fully decentralized way to publish your writings on the Internet.
Rewrote by Mia
When I first saw people using .eth in their Twitter nicknames, I wondered, since it looked like a domain name, would I be able to have a website running on it?
Then I started a little bit of research, and it turned out, yes, I can have a website on the .eth domain. The Ethereum community has a standard called EIP 1577, which makes it possible to set a content source for a domain.
However, it is different from A records for traditional DNS. With traditional DNS, A record set on a domain tells the user which server is responsible for serving the content. With ENS' EIP 1577, two supported content sources are IPFS and Swarm, and both are decentralized storage technologies.
I have played with IPFS before. First, you download and install a program on your computer. Then you can utilize it to add and publish files to the IPFS peer-to-peer network. Publishing here does not mean uploading your files to the cloud; instead, the program adds your files to its local repository and assigns a unique content ID to each file. Then, if someone else needs to download a file, they can request the content ID, and the IPFS network can locate it from the network.
But if you google how to publish a website on IPFS, you will most likely see a page full of commands to be typed in a Terminal, which could be too complex and problematic for many users.
So I was thinking, what if I can create a native macOS app to make those things easier? First, it should have a three-column UI like the Mail app, great for following and reading many different websites.
When writing, it should have a two-column Markdown editor, loved by many, including me. With an easy way to attach video and audio.
Furthermore, this app can generate and host websites with a local IPFS node so that users can use the Mac as server.
Websites hosted with IPFS can be set as the content source for ENS domains. Since IPFS and ENS are not entirely controlled by any corporate, your content is controlled by your private keys. It is a fully decentralized way to publish your writings on the Internet.
AI Version 1
Hello and welcome to the first episode of the Planetable podcast.
In this episode, we will be discussing the use of the .eth domain and how it can be used to host a website. The Ethereum community has a standard called EIP 1577, which allows users to set a content source for a domain. Unlike traditional DNS, where A records are used to specify the server responsible for serving the content, EIP 1577 supports the use of decentralized storage technologies like IPFS and Swarm.
Publishing a website on IPFS can be done by downloading and installing a program on your computer. The program is used to add and publish files to the IPFS peer-to-peer network. Instead of uploading files to the cloud, the program adds the files to its local repository and assigns a unique content ID to each file. When someone needs to download a file, they can request the content ID and the IPFS client will locate it from the network.
However, many users may find the process of publishing a website on IPFS to be too complex and difficult, as it involves using a Terminal and typing out commands. This is where a native macOS app could be useful. The app could have a three-column UI similar to the Mail app, making it easy to follow and read multiple websites. It could also have a two-column Markdown editor for writing and previewing side by side, with an easy way to attach video and audio.
The app could also generate and host websites using a local IPFS node, allowing users to use their Mac as a server. Websites hosted with IPFS can be set as the content source for ENS domains. Since IPFS and ENS are not controlled by any single entity, the user's content is controlled by their private keys. This offers a fully decentralized way to publish content on the internet.