>>/9428/
> >>from "lower propagation computer"...: ipfs://QmPZPLT3wKTdo22qVBvxtGbgpkL3tvDpKuVMZuQ9boDLzW
> >"lower propagation computer",
> Is that a computer you run that you refer to as that?
Yes (pinata.cloud isn't the actual host, just a gateway to access data from various users that have their data online; if you have a Pinata account you can pin 1GB there for free, so then Pinata will also/only be the actual host). If you didn't know... here https://ipfs.tech/ it says "IPFS is an open system to manage data without a central server". Basically there are two parts to IPFS: storage and networking (which is peer-to-peer). Everyone can easily store stuff, but to share stuff over the Internet: that's rarer and can wear down and eventually break HDDs too soon (due to high usage) if you don't know what you are doing. So unless anyone else hosts or seeds or stores /ipfs/QmPZPLT3wKTdo22qVBvxtGbgpkL3tvDpKuVMZuQ9boDLzW (QmPZ...DLzW) it will remain only stored and hosted by me. No worries of HDD wear: seed IPFS CIDs via a RAM disk and also store them in a HDD; however, you cannot share tens/hundreds of gigabytes of data this way unless you have a crazy amount of memory. QmPZ...DLzW will be accessible online at the upload speed that I have for as long as I have it up, unless anyone else also seeds it, in that case it would be accessible and up at speed=me+swarm and uptime=me+swarm. It's just like how in BitTorrent various peers can keep data up for longer and at a faster speed than just one guy. (I think you can also pay to have IPFS data stored in Filecoin, which is off-chain storage, not sure about the whole deal with propagation in that case.)
I use 3 computers: a main one, a "higher propagation" one, and a "lower propagation" one. In both the higher and lower propagation computers I self-host IPFS data from a ram disk; said data is Internet-accessible. Uptime in "higher"=currently about 19 days (plus another 9 days if you allow for an hour(s)-long period of downtime >>/9209/); uptime in "lower"=currently about 3 days. See how long the ipfs daemon has been running:
> $ ps -o etime $(ps aux | grep "ipfs daemon" | head -n1 | awk '{print $2}')
One computer is "lower propagation" due to how my local network is physically set up. Maybe in the future I will change it up to have better throughput. I was also thinking of connecting a "consigned to die" 5TB HDD to a computer; that way, I could share hundreds of gigabytes via IPFS over the Internet and not worry about it. Currently only sharing on a "rotational basis" where online stuff which is also stored offline might get rotated out with newer stuff, so it may go offline within the next ~weeks due to storage limitations of the RAM disks.