6 ms·

I'm still a little lost. Could someone more knowledgeable than me explain how operations in space would benefit from a public content-addressable filesystem? T

I'm still a little lost. Could someone more knowledgeable than me explain how operations in space would benefit from a public content-addressable filesystem? This seems like the kind of application that works best when bandwidth and storage are cheap, and I would have assumed that that, in space, both are about as far from cheap as you can get.

diggan 3y ago
The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific location your computer tries to reach in order to fetch the content. This means that particular node needs to respond to you, and the bandwidth is depending on the bandwidth available on the particular path to that specific node. Instead, IPFS uses content-addressing, where the content is hashed and given a ID based on the content itself. So "foo" could have the ID A, while "bar" could have the ID B. No matter who added the content to the network, if the content is the same, the ID will be the same. The benefit of this is that you can fetch the data from anywhere, and you'll get the data you wanted guaranteed (assuming the content is available somewhere on the network). In terms of space, imagine being on the moon and requesting some website. With location-addressing, you have to be able to reach that particular node, and the data has to travel from there to you. With content-addressing, that content can be fetched from anywhere, maybe another node on the moon has it already, so it can fetched quicker from there, or some node in-between the moon and earth. More reading about content-addressing: https://en.wikipedia.org/wiki/Content-addressable_storage https://en.wikipedia.org/wiki/Content-addressable_storage Magnet links and git are two fairly common technologies that uses content-addressing with lots of benefits. (edit: of course, this is a simplification of both how IP, networks, IPFS, DNS and more works, but I hope it provides a fair overview at least)
- solarkraft 3y ago
  Torrents with extra steps, eh?
  - kibwen 3y ago
    It's basically the same idea as magnet links, so you could say it's torrents with the same steps.
    - ChadNauseam 3y ago
      The main advantage IPFS has over torrents with magnet links is global deduplication / a global swarm. If you seed a torrent that just contains book A, and I seed a torrent that contains books A and B, I won't provide any bandwidth to people downloading book A through your torrent. If we were using IPFS, someone downloading book A will be able to pull from both you and me, even if we don't personally know about each other and started seeding independently.
      - roblabla 3y ago
        Actually, BitTorrent v2 (as specified in BEP 52) has per-file hash trees, so it supports sharing a swarm if the same file is shared between different torrents. Not a whole lot of torrents use it though.
      - anacrolix 3y ago
        This sounds like a feature but it's actually a source of serious performance issues in IPFS.
    - tshaddox 3y ago
      More specifically, I think it’s basically the same idea as trackerless magnet links where you find peers for your file via a DHT. In fact, the Mainline DHT used by most BitTorrent clients is apparently very similar to the DHT used by IPFS. They are both Kademlia implementations.
  - diggan 3y ago
    Torrents also rely on content-addressing, they go hand-in-hand :)
  - autonome 3y ago
    As chance would have it, an excellent deep dive into the differences between IPFS and Bittorrent was published by Daniel Norman today. https://norman.life/posts/ipfs-bittorrent https://norman.life/posts/ipfs-bittorrent
