NoFetch IPFS gateway in Onion Land!
http://5d6zyscsdarzytpbi3mypv37uoaro2to7oqru4a3oga42bwt3jkof4qd.onion:8080/ipfs/bafybeicavw2zrzrt675a6kaht6tqqjvsxtymvbnt2lhr52tpvqkevcen5a

NoFetch = does egress requests but not ingress requests. Data not locally in that repo =
> failed to resolve /ipfs/cid: block was not found locally (offline): ipld: could not find cid

You can watch this 1.2-GB 13-minute video (though I just dl'd a 480p version of it and watched that instead):
> I_Beat_Minecraft_But_im_a_pony.-Larkin-20230301-youtube-3816x2044-XkDX0mbq2AI.mp4

 >>/11132/
> Are you able to open/view/access the following image file? [onion link]
 >>/11143/
> archive.is is unable to capture that specific PNG
It didn't work, because in Tor Browser, it shows up as application/octet stream ("download only"). What you want is "image/png" to see it in a browser. Seems to be a bug or quirk with darkhttpd because that showed up as viewable in a browser in an IPFS gateway.

 >>/11196/
> 341.70 KiB/s
> How-to make it go faster ...
Saw this today:
> 191h48m43s 231.52 GiB / ? [--=] 351.56 KiB/s
and this on ipfs daemon startup:
> failed to sufficiently increase receive buffer size (was: 176 kiB, wanted: 7168 kiB, got: 352 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
I usually ignored that error/warning message because it seemed to not matter when I changed that setting. However, that 352 kiB looks awfully similar to "351.56 KiB/s" and "341.70 KiB/s". Perhaps if I change that buffer size it will go faster.