Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why build this blog, or anything, on IPFS?

teetotality.blog

Post reply on HN
Print view View original

11–20 of 156 posts

Re: Why build this blog, or anything, on IPFS?

#12

Post by EGreg »

I think IPFS should be a pluggable back-end among many back-ends that become possible once we move away from the idea that websites must be hosted by a specific server / domain and start thinking in terms of “client-first” architecture.

I don’t want to write a wall of text, right now the top post on https://qbix.com/blog lays out several specific actionable things we can all do to bring about this future. It requires a snowball effect and a critical mass for any of this to take off.

Re: Why build this blog, or anything, on IPFS?

#13

Post by stanferder »

endothrowho333 wrote: post #7

It's pieces like these that remind me why good writing skills are important, and one shouldn't stray from the basics unless they're fully aware of the trade-offs. For this article, it would be: write a better hook, and make sure to include a rudimentary thesis statement, because I wasn't able to deduce what you were trying to persuade me of, within the first few paragraphs. With a title like "Why build this blog -- o…

I think bloggers deserve some leeway in how they write; it's an informal medium and maybe the author's usual audience is arriving with a lot of shared assumptions.

Still, I wish IPFS had been defined within the post. I had to look it up on Wikipedia; presumably it's "Interplanetary File System".

Re: Why build this blog, or anything, on IPFS?

#16

Post by endothrowho333 »

stanferder wrote: post #13
endothrowho333 wrote: post #7

It's pieces like these that remind me why good writing skills are important, and one shouldn't stray from the basics unless they're fully aware of the trade-offs. For this article, it would be: write a better hook, and make sure to include a rudimentary thesis statement, because I wasn't able to deduce what you were trying to persuade me of, within the first few paragraphs. With a title like "Why build this blog -- o…

I think bloggers deserve some leeway in how they write; it's an informal medium and maybe the author's usual audience is arriving with a lot of shared assumptions. Still, I wish IPFS had been defined within the post. I had to look it up on Wikipedia; presumably it's "Interplanetary File System".

Yes, it occurred to me that his audience already had a background in IPFS and I wasn't his prospective audience; yet, then why craft the title to seem like it was meant for people who have no idea what IPFS is, because surely those with prior knowledge of it, would already be able to answer for themselves "Why... IPFS?"

I think my main problem with this blog post, and many others, is that they come off too "stream of consciousness," instead of something more structured, and easily-digestable.

It's obvious the author can write[0], but at risk of being presumptuous, it seems like it was hastily written and submitted to HN for the sole purpose of generating traffic.

[0] This is a much better piece, albeit short: http://teetotality.blog/posts/think-do-build/

Re: Why build this blog, or anything, on IPFS?

#17

Post by notyourday »

endothrowho333 wrote: post #7

It's pieces like these that remind me why good writing skills are important, and one shouldn't stray from the basics unless they're fully aware of the trade-offs. For this article, it would be: write a better hook, and make sure to include a rudimentary thesis statement, because I wasn't able to deduce what you were trying to persuade me of, within the first few paragraphs. With a title like "Why build this blog -- o…

> Suffice to say, the point of this pargraph was "DNS and HTTP unrobust, webservers fail under unforseen circumstances." Ok, well how does IPFS do things differently? You never explained how IPFS works, much less how it gets over any of the aforementioned issues you outlined.

If DNS and HTTP are not working absolutely no one will care about some blog being up.

Re: Why build this blog, or anything, on IPFS?

#19

Post by slacka »

endothrowho333 wrote: post #14
netfl0 wrote: post #11

This blog is “built” on cloudflare apparently. Why is medium being compared to IPFS???

>This blog is “built” on cloudflare apparently. You can read more about why that is here: http://teetotality.blog/posts/how-this-blog-was-made/

I found that too as the article linked raised more questions that it answered. I was like "how can I be reading this if it's not using DNS?" And from the link this explanation:

> It updates a dnslink pointer at Cloudflare, which allows Cloudflare's DNS to direct teetotality.blog HTTP traffic to the correct IPFS hash address via their IPFS Gateway. So even though you've (probably) reached this page through a regular old HTTP link that uses the teetotality.blog host name, there is in fact no server with that name - the content is stored on various IPFS nodes, including but not limited to Cloudflare's edge caches.

Re: Why build this blog, or anything, on IPFS?

#20

Post by azangru »

meerita wrote: post #15

I have my own blog on DigitalOcean using Jekyll. Can't be more easy to do and mantain.

> Can't be more easy to do and mantain.

Sure it can.

- Github pages

- Netlify

- Zeit

All free for static sites; all easy to set up a continuous deployment pipeline for.

Post reply on HN