thumbnail of CF9010C3-6A65-44BE-9BC9-F5FDDEF05F0B.jpeg
thumbnail of CF9010C3-6A65-44BE-9BC9-F5FDDEF05F0B.jpeg
CF9010C3-6A65-44BE-9B... jpeg
(41.51 KB, 315x315)
Cute Aggression
*WBM is back to being RW

 >>/11278/
With IPFS, data added to the repo using an ipfs command will never be invalid; it will always be bit-identical and hash-matching. Beyond that, there isn't much checking. Data coming out of an IPFS repo isn't checked for validity. BitTorrent is just like IPFS in these ways. Data egress isn't checked because that is too computationally/IO expensive. Data ingress is checked because it needs to at least initially be correct. Any exceptions to this? I was doing dag export+import over ssh from repo to repo (two different computers), and I think it didn't catch bad data where the "ipfs pin add [...]" command did on that same folder or file. Kubo IPFS does have some internal checks, text from roughly one year ago:
> $ ipfs repo gc
> Error: could not retrieve links for Qmaiwpin42nVvC98FEzMpcT29WM6DLtwdFJWqWfRPevjPq: block was not found locally (offline): ipld: could not find Qmaiwpin42nVvC98FEzMpcT29WM6DLtwdFJWqWfRPevjPq; garbage collection aborted: could not retrieve some links
> $ ipfs pin verify
> bafybeihlu4hgzryk6por3kedlkuoyjietr5vmmdpsoqshn2r5bmys7pwt4 broken
>  Qmaiwpin42nVvC98FEzMpcT29WM6DLtwdFJWqWfRPevjPq: block was not found locally (offline): ipld: could not find Qmaiwpin42nVvC98FEzMpcT29WM6DLtwdFJWqWfRPevjPq
> $ # ipfs://bafybeihlu4hgzryk6por3kedlkuoyjietr5vmmdpsoqshn2r5bmys7pwt4/ is MLP: The Manga
IPFS's pin verification command is like "checking resume data" in BitTorrent: it checks if all files related to the hashtree exist. Neither verify if the data in those files is completely valid to what it originally was. BitTorrent has an option to "recheck" a torrent, and this does recompute the SHA1/SHA2 hashes of all the piece(s) to see if they are valid. IPFS doesn't explicitly have a thing to do this, and Kubo doesn't have a thing to check all data in the repo for corruption or bad changes in a hash validity sort of way (maybe a gc command can do this?). However you can do stuff like this to check for validity, remember to use the original chunking settings:
> $ ipfs cat Qm.. | ipfs add
> $ ipfs add --cid-version=1 /ipfs/baf..
Input and output Qm/baf hash should be the same, otherwise there's a problem.

pfp from
> https://web.archive.org/web/20241105163234/https://inv.nadeko.net/watch?v=HWx2f0vGKWQ - title="DON'T SCREAM (literally)"