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

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

#81

Post by singron » Mon, Jan 20, 2020, 12:31 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…

Isn't this kind of an unreasonable demand? It's not like software isn't ready for anyone one day and ready for everyone the next. Considering just about nobody can give an accurate software development forecast for even objective milestones, it seems ridiculous that there would be any reasonable answer to this.

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

#82

Post by bureaucrat » Mon, Jan 20, 2020, 12:33 AM UTC

God, another IPFS shilling.

Can't they come back when it's really usable?

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

#83

Post by bureaucrat » Mon, Jan 20, 2020, 12:36 AM UTC

thenewnewguy wrote: post #23

slacka wrote: post #19

Earlier quoted context omitted.

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 o…

The blog is hosted on IPFS. To allow normal web browsers without IPFS support to view the website they use Cloudflare's IPFS gateway, which is a service that serves content from IPFS over normal HTTP.

i r o n y

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

#84

Post by Fr0styMatt88 » Mon, Jan 20, 2020, 12:48 AM UTC

indigodaddy wrote: post #70

samatman wrote: post #66

Earlier quoted context omitted.

It doesn't seem meaningfully different from a bad actor having, say, a tab with your Wordpress blog open on their computer. Or to pick something closer to the point, someone seeding a copyrighted film and also a Linux distribution. That sort of coexistence has gone on for many years without causing problems for the legal uses of torrents.

Thanks for the feedback. I get your point there. It feels much different though. A tab open is completely read only, and they are not aggregating your content. I guess I just don’t like the idea of seeding my content and not knowing who or what the the “seeders” might also be involved with. I guess purely an ethical concern/decision on my part in likely choosing never to use a seeding technology to serve my content.

That almost seems like a slippery slope. I mean, your site’s content could now just end up sitting on some CDN server or proxy alongside something nefarious, without IPFS and you’d have no idea.

I’d have the same objection if the seeder was voluntarily choosing what to seed for that express purpose, but I don’t know that it should apply if the seeding is just an automatic part of how the network operates underneath.

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

#85

Post by charles_f » Mon, Jan 20, 2020, 12:56 AM UTC

singron wrote: post #81

woodandsteel wrote: post #73

Earlier quoted context omitted.

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

Isn't this kind of an unreasonable demand? It's not like software isn't ready for anyone one day and ready for everyone the next. Considering just about nobody can give an accurate software development forecast for even objective milestones, it seems ridiculous that there would be any reasonable answer to this.

Beyond the question of the possibility of giving a precise answer, did OP lose sight of basic courtesy?

As far as I know IPFS is an open system contributed to by volunteers. Making those kind of demands for deadlines in such an aggressive tone is way out of place.

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

#86

Post by oska » Mon, Jan 20, 2020, 1:01 AM UTC

sergioro wrote: post #72

Stopped reading after "Medium's engineers are much better at all of this than you will ever be"; can't take this writer seriously.

I dislike this formula of "Stopped reading after ..." that I seem to be seeing more frequently.

Why not just make your criticism of the quoted text straight up? Why the rhetorical flounce out of the room?

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

#87

Post by eaurouge » Mon, Jan 20, 2020, 1:10 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…

Interesting name choice. The term “permaweb” is typically associated with Arweave and their decentralized permanent storage offering [1].

1. https://techcrunch.com/2019/11/05/how-arweave-permaweb-works...

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

#88

Post by ajayyy » Mon, Jan 20, 2020, 1:14 AM UTC

heelix wrote: post #8

ISPs have made it really expensive to get a static IP. I maintained a commercial connection for way to many years because I would remote into my home systems.

Not true in Canada

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

#89

Post by judge2020 » Mon, Jan 20, 2020, 1:15 AM UTC

mirimir wrote: post #33

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…

Well, one can use IPFS through Tor, and use gateways that are Tor onion services.

Obfuscating your IP doesn't solve the problem. If a malicious actor knew someone's info (such as address), they could give them an ipfs link with CP and report them.

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

#90

Post by boomlinde » Mon, Jan 20, 2020, 1:16 AM UTC

heelix wrote: post #8

ISPs have made it really expensive to get a static IP. I maintained a commercial connection for way to many years because I would remote into my home systems.

That depends on the market where you are, I suppose. My home ISP offers static addresses as an add-on for a cost comparable to a cheap VPS. With my last ISP there was no static address offer, but the address was the same for years. You can use dyndns-like services for the worst case, then.