thumbnail of F390FB14-ACCD-47D4-A136-2A911AE06909.png
thumbnail of F390FB14-ACCD-47D4-A136-2A911AE06909.png
F390FB14-ACCD-47D4-A1... png
(36.54 KB, 600x521)
thumbnail of 90B75C81-7663-4496-B218-0E5278A338DF.png
thumbnail of 90B75C81-7663-4496-B218-0E5278A338DF.png
90B75C81-7663-4496-B2... png
(84.15 KB, 762x609)
thumbnail of 00ABD984-E89A-4F24-AFF2-A20AB7E49904.jpeg
thumbnail of 00ABD984-E89A-4F24-AFF2-A20AB7E49904.jpeg
00ABD984-E89A-4F24-AF... jpeg
(62.53 KB, 900x838)
Torrent - MLP DVDs v2 [ISOs], which is >475 GB (appears to share a significant amount of blocks with the v1 release):
http://15.185.172.73:8084/ipfs/bafybeiaozdnfq6yfhr45e63i6li5w7l4wntjtodbeker6hiaejjnryvcxm

 >>/10902/
> [edit config file so that RPC API and Gateway are at non-loopback LAN-only IP addresses]
After doing that, you'll see this at http://10.0.0.123:5001/ipfs/webui -> http://10.0.0.123:5001/ipfs/bafybeigggyffcf6yfhx5irtwzx3cgnk6n3dwylkvcpckzhqqrigsxowjwe/#/welcome :
> Could not connect to the IPFS API [...]
It then shows this easy fix:
> $ ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://10.0.0.123:5001", "http://localhost:3000", "http://127.0.0.1:5001", "https://webui.ipfs.io"]'
> $ ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "POST"]'
I put ', "GET"' after 'POST"': not sure if it was at all helpful to do that. Image unrelated.

----

I've lightly analyzed rule34.xxx website data over the past months. It seems that a large mass purge happened with image posts between image upload #1 and image upload #1,000,000. I don't have solid stats to prove this, but that's what it looks like. This is another reason to dislike and distrust booru.org (who runs rule34.x).