Bloo

4ChanArchives.Cu.CC is worth mentioning for several reasons:
[*] He is the only one currently hosting the 4Archive's DB
[*] He is using a self/hand-made system for displaying that DB, not using any CMS/framework
[*] he is using a heavily modified system based on the 4Archive's lumenCMS for his auto/on-demand archiving
[*] He has been resolving any DMCA/takedown e-mails as well as replying swiftly to any sort of e-mail
[*] He is running advertisements on his site
[*] He has reuploaded more than 632k images from imageshack to imgur via MashapeAPI
[*] He is privately working on bringing up a new and better on-demand archiving system
[*] He is privately working on bringing up a 1:1 version of archive.moe, just as it was in the day it died.
[*] He has plans to convert some day the 4Archive's DB in to Fuuka DB structure
[*] He is online 24/7 and often active on the irc.rizon.net on several channels (nickname: Bloo_SemiAFK)

As of 1.November 2015, any image shown on imageshack free account will no longer be hot-linkable (displayed on other than imageshack's website) and as of 1. January 2015 all images hosted on free accounts will be deleted. 4ChanArchives.cu.cc admin (known as Bloo_SemiAFK in rizon's IRC network) took the tough challenge of getting all imageshack links from the current 4Archive's DB reuploaded.
At first he attempted to speak to 4Archive via email but the admin never replied.
He then bought a 25$ subscribtion to imageshack, only to get told that he is uploading too much and no matter how much he is paying he will not be allowed to upload this many images.
He then went to mashape and imgur, paying at first 25USD/month with a 25k images/day limit but quickly realized that it would take too long and bought a better plan with 100USD and 100k images/day limit.
Imgur does not allow direct uploading of imageshack images, for whatever reason there is, so he had to downloading every single image and uploading it to imgur via mashape. It took him about 25days and in the end out of the 665,015 images (~303.04GB) he managed to save 632,279 images (~288.18GB). The rest, 32,736 images (~14.86GB) were either deleted from the imageshack servers or corrupted and not archivable. He also provided the DB dump with the new links.[provide the link to the zip i gave you after you upload it to archive.com or w/e]
Thus, [stikretough]all[stikretough] most 4Archive images are now on imgur.
Speaking of imgur, whenever someone sends a DMCA to them, they remove the image. This causes the DB to have a lot of imgur link entries which point to nothing. In the following months he is going to check every single link in the 4Archive's DB and if it's deleted, it will be replaced with a 404.png. Empty posts (having a 404.png and no text body) are deleted as they have no value anymore and only keep DB space.
The table DB structure looks like this: http://i.imgur.com/CqZAEmO.png

In terms of the advertisements on 4chanarchives.cu.cc site there are 3 main opinions
[*] It's ok, at least this way he will maintain and secure a long lasting future for the current and upcoming archives as well as a financial motivation to continue to improve current systems like the 4Archive and in the future Fuuka&Asagi or creating a custom and new CMS (he is an experienced PHP&MySQL, HTML&CSS, Laravel, developer and knows what he's doing).
[*] It's not ok, archivers should pay out of their pocket, regardless if the admin is an Europoor from the Balkans, if he want's to maintain a site like that he should pay everything on his own without getting anything in return!
[*] I don't care, as long as the archive is running, it doesn't matter for me if it has adds or no, I use uBlock/AdBlockPlus.

The administrator is working with different media advertisers to display NSFW adds only on NSFW boards and SFW adds on the SFW boards.

It's worth noting that the administrator of 4ChanArchives.cu.cc is one of the very few who replies in under 24hours to any DMCA notice or a friendly take-down notice (personal images and information, etc.) thus keeping a healthy website.

Furthermore, the administrator has been running locally as of about the middle of October 4Archive's CMS, which is based on lumen and has a lot of bugs, perhaps some of which caused the death of 4zip.org. He was using that system as a on-demand archiving in a closed beta, runing only on his dev mashine and not publicly. The threads will be added to the 4chanarchive.cu.cc DB [soon]
Since about 7. Nov. he has created a script (threads.php) which pulls all board names from the 4chan API (boards.json) and then accesses each board's archive.json to pull all threads and send them to his local installation.
As of 18. Nov, meaning about 10days of active automatic archiving, he has archived about 4mil. posts, 1mil images (500gb), 35k threads.

A block diagram of the archiving process is shown here:
https://i.imgur.com/WXcf4OY.png

A screenshot of the actual process in motion:
http://i.imgur.com/5YWxrMT.png (as you can notice it barely stresses the HDD with 5 simultaneous scripts running

Each thread is checked if it already exists in the DB, if it does - the script continues to the other one, going though all threads per board, going though each single board.
The sourcecode for the thread.php can be found here:
http://puu.sh/lq7lp/8343892db4.txt
If the thread does not exist in the DB, it's ID is written by the 4Archive's API and then via the 4Chan API  (threads.json) the entire thread is archived.
The images in the thread are send one by one as a link to imgur via the mashape's API. If it fails, the file is downloaded locally and uploaded again. If it uploads - the file is deleted from the local hdd, if the file did not upload, it is kept and another script (upload.php) attempts to upload it.
Both threads.php nd upload.php run 24/7 with a 30 minute pause when they are done.

Currently the administrator aims to archive all NSFW boards (you can see them in the source code) as well as all other boards, excluding /b/ and /trash/ since they don't have archive.json and /f/ since they cant be uploaded to imgur.

[Editor's note] This text has been originally written by the admin himself, better known as Bloo_SemiAFK (the name coming from a cartoon character and the lazyness of always changing his IRC nick from Bloo_AFK to Bloo, thus Bloo_SemiAFK came to be).