Skip to content
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.

Static Web Publishing with IPFS - Simpler and Decentralized #31

Closed
wants to merge 16 commits into from

Conversation

daviddias
Copy link
Contributor

No description provided.

# Users friendly

- [ ] explain naming problem
- [ ] explain how IPFS public gateways can be the proxies for users seemlessly (with graphs!)
Copy link

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

Copy link
Contributor Author

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

@RichardLitt
Copy link
Contributor

Ping me before merging. I'm going to comb over this again when ya'll are done.

> - 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.
Copy link
Contributor

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.


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.
Copy link
Contributor

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.

@RichardLitt
Copy link
Contributor

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.
Copy link
Contributor

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"

Copy link
Contributor

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")

Copy link
Contributor

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?

@daviddias
Copy link
Contributor Author

  • {from @jbenet} we need a part for ​_updating_​ the site. which works, given we use dnslink. we can do it in a "next steps" section. and reference ipns

@jbenet
Copy link
Contributor

jbenet commented Feb 24, 2016

I updated the post. It still needs some images. And i need to improve the top image. (make it from teh proper stock photo).

@jbenet
Copy link
Contributor

jbenet commented Feb 24, 2016

From here out, let's just stick with this, no major wording changes. we still need to:

  • do one more pass
    • correct typos
    • correct grammar
    • make sure all the commands work exactly right.
  • make proper topbar image
  • add other images:
    • an image for links broken (intro)
    • an image for DNS naming
    • an image for pinning
    • an image for successful web publishing
  • download all images and host them in this repo

@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).


Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉

@jbenet jbenet force-pushed the post/ipscend-update branch from 453b50e to 637f458 Compare February 24, 2016 11:32
@jbenet jbenet force-pushed the post/ipscend-update branch from 637f458 to f5616fd Compare February 24, 2016 11:33
@RichardLitt
Copy link
Contributor

To do:

  • @RichardLitt overview again
  • Pin cat image on both networks
  • @whyrusleeping: "we advise the user to try out node-static to preview their webpage on port 8080. But if they followed the instructions correctly, they have an ipfs node running a gateway there." Fix.

@RichardLitt
Copy link
Contributor

I was unable to do the following: ipfs get -o website/cat.jpg /ipfs/QmZVLbEzkoZBMMzBsLfY4d86NFMXo1yBBhsqucd7w7VnGV/cat.jpg. No one responded on IRC, so I am stopping going through the tutorial at the moment. No idea why get fails. Using the online gateway worked fine.

@RichardLitt RichardLitt changed the title WIP WIPL "Static Web Publishing with IPFS - Simpler and Decentralized" Mar 8, 2016
@RichardLitt RichardLitt added the WIP label May 9, 2016
@RichardLitt RichardLitt changed the title WIPL "Static Web Publishing with IPFS - Simpler and Decentralized" Static Web Publishing with IPFS - Simpler and Decentralized May 9, 2016
@RichardLitt
Copy link
Contributor

Waiting on designs. Review once designs have been had.

@Kubuxu
Copy link
Contributor

Kubuxu commented Jul 29, 2016

ipscend needs to be fixed before this can be released.

@daviddias
Copy link
Contributor Author

Closing ancient posts that never got posted.

@daviddias daviddias closed this Jul 27, 2018
@ghost ghost removed the stage: writing label Jul 27, 2018
@daviddias daviddias deleted the post/ipscend-update branch July 27, 2018 13:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants