configurable "outdated" threshold for manga
better outgoing proxy signature
updating every 12hrs is more than enough
not-so-secret sauce proxy
Until they're on to us again I guess
cope with CF failures by refreshing session
Revert "Revert "update deps""
This reverts commit 52b798f80160c4df719863687281dc54f9f8f9fe.
install poetry from pipx; let poetry manage venv
To work around weird versioning issue:
Command ['/home/build/venv/bin/pip', 'install', '--no-deps', '/home/build/.cache/pypoetry/artifacts/cd/da/a5/4cfa20f311002e7588045a07491e292e7fb819fcc777144055b7c7ba89/MarkupSafe-1.1.1-cp37-cp37m-manylinux2010_x86_64.whl'] errored with the following return code 1, and output:
MarkupSafe-1.1.1-cp37-cp37m-manylinux2010_x86_64.whl is not a supported wheel on this platform.
Revert "update deps"
This reverts commit 2521a2d14e39b431f73c2ce0894143c8afc900ef.
bypass mangasee's cloudflare protection
show mangasee titles first
Stopgap measure until I actually implement the new mangadex API.
remove prints & outdated docstring/comment/annotation
mangasee with the new url fuckery
Mangasee may now use a different chapter link depending on the first
digit of its raw id. Therefore, we now need to use that raw id as our
unique `chapter.id`. This naturally required a migration script to
update existing records too.
Also disable mangadex updates because, you know, it's dead.
catch JsonDecodeError in title updater
fix mangadex cover link
It may not always have a `?` now.
I no longer need to manually mirror
also look for pages_alt when checking img url
fix extra blank space below spoiler