As part of the server migration announced here: https://wiki.bibanon.org/News/2021-04-11_Desuarchive_Migration

The Bibliotheca Anonoma has built two drop in replacements in Python to replace the aging FoolFuuka/Asagi archival stack. https://wiki.bibanon.org/FoolFuuka

* https://github.com/bibanon/neofuuka-scraper is in use at Desuarchive as part of this server migration. See the improved features over Asagi scraper in the repository.
* https://github.com/bibanon/ayase is a drop in replacement for the FoolFuuka frontend, check it out at our demonstration site: https://ayase.wakarimasen.moe. It is sufficient for non-ghostposting use, but we are still working on search and moderation tools and development help is appreciated.

Lastly, We hope to learn Rust to totally redesign the Asagi SQL schema. Two efforts are underway:
* https://github.com/miyachan/torako is a drop in replacement for the Asagi scraper. It is in testing at https://ayase.wakarimasen.moe .
* https://github.com/reasv/mitsuba is a full stack archive stack replacement and PostgreSQL schema redesign, most likely the best path forward past the aging Asagi schema.

If you'd like to help develop or plan to make the next Yuki.la, it is a tough road but we have the expertise to help set things up. Post below or contact us at:
irc.rizon.net #bibanon
https://matrix.to/#/#bibanon-chat:matrix.org
https://discord.com/invite/3jxxGDC

BTW if anyone knows any 4chan admins, please tell them to unblock or increase the Cloudflare limits on the desuarchive/rbt.asia and archived.moe scrapers. The method used to hold us over for the past year does not seem to be working well anymore and it is failing to archive threads periodically.

Relevant actions taken by archived.moe admins as FYI, we are also using the same temporary fix: https://archived.moe/talk/thread/14/#q141_200

This reveals that our time is up with the FoolFuuka/Asagi archiver stack. It has not had active development since the collapse of Archive.moe in 2016. It is too inefficient with bandwidth to function any further. It is not worth feeding both with additional RAM and resources if it is too inefficient with requests as well, the stack is already consuming 168GB RAM as it is. It is only a matter of time before the other archivers meet this fate too.

This is an unexpected development and it could take weeks if not months, but the C# .NET developer of hayden is working hard on it with massive reductions and huge improvements in efficiency and request limit compliance, such as RAM use reduction to 100MB, but his time is limited, we wish we could have bought some more time.

To anyone who can help, call up all C# .NET developers and skilled MySQL/Percona DBAs to try and bring the Hayden code up to scratch as a suitable drop in Asagi replacement. Once the scraper is replaced, we can also work together with Python developers to build a new frontend replacement for FoolFuuka as described in the previous thread. It is already demonstrably more efficient and accurate, however it is not fully tested and often hits deadlock issues. Using Hayden will allow us to consolidate our operations on s2.desuarchive.org instead of s1.desuarchive.org on a separate continent, immediately saving $90 a month and removing a Sword of Damocles by eliminating s1 which the previous admin (peace be upon his wrists) is likely to default on due to crippling medical bills.

There are some download reliability issues that need testing to be able to use in production, but we wish we had some more time before this happened.

https://github.com/bbepis/Hayden

In the future we would like to totally overhaul the FoolFuuka/Asagi stack with a total replacement for the sole use of Desuarchive, but a drop in Asagi replacement is crucial as the vast majority of other archiver admins such as archived.moe have lives to live and are unlikely to take up any SQL schema changes.

Feel free to drop by the chat to help brainstorm what can be done.

https://matrix.to/#/@bibanon-chat:matrix.org

https://discord.com/invite/3jxxGDC

It is helpful to read our previous thread on the topic as well: https://desuarchive.org/desu/thread/3894/

EDIT: Modified to clarify that FoolFuuka/Asagi, both the frontend, backend, and inefficient MySQL schema, are all to blame for the situation.

This post was modified by Desuarchive Administrator on 2019-12-07

>RIP Desuarchive ;_;
Don't do that to me again!

https://archive.org/details/desuarchive_db_201909

UPDATE IT

When will the Recaptcha system get improved? You could remove it completely or at least make it render before posting because as of now, this shit is retarded.
Better yet try adding a cooldown at least, like in 4chan, that should be pretty easy.

Is /qb/ gonna be archived here?

>Need some webms quick
>Go to desuarchive
>Go to /gif/
>Play one of the webms
>404s
>Can't play webms here like I used to
What happened to desuarchive? Is there an alternative to this?

hey guise why dont we just talk about animes here insted of 4chinz? normalfags wont find us here amirite

Anons, what's happening, why is yuki.la down, and desu was down too...

Is it possible to use regex expressions in the various search fields somehow? Specifically I want to search for file names that contain left or right square brackets, [ or ], but they just get ignored. Is there a way I can do this? Regex doesn't seem to be working either. Thanks.

Archive 4plebs shows the number of replies on thread opening posts. Very useful feature. Can desuarchive look into adding that as well?