Live data from Hacker News

IPFS 0.5

blog.ipfs.io

131–140 of 145 posts

Re: IPFS 0.5

#131
post #62

Can someone provide an example of a service that ipfs enables that can’t be provided on the regular web?

You can publish static content that doesn't go down when the server goes down and scales on its own as the content becomes more popular. It also has hashing built-in, so you can be sure the content you got is what you wanted, Things like distribution of apt packages becomes much more exciting when each computer can choose to redistribute the packages it got to others in the LAN or area, even offline. It's also very i…

That's "how it works", not "what it can be used for". Regular websites can be designed to handle high traffic. Regular websites can make backups.

What new thing does ipfs make possible that would make users install the software to use it?

Re: IPFS 0.5

#132
post #41

Earlier quoted context omitted.

Rust will start edging out Go once Rust becomes easier than Go to prototype/start projects. Rust is a great language, but right now I can start a project in Go and have someone else start a project in Go and have something up and working in a week. Rust still takes significantly longer to learn and/or find skilled developers for. Go is up there with Python in terms of "Get something out now ".

Rust isn't that difficult to prototype or start projects with? What trouble do you run into? I think the hardest parts to understand are the concepts of borrowing, lifetimes, and ownership, but you don't have to know all the subtleties of that to prototype. A basic understanding is fine to get started with. Just like a developer doesn't have to understand all the subtleties of generics to get started with either, lot…

A good related question is: what will be the "future" of software development? I would bet that WASM and Rust will become more and more dominant in a 5-10 years timeframe. But it's so hard to come up with an informed opinion, as many developers tend to become "religious" about their language of choice.

Re: IPFS 0.5

#133

Earlier quoted context omitted.

You can publish static content that doesn't go down when the server goes down and scales on its own as the content becomes more popular. It also has hashing built-in, so you can be sure the content you got is what you wanted, Things like distribution of apt packages becomes much more exciting when each computer can choose to redistribute the packages it got to others in the LAN or area, even offline. It's also very i…

That's "how it works", not "what it can be used for". Regular websites can be designed to handle high traffic. Regular websites can make backups. What new thing does ipfs make possible that would make users install the software to use it?

Nothing has any advantage except the advantages it has. I don't want to repeat everything I said in the last post, but what you mentioned isn't a counterargument to any of what I detailed.

Re: IPFS 0.5

#134
post #102
post #63

Earlier quoted context omitted.

If there's enough enthusiasts using spare disks at home to offer enough disk capacity for everyone, then that means Filecoin hosting will be available cheaper than cloud hosts. If all that capacity gets used up, then supply and demand will cause the price to go up until more people add capacity. If the price hits the price of cloud hosts, then people will just run tons of Filecoin nodes on cloud hosts, so the price o…

> If there's enough enthusiasts using spare disks at home to offer enough disk capacity for everyone, then that means Filecoin hosting will be available cheaper than cloud hosts. Only if these enthusiasts are willing to take a loss on power. > If the price hits the price of cloud hosts, then people will just run tons of Filecoin nodes on cloud hosts Or the cloud hosts themselves will enter the market. The upper bound…

> Only if these enthusiasts are willing to take a loss on power.

An 8TB HDD doesn't use more power than a 100GB one.

Re: IPFS 0.5

#135
post #134
post #102

Earlier quoted context omitted.

> If there's enough enthusiasts using spare disks at home to offer enough disk capacity for everyone, then that means Filecoin hosting will be available cheaper than cloud hosts. Only if these enthusiasts are willing to take a loss on power. > If the price hits the price of cloud hosts, then people will just run tons of Filecoin nodes on cloud hosts Or the cloud hosts themselves will enter the market. The upper bound…

> Only if these enthusiasts are willing to take a loss on power. An 8TB HDD doesn't use more power than a 100GB one.

It is not a matter of size. It is a matter of availability.

If I only have my data on a disk, I can turn it off anytime. If I am hosting someone else's data and I want to get paid for it, I need to keep the computer running 24/7/365. That costs quite a bit.

Re: IPFS 0.5

#136

Good progress. I looked at IPFS a few months ago from the point of view of fitting a decentralized file store. The decentralized requirement came primarily from the point of view wanting to fit this in a broader product that is all about decentralized for various reasons. Key problems in this space: - decentralized is something techies obsess about but that has as of yet no business value whatsoever. Customers don't…

Siacoin seems much farther along if you just want a decentralized file store solution where you can pay others to provide the storage/bandwidth.

Re: IPFS 0.5

#137

Earlier quoted context omitted.

That's "how it works", not "what it can be used for". Regular websites can be designed to handle high traffic. Regular websites can make backups. What new thing does ipfs make possible that would make users install the software to use it?

Nothing has any advantage except the advantages it has. I don't want to repeat everything I said in the last post, but what you mentioned isn't a counterargument to any of what I detailed.

If you're not going to answer a question, don't bother replying.

Re: IPFS 0.5

#138

Earlier quoted context omitted.

Nothing has any advantage except the advantages it has. I don't want to repeat everything I said in the last post, but what you mentioned isn't a counterargument to any of what I detailed.

If you're not going to answer a question, don't bother replying.

> Regular websites can be designed to handle high traffic

IPFS lets them not have to.

> Regular websites can make backups

Backups don't help when the company shuts down and takes the site down.

> What new thing does ipfs make possible that would make users install the software to use it?

"Think of all the Geocities sites (and all versions of them) just existing for ever, regardless if Geocities decided to shut down."

I don't think you even read my post.

Re: IPFS 0.5

#139
post #85
post #58

Earlier quoted context omitted.

Understanding the concepts is one thing, applying them is another thing entirely. The Rust compiler is an incredibly difficult beast to placate.

Especially in prototyping you can mostly .clone() everything, and stop worrying about any lifetime problems.

Lots of deferred pain for when you productionize.

Re: IPFS 0.5

#140
post #134
post #102

Earlier quoted context omitted.

> If there's enough enthusiasts using spare disks at home to offer enough disk capacity for everyone, then that means Filecoin hosting will be available cheaper than cloud hosts. Only if these enthusiasts are willing to take a loss on power. > If the price hits the price of cloud hosts, then people will just run tons of Filecoin nodes on cloud hosts Or the cloud hosts themselves will enter the market. The upper bound…

> Only if these enthusiasts are willing to take a loss on power. An 8TB HDD doesn't use more power than a 100GB one.

> An 8TB HDD doesn't use more power than a 100GB one.

But access to it by third parties does, it changes the usage model and increases your electricity costs. This may not be a lot but it doesn't have to be a lot to make your costs more than those of a datacentre operator, not to mention you also need to be online all the time.

The dream of edge-node storage utilisation has never survived in the face of economic analysis.

Post reply on HN