If i may ask, how long would it take for a regular diplomatic programmer to set the site up with all of its button commands working as needed?
It would be pretty quick and easy to get a basic site going. The hardest part would be developing patreon/fanbox/etc site scrapers. To answer your question, this whole thing could probably be set up in under a day, not counting the hardware side of it.
A comment above said the entire archive took up only 30TB, which isn't really that much if self-hosting, because harddrive prices have fallen dramatically.
But if the site uses cloud-based storage, 30TB would be a very very expensive monthly cost. It would also require hefty bandwidth to support all the image loading requests from thousands of people a day.
If I were to make this, I would go for a torrent-based site. Could have a few preview pictures per artist, and have the rest of their content in a torrent file where there is no bandwidth needed for the site host, thus the site saves a ton of money and would be blazing fast. I think this is where yiff party failed, they had so much content, all self-hosted, so it bogged down the site so bad that sometimes we couldn't even browse it.
If it was
not a torrent-based site, I would set up a way to require every user to contribute at least 1 artist's content in order to unlock the rest of the site to download/browse content. That way the site has content to share, and it would dramatically cut down on the amount of leechers who use up all the bandwidth for free.
---
Long ass edit:
Not sure if it was clear, but my idea for the paywalled version was just for if the site hosted all of the content itself. Buying 30TB of cloud storage is not cheap, even with a fuckton of ads out of the ass. So obviously the other version that's free and doesn't host any content itself is the ideal version.
As for a "torrent-based site", I meant similar to how sites like
thepiratebay work, where seeders have the content, and leechers can download it from them for free. So the site would just basically be an index for these torrent hashes without having to store any content itself, again similar to how
thepiratebay is. niginigi's reply to this below is excellent in further expanding on this idea, using IPFS and storing hashes.
It would be future-proof, because if there was a lawsuit against the site, the site owner can simply claim that he doesnt host ANY content at all, therefore is not liable. If the site did go down, whoever kept lists of hashes could still share that list and let people continue downloading anything and everything, site or no site.
(Also, important note, I hope saying something political doesn't get me banned or anything, but Trump wanted to get rid of "Section 230". Section 230 makes it so site owners aren't responsible for content that it's users post. So if Trump got rid of it, there is no way in hell I would consider making a "yiff alternative" site, I would just be living the rest of my life fighting lawsuits and
losing every single one.)