^
*whatever the character count for /ipfs/baf... is.

> DW190 UC2F4UaQkukqf6CKyc0soMUw
No uploaded MLP videos, playlists maybe related to that.

----

I can locally duplicate larger folders (>100GB) from one HDD to another in a somewhat fault-tolerant way. However, it goes slower than I want and is tolerant of network disconnects but not computer shutdowns. I have set HPC to 85% on all cpu_freq things (CPU throttled) = no thermal shutdowns over days even with higher fan speeds sometimes.  (Maybe only works in a non-hot environment, so not on hot days.) HPC pinning something relatively large = ipfs daemon can die (running "ipfs pin add --progress cid"). So, pin it this way instead, which is less intensive and therefore works better: "ipfs dag export cid | ipfs dag import --stats #; ipfs pin add cid" (running in GNU screen). This is how slow it is:
> 133h33m35s 156.68 GiB / ? [--] 341.70 KiB/s
That's with a folder which contains ISOs of about 260 GB of pornographic DVDs:
> https://bafybeiat5qb276e3wtbaw7624cut2k5hd7n5wta45rfsxoa7aseznzjfuu.ipfs2.eth.limo/
That folder contains a small amount of large files; all of it is raw blocks at 1M chunks.

156.68 GiB over 133 hours and 33 minutes is factoring in the too many times that HPC disconnected from the LAN for hours. If it had a more steady/unbreakable connection like MPC, then more would have been copied sooner. That many GiBs over 5.565 days = a pitiful 28.15 GiB per day at 325.86 KB/s (156680000000B/480816s). Around 300 KB/s = kinda like the minimum tolerable torrent download/upload speed. Local transfers should be faster. How-to make it go faster - with ipfs daemon running ("online"):
> $ ipfs dag export cid | ipfs --offline dag import --stats #; ipfs pin add cid
Offline - fault-tolerant of computer shutdowns but only tolerant of network disconnects per-file unless doing the rsync partial/hashing thing:
> rsync over ssh then hash+store that in HPC, then delete the mutable path
Offline, but only for smaller files/folders:
> ipfs dag export+import over ssh with one or both ipfs daemons being offline (not running)
This is basically fault-tolerant of neither network disconnects nor computer shutdowns. SSH connection closed: have to do it over again (but should run faster due to some things being stored). With this method: could copy a max of like 40 GB before crappy router or older computer disconnecting the LAN(->SSH) connection.

 >>/11167/ (cross-thread)
That PDF is from
> https://web.archive.org/web/20240930022248if_/https://api.products.aspose.app/words/conversion/api/Download?id=80a460b7-82a0-4f93-b29b-c6d850871aad%2FjnL9BW7olBSMNgJWNZLVRKEA5slpd5fMFWZ01JjSJtE.pdf

Image from "clop folder":
https://ipfs.hypha.coop/ipfs/QmS4CsBxFXPqvXYuJp2ZDQCqEMbKMB9zfHQevGY8d3TtTD