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

61–70 of 156 posts

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

#61

Post by Sargos »

StavrosK wrote: post #56
Sargos wrote: post #44

Earlier quoted context omitted.

I consider IPNS fundamentally broken and have stopped using it. ENS is better in almost every way and is extremely reliable so it's not that big of deal.

How can I register an ENS domain/id? I've found very little practical info on a cursory search.

There's probably a simple article out there but I'll summarize it a bit:

You go to https://manager.ens.domains/ to register a .eth address and on the settings page for your domain you add a Content record and point it to ipfs://Qma7nxS98CAb2BTaxLJBSFozxxSp5XTu6tMtCrKcRQ9ByV or whatever the IPFS hash of your website is.

After that you can visit your site at https://myname.eth in a browser that supports ENS/IPFS or you can go to https://myname.eth.link in any browser and see your website.

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

#62

Post by StavrosK »

Sargos wrote: post #61
StavrosK wrote: post #56

Earlier quoted context omitted.

How can I register an ENS domain/id? I've found very little practical info on a cursory search.

There's probably a simple article out there but I'll summarize it a bit: You go to https://manager.ens.domains/ to register a .eth address and on the settings page for your domain you add a Content record and point it to ipfs://Qma7nxS98CAb2BTaxLJBSFozxxSp5XTu6tMtCrKcRQ9ByV or whatever the IPFS hash of your website is. After that you can visit your site at https://myname.eth in a browser that supports ENS/IPFS or you…

This is what I needed, thanks!

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

#63

Post by indigodaddy »

indigodaddy wrote: post #34
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…

The other potential possibility/issue that I would be uncomfortable with, would be a bad actor visiting and then seeding my content. Say someone also seeding or just locally having child pornography or some other nefarious thing, and now they are also an aggregator for your non-nefarious content. Just the possibility of that type of potential unintended association gives me pause in terms of considering it for a blog…

I got a downvote so I guess people aren’t concerned about this or believe my concern not valid or naive?

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

#64

Post by agumonkey »

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.

there's something weirdly poetic of having information reborn through voluntary noise

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

#65

Post by alwillis »

azangru wrote: post #20
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.

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.

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

#66

Post by samatman »

indigodaddy wrote: post #63
indigodaddy wrote: post #34

Earlier quoted context omitted.

The other potential possibility/issue that I would be uncomfortable with, would be a bad actor visiting and then seeding my content. Say someone also seeding or just locally having child pornography or some other nefarious thing, and now they are also an aggregator for your non-nefarious content. Just the possibility of that type of potential unintended association gives me pause in terms of considering it for a blog…

I got a downvote so I guess people aren’t concerned about this or believe my concern not valid or naive?

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.

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

#67

Post by rraghur »

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…

Which isp are you on? For all you know, it might be possible to get an ipv6 now.

I was in the same predicament but there was a news item that act(ISP) was rolling out ipv6... speaking with customer care and even escalating to nodal support was useless as they were clueless... Spent an afternoon fiddling with router and I got a v6 address no problem!

Tl;dr; don't believe clueless tech support .. Just try it out at your end.. you might get a pleasant surprise!

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

#68

Post by rakoo »

StavrosK wrote: post #59
olodus wrote: post #26

Last I checked a lot of the consensus were that the Dat project was more mature than IPFS and that it had some advantages over IPFS (such as not using as much resources to run). How is it now? Is it more mature? Even though I actually even sub to their newsletter I haven't really been keeping up to date if they have made any major releases. Not to be a downer on IPFS at all, btw. I'm very glad that both it and Dat ex…

I have quite a bit of experience with IPFS and I tried Dat once. It seems to me that Dat works much better, but I think the immutability of IPFS is its killer feature, Dat is thus much less interesting to me.

Underlying dat data is immutable. It's the constructs built on top that provide mutability. Dat is fundamentally a chain of immutable chunks, some having a special meaning to say what the data means (file/folder) and where to look for it. Once a chunk is there it will 'ever ever change. It is perfectly possible to play with those only.

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

#69

Post by kickscondor »

olodus wrote: post #26

Last I checked a lot of the consensus were that the Dat project was more mature than IPFS and that it had some advantages over IPFS (such as not using as much resources to run). How is it now? Is it more mature? Even though I actually even sub to their newsletter I haven't really been keeping up to date if they have made any major releases. Not to be a downer on IPFS at all, btw. I'm very glad that both it and Dat ex…

Well, Beaker is being rethought and rewritten right now - hopefully it survives that process.

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

#70

Post by indigodaddy »

samatman wrote: post #66
indigodaddy wrote: post #63

Earlier quoted context omitted.

I got a downvote so I guess people aren’t concerned about this or believe my concern not valid or naive?

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.
Post reply on HN