YayPonies has hundreds of torrents. I can't abide by this, or that's my initial thought. I'm not really interested in "exploding" qBittorrent with those many new entries to the transfer list. At least, I don't really want to keep them in there permanently. Maybe I'll download many of them with qBittorrent and not seed them at all. That many torrents where each one contains only one ~20 MB file: seems better suited for IPFS. Why so many torrents? Perhaps they could have done this: make per-year torrent sets. Those could include all of their releases for each year that they released. And with torrents, you can have multiple torrents which all are including one specific file path (so many:one with torrents:one_file_path_such_as_/path/example.txt). https://yayponies.no/books/resources/book.json basically has 805 .torrent URLs, such as:
>$ sort -R yayponies.no-books-resources-book.json.torrent.txt | head -n3
>https://yayponies.no/books/torrents/CBZ/YP-CBZ-ANNUAL17.cbz.torrent
>https://yayponies.no/books/torrents/CBZ/YP-CBZ-COMIC57.cbz.torrent
>https://yayponies.no/books/torrents/EPUB/YP-EPUB-ANNUAL2013-HB.epub.torrent

Due to WBM's limitations, it's a bit of a pain to try to save all of those links to WBM using automated methods. So here's a WARC of that which has this info:
> wpull.application.tasks.stats - INFO - Duration: 0:01:56. Speed: 26.0 KiB/s.
> wpull.application.tasks.stats - INFO - Downloaded: 805 files, 4.3 MiB.
(All HTTP 200.) Trying to save those all to WBM = a pain, takes way longer.

>>10201
>eFYFu9ytsVg
Nice video, easy explanation on how to run Bash with Apache. Knowing this, I can now maybe make IPFS more accessible when using a 32-bit computer: just gotta make some .sh files to do that. Notes:
>$ grep -R LoadModule /etc/apache2 | grep mod_cgi
>/etc/apache2/mods-available/cgid.load:LoadModule cgid_module /usr/lib/apache2/modules/mod_cgid.so
>/etc/apache2/mods-available/cgi.load:LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so