-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Article on uploading your user interface to IPFS #12984
base: dev
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @qbzzt! Thanks for this. Commented with a few suggestions and questions, lemme know what you think
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
|
||
## Conclusion {#conclusion} | ||
|
||
You cannot reliably delete IPFS files, so as long as you're modifying your user interface, it is probably best to leave it centralized. However, once you've stabilized it, it seems like it would be an excellent idea to release it on IPFS so that portion of your dapp can also be decentralized and censorship resistant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be worth mentioning IPNS here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would also consider changing the topic (first) sentence here for the "Conclusion" section... it currently starts by adding an entirely new point that has not been brought up yet, when I would have expected summary of the points so far.
Maybe a new section on "Drawbacks" or "When to use?" before the conclusion?
On a similar note, there are some challenges that can arise by using IPFS to serve some sites (ie, ethereum.org struggles with this since it has many package dependencies, and some have led to roadblocks on our own ability to implement on IPFS, though I'll admit we've typically tried using services such as Fleek). Any thoughts on adding a bit of content related to this topic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What packages? I'd happily add more details, but I need to know them first. Otherwise, I'll just write "IPFS can be forever" as the heading.
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
public/content/developers/tutorials/ispf-decentralized-ui/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Description
This tutorial teaches the reader how to use IPFS to store the user interface for a dapp. Although the application's data and business logic are decentralized, without a censorship resistant user interface users might lose access to it anyway.
Related Issue