-
Notifications
You must be signed in to change notification settings - Fork 48
Static Web Publishing with IPFS - Simpler and Decentralized #31
Conversation
src/10-ipscend-update/index.md
Outdated
# Users friendly | ||
|
||
- [ ] explain naming problem | ||
- [ ] explain how IPFS public gateways can be the proxies for users seemlessly (with graphs!) |
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.
we could reference the firefox addon 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.
Doesn't it have a different purpose? Here would be explaining how we can get DNS names to load IPFS hashes through using IPFS public gateways as a proxy
Ping me before merging. I'm going to comb over this again when ya'll are done. |
e2a8643
to
876de2e
Compare
> - Don't you hate it when people relying on your content get broken embeds? | ||
|
||
> NOTE: I think it'd be better to start stronger than rhetorical questions. For instance: | ||
> The web is broken. Links break; webhosts get attacked, and websites go down (often permanently). As a web developer, you have to by a sysadmin just to host a webpage. If you switch cloud providers, links break. Even with a fully functional website, more issues might pop up; link rot, or broken embeds for third parties serving your content. It's 2016, and not all is as it should be. |
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.
We're going to have to go with one of these, or the other. The questions, or the paragraph.
051f0c5
to
c163ba0
Compare
|
||
Version Control Systems have enabled developers to work collaboratively on the same code, without wasting time dealing with merge conflicts. We can improve these tools by letting developers, designers and other individuals have more power. Ultimately, they should be able to have quick access to the timeline for their application, to make annotations on the current iterations before a release, to cherry pick which version to be released (using visual rollbacks), to analyze if there have been any regressions in a specific browser, among other things. | ||
|
||
Currently we have a `timeline` feature that lets you browse through screenshots of all of the published versions of your application. |
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.
Needs to be fleshed out.
The piece is a bit loose at the beginning, very casual during the steps, and then really dense at the end. Would be good to tighten up the beginning a bit so that users don't get jarred towards the end. Also, add some sign posting at the beginning, saying what we are going to do and what we will talk about at the end, too. Otherwise, people will just think it is a tutorial, and not also an exposé of future plans. |
> - Don't you hate it when people relying on your content get broken embeds? | ||
|
||
> NOTE: I think it'd be better to start stronger than rhetorical questions. For instance: | ||
> The web is broken. Links break; web hosts get attacked, and websites go down (often permanently). As a web developer, you have to by a sysadmin just to host a web page. If you switch cloud providers, links break. Even with a fully functional website, more issues might pop up; link rot, or broken embeds for third parties serving your content. It's 2016, and not all is as it should be. |
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.
"have to be a sysadmin"
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.
"If you switch cloud providers, links often break." (add "often")
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.
Good catch. Should we keep this paragraph?
|
I updated the post. It still needs some images. And i need to improve the top image. (make it from teh proper stock photo). |
From here out, let's just stick with this, no major wording changes. we still need to:
@RichardLitt if you could help with some, A+. |
- (cloud service) [Protocol Labs](http://ipn.io) is creating a cloud service on top of existing cloud providers. Stay tuned for more news on this. | ||
- (incentivized protocols) [Protocol Labs](http://ipn.io) is also creating [Filecoin](http://filecoin.io), a cryptocurrency incentivized storage network on top of IPFS. This will be the best way to pin long-term. If you're interested in building Filecoin with Protocol Labs, [reach out](http://ipn.io/join). | ||
|
||
|
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.
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉
453b50e
to
637f458
Compare
637f458
to
f5616fd
Compare
To do:
|
I was unable to do the following: |
Waiting on designs. Review once designs have been had. |
|
Closing ancient posts that never got posted. |
No description provided.