Donations to the archive would be appreciated to help fund our server hardware & storage drives. We are looking for developers to help build new software and archives, discuss here.
After a painful few weeks, the brand new server is installed and running. Threads load much faster and (in a few days) images will be served at a speed yet to be seen on desuarchive.
Please use this thread to report any issues you may encounter. Also be aware that we are importing the missing posts & images from our neighbor archives. Expect those to appear in a few days.
The image repost stats for /r9k/ changed suddenly. Most of the images repost counts got bumped up. The numbers listed don't match the number returned when that hash is searched, not sure if this is to be expected.
I'm confident that images 4-20 are way off and shouldn't be there, I think #3 is inaccurate as well. The rest seem fine at least in terms of order. Here is a screenshot of the page from Feb 6th 2017 to compare to.
Our domain registar terminated our entire account due to CP. Instead of attempting to contact me to get it resolved, they have locked me out of the account and are holding the domain hostage. I am waiting for a response from their legal team, but I am doubtful that this site will ever run under desustorage.org again.
All data is here and new images are still being pulled. Images will be down until we can get everything back together.
Please be sure to follow us on Twitter so you can stay in the loop if something like this happens again.
I am a android user and am constantly getting redirected to scam sites. And recently had a site claim to have put randsomware on my phone. Is everyone getting this, and why are the adds even allowed.
Here's a few suggestions on how to better deal with CP for you
>ban certain thumbnail hashes a lot of the material posted for shock value is the same stuff, people usually get it from that one German guy on /sp/ or from /b/. By implementing a system which automatically removes images which are known to be CP, some burden on the moderators can be avoided. Since CP spammers might try to evade such measures (especially since 4chan already does md5 filtering), perceptual hashing might be a better solution. There are existing libraries for perceptual hashing, and basic methods of it that have a moderate amount of success are fairly easy to implement within an afternoon, if you know what a DCT is. Also, this lets you simply store hashes of banned images, which means you don't need to store any of the illegal material to actually detect it.
>do not show images of deleted posts on certain high-risk boards until manually approved by a moderator this one is a bit extreme, but if there are boards with a known issue of some user repeatedly spamming CP (hi /sp/!), a temporary (or permanent?) restriction could be imposed which does not show images of deleted posts until a moderator approves them. It might be risky, but it's better than losing the entire archive due to a few shitheads. This obviously increases the burden on moderators significantly, but also means that you're on the safe side if you can't keep up with how many posts you can moderate.
>develop a small browser addon for 4chan which also sends a notification to relevant archives if a user reports a post on 4chan as containing illegal material might be something to bring up with the 4chan X developers and the foolfukka devs. A standardised API to make it easier for users to make sure CP is reported in a timely manner to all affected places could lead to more reports.