- littlestymaar 3y ago
  > The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific geographical location This complete nonsense. First of all DNS can give you multiple IP addresses[1] (that's how CDNs work eh!) and then IP addresses are only very loosely coupled to geographical locations… [1]: https://www.cloudflare.com/learning/dns/what-is-anycast-dns/ https://www.cloudflare.com/learning/dns/what-is-anycast-dns/
  - diggan 3y ago
    Obviously, it's a simplification, as I'm sure you realized by now. Generally though, I think it can serve as a initial starting point to understanding more. Edit: I removed the "geographical" from the "pointing to a IP which has a specific geographical location" part. Hopefully it'll make things clear enough while not over-simplifying it.
  - deleted 3y ago
    [deleted]
- numbsafari 3y ago
  Yeah, I don’t think your explanation offers anything over and above what actual CDNs already do for us right here on earth. CAS is a separate issue than a caching hierarchy.
  - diggan 3y ago
    > Yeah, I don’t think your explanation offers anything over and above what actual CDNs already do for us right here on earth CDNs usually offer location-addressing, sometimes via different ways but most of the time boils down to "I have to reach that specific node to fetch this specific content". I'm not sure in what other words I could use to explain how content-addressing is different from that... (not even talking about IPFS at this point (or in my grand-parent comment), it's just about URIs vs URLs in the end) (edit: besides, the CDNs you're talking about are with 99% certainty using content-addressing all over the place internally)
- foobiekr 3y ago
  Caches solve this placement problem just fine today and content addressing does not alleviate the placement problem at all. Reality is the space thing is just part of the usual crypto grift narrative building.
  - diggan 3y ago
    > Caches solve this placement problem just fine today and content addressing does not alleviate the placement problem at all. Being able to arbitrary place caches anywhere and let anyone serve the data, and you can trust you're getting the right data, is a huge benefit over location-addressing. Ignoring IPFS, content-addressing makes sense for so many things, which is what lots of storage/caching/CDN solutions have discovered decades ago. Content-addressing is nothing new (nor did Protocol Labs/IPFS "invent" it) and if you're using a CDN to serve content today, the CDN is with 99% certainty using content-addressing at least internally.
    - numbsafari 3y ago
      > Being able to arbitrary place caches anywhere and let anyone serve the data This is the grift. The "libertarians" want to be able to host their CSAM, sorry, their "freedom materials" on everyone's servers in such a way that nobody can ever "silence their freedom" because it would mean silencing the cat gifs, too. Want to be "on the net"? Well, you absolutely have to agree to host anyone else's content without question at all times. But, it's okay, we'll pay you with... coins!
      - diggan 3y ago
        Like many others, you seem to not really grasp how IPFS works. Nothing gets distributed automatically. Besides, how on earth is your argument even relevant when we're talking about content-addressing as a whole, without involving IPFS at all?
        numbsafari 3y ago
        I get how IPFS works. I think the problem you have is that you can't distinguish between IPFS and CAS. Lots of things use CAS, not just IPFS. The specific case you outline can be served by existing technology, without having to introduce magic coins, beans, or other distractions. I was pretty interested in IPFS prior to it being overtaken by web3 grifters.
- bunderbunder 3y ago
  OK. But, going back to my comment about cheap. This claim: > The benefit of this is that you can fetch the data from anywhere Only works if the data I want is being replicated in many locations. But storage in spacecraft is presumably a tightly constrained resource, due to the need to use technology that's space-hardened and has an extremely good reliability record, and is therefore probably far from being both cutting edge and high density. JWST, for example, only has 68GB of storage despite being an instrument for taking high resolution photographs. I would guess that that creates a situation that is very far from the one content-addressable storage is trying to solve. The goal isn't on-demand access to arbitrary files that are just sitting around in long term storage, because I'm guessing that, in space, there is effectively no long-term storage of data files in the first place. Instead, what you're looking to do is to get the data off of the spacecraft and down to earth as quickly and efficiently as possible, and then delete it from the spacecraft's storage so that you can make room to do more cool space stuff. And I also don't want to be using my spacecraft's SSD to cache or replicate data for others if I can possibly avoid it. That will unnecessarily shorten the lifetime of the SSD, and, by extension, the piece of hardware that I just spent millions or perhaps even billions of dollars to build and launch into space. And I just can't follow you as far as > imagine being on the moon and requesting some website because, right here right now, that is such a hypothetical situation that I have absolutely no idea why it needs a real-world demonstration of proof of concept using currently-available technology. Let's wait to see if browsing the Web from the moon leaves the domain of science fiction and becomes science reality first, so that then we can benefit from whatever technology exists in that future when we're solving the problem.
  - jayd16 3y ago
    You're asking why a superglue company would superglue a construction worker to a steel beam. Its promotional material.
    - TrainedMonkey 3y ago
      I think the key is understanding why promotional material matters so much to crypto. Crypto operates on hype -> higher price -> FOMO -> higher price cycle. The trade is that for large holders $$$ invested in hype would return significantly higher gains. This enabled questionable coins / ICOs to get celebrity endorsements for easy money in the past. In current regime the model can still work, but with smaller returns and significantly higher execution barriers.
- hasty_pudding 3y ago
  How do you mark something for deletion? Or once its in the network thats it? Seems easy to DDOS by changing one character many times in a file which generates a new id each time
  - diggan 3y ago
    > How do you mark something for deletion? The same as you'd delete anything from any protocol essentially, you delete it locally. If you've shared it on the internet, you ask people nicely to delete it, if they refuse, you either pursue them legally or give up. Basically, just like how you delete a picture from the internet today. > Seems easy to DDOS by changing one character many times in a file which generates a new id each time All you're doing in that case is adding more files locally and filling your hard-drive with random files. No content gets automatically distributed unless people request it.
    - deleted 3y ago
      [deleted]
- simiones 3y ago
  You still have to talk to specific machines to get the data, so having it content addressable will not automatically make it either more or less rapidly available. Also, even for a peer-to-peer network, you still need some way to discover the peers that actually have the data, so you need some kind of centralized infrastructure that can help coordinate. Ultimately whether you connect to a CDN or to the centralized P2P facilitator is not such a massive difference. Also, given the way ISPs typically operate, you will probably have much better bandwidth downloading from a centralized server than from a generic other end-user. This is why BitTorrent only really has two successfully deployed use cases: 1. Windows updates and similar, where machines can rely on broadcasts on a small LAN to coordinate without needing more complex infrastructure (doesn't scale beyond LAN) 2. "Piracy", where the major advantage is that it diffuses the blame for copyright infringement, instead of presenting a single large target that holds all of it.
wegfawefgawefg 3y ago
I think the idea behind content addressable databases like this is that they are supposed to be permanent. Putting it out into space may be a way of saying "its never going down".
- diggan 3y ago
  Worth noting that content-addressing is not meant to help making the data itself permanent, but it does help with making the identifier of the content permanent. It doesn't guarantee that the content the ID resolves to is available, but once you have a content-addressable ID, you can be sure you'll be able to get the data as long as the data is available somewhere on the network.
- Yizahi 3y ago
  Most likely and obfuscation technique, they (IPFS people) are afraid to admit that there is no guarantee about file preservation there at all (unless you pay to people hosting your files specifically) and cache eviction may happen to your file at any time, so they try to shout all across the internet how their tech is so reliable and great to drown any dissent. Scary and important looking headlines like "Something In Space" help to instill superficial respect in the tech.
  - wegfawefgawefg 3y ago
    I have uploaded files about 3 years ago to ipfs and somehow its still there.
    - Yizahi 3y ago
      Unfortunately I have to repeat what I just wrote word for word: "there is no GUARANTEE about file preservation there at all (unless you pay to people hosting your files specifically)" Sure your files are accidentally still present in the cache. Good for you. The problem is deceiving other people who may think it's somehow spacemagically-interplanetary guaranteed.
      - 3y ago
jauntywundrkind 3y ago
You're asking about why run this service in space, but this service is a reliable scalable data store. Ask instead what kinds of data would you want in space, and why? The throughput probably won't be great, but mainly if we assume 1:1 not broadcast connections! There will be roving access, not continual, to a given satellite - a fact until there are thousands of other satellites also serving ipfs. Costs will be high. But still, there are wins. So far, satellite reliability is fairly high; there haven't been natural or human-made disasters afflicting many satellites. In some conditions the roving nature of the satellite could be a boon; you can get information out to a lot of people. Wikipedia, news, important events... those would all benefit from guaranteed-reoccuring-availability model, perhaps. This would be an interesting tamper-resistant way to store something like votes, if it could be vetted. If there's satellite to satellite communications, the ability to have an expanding archive of crucial orbital information is useful; the swarm can grow & update vital behavior with ipfs in interesting ways. Rather than assess just on whether this will make a good ipfs node as ipfs is typically used (high bandwidth, high storage nodes), I think it's worth considering this on the merits of what this technology offers that is distinct. Pulling out a single ruler to measure everything isn't always the best and only way to judge; indeed I think we miss a lot when we apply only our current set of expectations to new ideas & encounters. I'd encourage a more liberal consideration. Although I agree, I'm not sure either what the killer use is, I want to see thinking that pioneers what could work, that explored what values are on offer, even if it's not the same old values as the incumbent (fiber optics on the ground).
- deleted 3y ago
  [deleted]
posix86 3y ago
It's quite the opposite. We've sketched out a school platform using IPFS that allows very remote villages in third world countries that have little to no internet to still have viable "google drive" like experiences for school home work. The idea is that a single USB drive that contains all the updated files for the google drive is sufficient for the entire network (that exists in the village, that is decent, but has otherwise very low to no bandwidth to the outside world) to have access to the files. Or, a single node downloads the homework/movie/article/whatever, and the remainder of the network has access to it - through IPFS, which only asks for the content's hash, and gets it whever it can. The same thing could be applied to space.
- pastage 3y ago
  Have you actually used it? The usb with random information is a very versatile distribution method, I am not sure IPFS is much better than this.

diggan 3y ago

The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific location your computer tries to reach in order to fetch the content. This means that particular node needs to respond to you, and the bandwidth is depending on the bandwidth available on the particular path to that specific node. Instead, IPFS uses content-addressing, where the content is hashed and given a ID based on the content itself. So "foo" could have the ID A, while "bar" could have the ID B. No matter who added the content to the network, if the content is the same, the ID will be the same. The benefit of this is that you can fetch the data from anywhere, and you'll get the data you wanted guaranteed (assuming the content is available somewhere on the network). In terms of space, imagine being on the moon and requesting some website. With location-addressing, you have to be able to reach that particular node, and the data has to travel from there to you. With content-addressing, that content can be fetched from anywhere, maybe another node on the moon has it already, so it can fetched quicker from there, or some node in-between the moon and earth. More reading about content-addressing: https://en.wikipedia.org/wiki/Content-addressable_storage https://en.wikipedia.org/wiki/Content-addressable_storage Magnet links and git are two fairly common technologies that uses content-addressing with lots of benefits. (edit: of course, this is a simplification of both how IP, networks, IPFS, DNS and more works, but I hope it provides a fair overview at least)

solarkraft 3y ago
Torrents with extra steps, eh?
- kibwen 3y ago
  It's basically the same idea as magnet links, so you could say it's torrents with the same steps.
  - ChadNauseam 3y ago
    The main advantage IPFS has over torrents with magnet links is global deduplication / a global swarm. If you seed a torrent that just contains book A, and I seed a torrent that contains books A and B, I won't provide any bandwidth to people downloading book A through your torrent. If we were using IPFS, someone downloading book A will be able to pull from both you and me, even if we don't personally know about each other and started seeding independently.
    - roblabla 3y ago
      Actually, BitTorrent v2 (as specified in BEP 52) has per-file hash trees, so it supports sharing a swarm if the same file is shared between different torrents. Not a whole lot of torrents use it though.
    - anacrolix 3y ago
      This sounds like a feature but it's actually a source of serious performance issues in IPFS.
  - tshaddox 3y ago
    More specifically, I think it’s basically the same idea as trackerless magnet links where you find peers for your file via a DHT. In fact, the Mainline DHT used by most BitTorrent clients is apparently very similar to the DHT used by IPFS. They are both Kademlia implementations.
- diggan 3y ago
  Torrents also rely on content-addressing, they go hand-in-hand :)
- autonome 3y ago
  As chance would have it, an excellent deep dive into the differences between IPFS and Bittorrent was published by Daniel Norman today. https://norman.life/posts/ipfs-bittorrent https://norman.life/posts/ipfs-bittorrent
littlestymaar 3y ago
> The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific geographical location This complete nonsense. First of all DNS can give you multiple IP addresses[1] (that's how CDNs work eh!) and then IP addresses are only very loosely coupled to geographical locations… [1]: https://www.cloudflare.com/learning/dns/what-is-anycast-dns/ https://www.cloudflare.com/learning/dns/what-is-anycast-dns/
- diggan 3y ago
  Obviously, it's a simplification, as I'm sure you realized by now. Generally though, I think it can serve as a initial starting point to understanding more. Edit: I removed the "geographical" from the "pointing to a IP which has a specific geographical location" part. Hopefully it'll make things clear enough while not over-simplifying it.
- deleted 3y ago
  [deleted]
numbsafari 3y ago
Yeah, I don’t think your explanation offers anything over and above what actual CDNs already do for us right here on earth. CAS is a separate issue than a caching hierarchy.
- diggan 3y ago
  > Yeah, I don’t think your explanation offers anything over and above what actual CDNs already do for us right here on earth CDNs usually offer location-addressing, sometimes via different ways but most of the time boils down to "I have to reach that specific node to fetch this specific content". I'm not sure in what other words I could use to explain how content-addressing is different from that... (not even talking about IPFS at this point (or in my grand-parent comment), it's just about URIs vs URLs in the end) (edit: besides, the CDNs you're talking about are with 99% certainty using content-addressing all over the place internally)
foobiekr 3y ago
Caches solve this placement problem just fine today and content addressing does not alleviate the placement problem at all. Reality is the space thing is just part of the usual crypto grift narrative building.
- diggan 3y ago
  > Caches solve this placement problem just fine today and content addressing does not alleviate the placement problem at all. Being able to arbitrary place caches anywhere and let anyone serve the data, and you can trust you're getting the right data, is a huge benefit over location-addressing. Ignoring IPFS, content-addressing makes sense for so many things, which is what lots of storage/caching/CDN solutions have discovered decades ago. Content-addressing is nothing new (nor did Protocol Labs/IPFS "invent" it) and if you're using a CDN to serve content today, the CDN is with 99% certainty using content-addressing at least internally.
  - numbsafari 3y ago
    > Being able to arbitrary place caches anywhere and let anyone serve the data This is the grift. The "libertarians" want to be able to host their CSAM, sorry, their "freedom materials" on everyone's servers in such a way that nobody can ever "silence their freedom" because it would mean silencing the cat gifs, too. Want to be "on the net"? Well, you absolutely have to agree to host anyone else's content without question at all times. But, it's okay, we'll pay you with... coins!
    - diggan 3y ago
      Like many others, you seem to not really grasp how IPFS works. Nothing gets distributed automatically. Besides, how on earth is your argument even relevant when we're talking about content-addressing as a whole, without involving IPFS at all?
      - numbsafari 3y ago
        I get how IPFS works. I think the problem you have is that you can't distinguish between IPFS and CAS. Lots of things use CAS, not just IPFS. The specific case you outline can be served by existing technology, without having to introduce magic coins, beans, or other distractions. I was pretty interested in IPFS prior to it being overtaken by web3 grifters.
bunderbunder 3y ago
OK. But, going back to my comment about cheap. This claim: > The benefit of this is that you can fetch the data from anywhere Only works if the data I want is being replicated in many locations. But storage in spacecraft is presumably a tightly constrained resource, due to the need to use technology that's space-hardened and has an extremely good reliability record, and is therefore probably far from being both cutting edge and high density. JWST, for example, only has 68GB of storage despite being an instrument for taking high resolution photographs. I would guess that that creates a situation that is very far from the one content-addressable storage is trying to solve. The goal isn't on-demand access to arbitrary files that are just sitting around in long term storage, because I'm guessing that, in space, there is effectively no long-term storage of data files in the first place. Instead, what you're looking to do is to get the data off of the spacecraft and down to earth as quickly and efficiently as possible, and then delete it from the spacecraft's storage so that you can make room to do more cool space stuff. And I also don't want to be using my spacecraft's SSD to cache or replicate data for others if I can possibly avoid it. That will unnecessarily shorten the lifetime of the SSD, and, by extension, the piece of hardware that I just spent millions or perhaps even billions of dollars to build and launch into space. And I just can't follow you as far as > imagine being on the moon and requesting some website because, right here right now, that is such a hypothetical situation that I have absolutely no idea why it needs a real-world demonstration of proof of concept using currently-available technology. Let's wait to see if browsing the Web from the moon leaves the domain of science fiction and becomes science reality first, so that then we can benefit from whatever technology exists in that future when we're solving the problem.
- jayd16 3y ago
  You're asking why a superglue company would superglue a construction worker to a steel beam. Its promotional material.
  - TrainedMonkey 3y ago
    I think the key is understanding why promotional material matters so much to crypto. Crypto operates on hype -> higher price -> FOMO -> higher price cycle. The trade is that for large holders $$$ invested in hype would return significantly higher gains. This enabled questionable coins / ICOs to get celebrity endorsements for easy money in the past. In current regime the model can still work, but with smaller returns and significantly higher execution barriers.
hasty_pudding 3y ago
How do you mark something for deletion? Or once its in the network thats it? Seems easy to DDOS by changing one character many times in a file which generates a new id each time
- diggan 3y ago
  > How do you mark something for deletion? The same as you'd delete anything from any protocol essentially, you delete it locally. If you've shared it on the internet, you ask people nicely to delete it, if they refuse, you either pursue them legally or give up. Basically, just like how you delete a picture from the internet today. > Seems easy to DDOS by changing one character many times in a file which generates a new id each time All you're doing in that case is adding more files locally and filling your hard-drive with random files. No content gets automatically distributed unless people request it.
  - deleted 3y ago
    [deleted]
simiones 3y ago
You still have to talk to specific machines to get the data, so having it content addressable will not automatically make it either more or less rapidly available. Also, even for a peer-to-peer network, you still need some way to discover the peers that actually have the data, so you need some kind of centralized infrastructure that can help coordinate. Ultimately whether you connect to a CDN or to the centralized P2P facilitator is not such a massive difference. Also, given the way ISPs typically operate, you will probably have much better bandwidth downloading from a centralized server than from a generic other end-user. This is why BitTorrent only really has two successfully deployed use cases: 1. Windows updates and similar, where machines can rely on broadcasts on a small LAN to coordinate without needing more complex infrastructure (doesn't scale beyond LAN) 2. "Piracy", where the major advantage is that it diffuses the blame for copyright infringement, instead of presenting a single large target that holds all of it.

wegfawefgawefg 3y ago

I think the idea behind content addressable databases like this is that they are supposed to be permanent. Putting it out into space may be a way of saying "its never going down".

diggan 3y ago
Worth noting that content-addressing is not meant to help making the data itself permanent, but it does help with making the identifier of the content permanent. It doesn't guarantee that the content the ID resolves to is available, but once you have a content-addressable ID, you can be sure you'll be able to get the data as long as the data is available somewhere on the network.
Yizahi 3y ago
Most likely and obfuscation technique, they (IPFS people) are afraid to admit that there is no guarantee about file preservation there at all (unless you pay to people hosting your files specifically) and cache eviction may happen to your file at any time, so they try to shout all across the internet how their tech is so reliable and great to drown any dissent. Scary and important looking headlines like "Something In Space" help to instill superficial respect in the tech.
- wegfawefgawefg 3y ago
  I have uploaded files about 3 years ago to ipfs and somehow its still there.
  - Yizahi 3y ago
    Unfortunately I have to repeat what I just wrote word for word: "there is no GUARANTEE about file preservation there at all (unless you pay to people hosting your files specifically)" Sure your files are accidentally still present in the cache. Good for you. The problem is deceiving other people who may think it's somehow spacemagically-interplanetary guaranteed.
    - 3y ago

jauntywundrkind 3y ago

You're asking about why run this service in space, but this service is a reliable scalable data store. Ask instead what kinds of data would you want in space, and why? The throughput probably won't be great, but mainly if we assume 1:1 not broadcast connections! There will be roving access, not continual, to a given satellite - a fact until there are thousands of other satellites also serving ipfs. Costs will be high. But still, there are wins. So far, satellite reliability is fairly high; there haven't been natural or human-made disasters afflicting many satellites. In some conditions the roving nature of the satellite could be a boon; you can get information out to a lot of people. Wikipedia, news, important events... those would all benefit from guaranteed-reoccuring-availability model, perhaps. This would be an interesting tamper-resistant way to store something like votes, if it could be vetted. If there's satellite to satellite communications, the ability to have an expanding archive of crucial orbital information is useful; the swarm can grow & update vital behavior with ipfs in interesting ways. Rather than assess just on whether this will make a good ipfs node as ipfs is typically used (high bandwidth, high storage nodes), I think it's worth considering this on the merits of what this technology offers that is distinct. Pulling out a single ruler to measure everything isn't always the best and only way to judge; indeed I think we miss a lot when we apply only our current set of expectations to new ideas & encounters. I'd encourage a more liberal consideration. Although I agree, I'm not sure either what the killer use is, I want to see thinking that pioneers what could work, that explored what values are on offer, even if it's not the same old values as the incumbent (fiber optics on the ground).

deleted 3y ago
[deleted]

posix86 3y ago

It's quite the opposite. We've sketched out a school platform using IPFS that allows very remote villages in third world countries that have little to no internet to still have viable "google drive" like experiences for school home work. The idea is that a single USB drive that contains all the updated files for the google drive is sufficient for the entire network (that exists in the village, that is decent, but has otherwise very low to no bandwidth to the outside world) to have access to the files. Or, a single node downloads the homework/movie/article/whatever, and the remainder of the network has access to it - through IPFS, which only asks for the content's hash, and gets it whever it can. The same thing could be applied to space.

pastage 3y ago
Have you actually used it? The usb with random information is a very versatile distribution method, I am not sure IPFS is much better than this.