If you are just hosting data for yourself, sure, go ahead and stick with a regular storage provider. IPFS is useful for the cases where there will be many people who will be accessing that data. The more popular a file is, the more nodes in the swarm will have it and the less it will be requested from your node specifically.
“Cheaper and simpler” only if you are comparing with sites hosted on some big cloud provider. Consider the case where you don’t want or can’t rely on, e.g, Cloudflare or AwS and ask yourself how you would serve lots of static data without worrying about bandwidth or getting DDOS.
it is content addressable, files are addressed by their hash, which means you can have a system, e.g, different Lemmy instance admins can share a IPFS server and it gets automatically deduplicated, or you can have something like trustless package managers that run without the need of a central authority.
Might not be useful for you, but it should be useful for a lot of people.
If I share data on an online hosting I also doesn’t pay more for distribution? Or is this for some special cases? I havent checked for a long time but I had over 800Mb/s in like 2010 at OVH and I don’t think it has gone exacty down …
Are you trying to really understand how the thing works, or are you just looking for ways to dismiss the thing so that you can remain ignorant about it.
We’re talking about data transmission caps (as in, 1TB/month), not in bandwidth (as in 800MB/s) Also, IPFS is a protocol. The “cap” of the network is only theoretically bound by the amount of nodes running in it, but in practice it doesn’t really matter because the bandwidth of any single node will always end up being the real bottleneck.
I’m not trying to dismiss this thing, but I see not very many usecases for it. That’s why I ask all those questions and the answers are not really fulfilling IMO.
BTW 800Mb/s is sure a cap too in its way, a 100MB/s is just that, capped on one second instead of a month.
Because you won’t be paying for distribution.
If you are just hosting data for yourself, sure, go ahead and stick with a regular storage provider. IPFS is useful for the cases where there will be many people who will be accessing that data. The more popular a file is, the more nodes in the swarm will have it and the less it will be requested from your node specifically.
So like torrenting?
Yes, very much like torrents
If you could get a torrent file to display an image in your web browser, yes.
So regular web browser can browse IPFS only systems?
Yes. Brave has it built-in. Others can do it through an extension.
Cool. :)
That’s cool, still can’t see why I wouldn’t use http(s) though that is cheaper and simpler?
“Cheaper and simpler” only if you are comparing with sites hosted on some big cloud provider. Consider the case where you don’t want or can’t rely on, e.g, Cloudflare or AwS and ask yourself how you would serve lots of static data without worrying about bandwidth or getting DDOS.
OVH, Mega, insert lots and lots of other providers here. They probably can handle DDOS etc good enough.
I mean is it only for some niche usage (which is totally okay and fine) like serving lots of static data from lesser unknown providers then?
There are two aspects you are ignoring here:
with IPFS you can do it from your own computer
it is content addressable, files are addressed by their hash, which means you can have a system, e.g, different Lemmy instance admins can share a IPFS server and it gets automatically deduplicated, or you can have something like trustless package managers that run without the need of a central authority.
Might not be useful for you, but it should be useful for a lot of people.
If I share data on an online hosting I also doesn’t pay more for distribution? Or is this for some special cases? I havent checked for a long time but I had over 800Mb/s in like 2010 at OVH and I don’t think it has gone exacty down …
There is always a cap.
I assure you, IPFS has a cap too.
The question is, it is higher?
“IPFS” can not have a cap, because IPFS is not a service provider. IPFS is a protocol.
Fair enough.
So the IPFS network has a cap. Like OVH doesn’t have a cap as it’s a company, but their network does.
Are you trying to really understand how the thing works, or are you just looking for ways to dismiss the thing so that you can remain ignorant about it.
We’re talking about data transmission caps (as in, 1TB/month), not in bandwidth (as in 800MB/s) Also, IPFS is a protocol. The “cap” of the network is only theoretically bound by the amount of nodes running in it, but in practice it doesn’t really matter because the bandwidth of any single node will always end up being the real bottleneck.
I’m not trying to dismiss this thing, but I see not very many usecases for it. That’s why I ask all those questions and the answers are not really fulfilling IMO.
BTW 800Mb/s is sure a cap too in its way, a 100MB/s is just that, capped on one second instead of a month.