Why build this blog, or anything, on IPFS? • Hacker News Board

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

#91

Post by NortySpock » Mon, Jan 20, 2020, 1:18 AM UTC

kalmi10 wrote: post #30

The thing I worry about with IPFS is privacy. If you use IPFS directly (as intended, not via a public gateway), and you visit a site, then you are automatically going to be seeding (like a torrent) the visited content, and thus you will be announcing/broadcasting the fact to the world that you (your node/your IP) have visited it. My current understanding is that this cannot really be avoided, since one needs to be ab…

Maybe a software delay where it only starts seeding 5 minutes later, or an opt-out button where you can avoid re-seeding if you don't like what you see.

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

#92

Post by zelly » Mon, Jan 20, 2020, 1:28 AM UTC

kalmi10 wrote: post #30

The thing I worry about with IPFS is privacy. If you use IPFS directly (as intended, not via a public gateway), and you visit a site, then you are automatically going to be seeding (like a torrent) the visited content, and thus you will be announcing/broadcasting the fact to the world that you (your node/your IP) have visited it. My current understanding is that this cannot really be avoided, since one needs to be ab…

IPFS really needs onion routing built-in. When I was reading this, I thought about running an IPFS node on my desktop but remembered it doesn't have onion routing built-in. So I'd have to run a proxy like torsocks and torify the IPFS server. Then I have to worry about all the ways that IP can leak from this. Then I have to figure out how to connect to other IPFS nodes through TOR. So forget it, I'll do it when I have time, which is the same thing I said the last time I thought about running an IPFS node.

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

#93

Post by jabedude » Mon, Jan 20, 2020, 1:39 AM UTC

iampims wrote: post #24

rohan1024 wrote: post #3

> even go super old-school and run a web server at home. It's not as if we're short on options in 2020. Though it's old school, it's incredibly difficult to run server at home now at least in India. The network I connect to is behind a NAT which is behind another NAT. At least that's what I saw when I tried to host my blog on Raspberry PI at home over a year ago. Ultimately I gave up on that endeavor. If anyone has s…

You can always use https://ngrok.com and other similar "tunneling" solutions. It works like a charm: https://ngrok.com https://github.com/cloudflare/cloudflared https://github.com/inlets/inlets

Thank you for all of these links. This is the first time I've heard of any of them. I especially like the inlets project.

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

#94

Post by zelly » Mon, Jan 20, 2020, 1:40 AM UTC

tetrisgm wrote: post #41

Disclaimer: I run the unofficial IPFS Discord and Matrix (found at https://permaweb.io/discord and /matrix) and have helped organize IPFS Meetups in SF. We also run an IPFS gateway and have built a groups app on top of IPFS and Textile. I generally agree with the conclusion, but there's a few downsides that aren't conveyed here. Let's look at the proposed upsides: 1) Ownership, control, censorship: That's partly corr…

> IPFS doesn't encrypt the content, or the connectivity, or hide the hosts. Solutions exist around that, but they're niche, and honestly I question the motives besides just ideology.

I question the motives of people who would be against encryption, aside from it being a lot of work and just not having been done yet. Ideally: no one should know the true IPs of their peers, and no one snooping on the connection should be able to read anything useful. Even the contents of the files should be encrypted, but I struggle to see how that could be easily implemented (maybe like Mega.NZ does where the key is part of the URL).

Otherwise it's going to be very hard to convince me to host arbitrary content from untrusted strangers. It's just pragmatic. No encryption = no plausible deniability.

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

#95

Post by zelly » Mon, Jan 20, 2020, 1:42 AM UTC

buboard wrote: post #21

Wordpress is unlike github pages or medium. In theory a LAMP server could run on everyone's home router, and they 'd publish their blog there. With commercial interest , network configurations would change to accomodate that, and people wouldn't lose their content when any service decides to shutdown. It's scary how much of the web is being lost , i would wager most links to nonocorporate sites > 10 years old barely…

I dream of the day when home routers have IPFS installed.

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

#96

Post by buboard » Mon, Jan 20, 2020, 1:50 AM UTC

zelly wrote: post #95

buboard wrote: post #21

Wordpress is unlike github pages or medium. In theory a LAMP server could run on everyone's home router, and they 'd publish their blog there. With commercial interest , network configurations would change to accomodate that, and people wouldn't lose their content when any service decides to shutdown. It's scary how much of the web is being lost , i would wager most links to nonocorporate sites > 10 years old barely…

I dream of the day when home routers have IPFS installed.

or webtorrent.

but even a personal publishing server would also be great to keep people's data being controlled by megacorps

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

#97

Post by [deleted] » Mon, Jan 20, 2020, 1:54 AM UTC

woodandsteel wrote: post #73

momack2 wrote: post #50

Earlier quoted context omitted.

Hey IPFS person here. We actually made a change to ipfs-desktop back in Feb of last year to reduce the default connection limit to ~300 ( https://github.com/ipfs-shipyard/ipfs-desktop/pull/828 ), and also to set desktop nodes into DHT-client mode (so they don't get lots of requests from other nodes for where to find content). If you've been running your node since back then, you can change your defaults in the deskto…

>You're right, there are a ton of great ideas and suggestions for how to make IPFS better that we haven't gotten to yet I love the idea of IPFS, but let me ask you the question, when is it finally going to be ready for people to easily deploy? A year from now, 3 years, 5 years? Or maybe you have no idea? Don't give some vague answer about how you are working on it. Give me a reasonably specific prediction, or say you…

[deleted]

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

#98

Post by lmm » Mon, Jan 20, 2020, 1:55 AM UTC

alwillis wrote: post #65

azangru wrote: post #20

Earlier quoted context omitted.

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

I’ve been on Netlify for a while and it’s great at what it does. I recently went back to Digital Ocean for my side project because of what Netlify currently doesn’t have: DNSSEC, HTTP/2 push and prioritization. ECC certificates from Let’s Encrypt.

Why do you want ECC specifically? Isn't that an implementation detail?

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

#99

Post by mirimir » Mon, Jan 20, 2020, 1:58 AM UTC

tetrisgm wrote: post #41

Disclaimer: I run the unofficial IPFS Discord and Matrix (found at https://permaweb.io/discord and /matrix) and have helped organize IPFS Meetups in SF. We also run an IPFS gateway and have built a groups app on top of IPFS and Textile. I generally agree with the conclusion, but there's a few downsides that aren't conveyed here. Let's look at the proposed upsides: 1) Ownership, control, censorship: That's partly corr…

> IPFS doesn't encrypt the content, or the connectivity, or hide the hosts. Solutions exist around that, but they're niche, and honestly I question the motives besides just ideology.

Hiding connectivity metadata and host identity are essential to protect users from adversaries.

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

#100

Post by skybrian » Mon, Jan 20, 2020, 1:59 AM UTC

tetrisgm wrote: post #41

Disclaimer: I run the unofficial IPFS Discord and Matrix (found at https://permaweb.io/discord and /matrix) and have helped organize IPFS Meetups in SF. We also run an IPFS gateway and have built a groups app on top of IPFS and Textile. I generally agree with the conclusion, but there's a few downsides that aren't conveyed here. Let's look at the proposed upsides: 1) Ownership, control, censorship: That's partly corr…

I'm wondering if IPFS might be better thought of as a common data-publishing protocol that might be used to push content to any number of CDN's?

So, you could publish content to IPFS and tell your favorite CDN to pick it up, and you pay them to keep it active. But IPFS isn't limited to one CDN, so you could always pick another one. And your users could also go through a different CDN. Or some people who really want to could run their own CDN and pin whatever they want to host.