[GUI Plugin] FanFicFare

[ownedbycats]

In-built function, sorry. The story that updated is just a bit under 200 chapters so that would make sense.

I didn't try downoading with FFF - would've just got a 403. The RSS feed is dead too, lol.

[nan1923]

Originally Posted by JimmXinu

I would suggest not trying too much with FFF right now. We don't want to be categorized as part of the problem.

ok thanks, I just tried it once for a fic and once for metadata only, didn't know that cache isn't working for ao3.
Maybe write that also on the first page of this forum?

[ownedbycats]

Note that some people have reported success with the browser cache method. I got an error when I tried but may have made a mistake. It worked for me (though I had to clear the cache first).

[shinykari]

From Reddit, when asking AO3 support about FFF:

We won't have any information about that for a while, including how much we're going to keep routing through Cloudflare - all traffic, some traffic, just during high traffic times, just when things look sus? We don't know.

[ipaqi]

@JimmXinu, given the likely scenario that AO3 continues to use CloudFlare for the forseeable future, and given that historically, whatever proportion of users use Calibre with FFF wasn't enough to cause meltdowns, how much of an issue would it be to add flaresolverr support for AO3 downloads?

[ownedbycats]

I mentioned that in the github issue. Note that the CF-bypassing measures won't work in under-attack mode regardless, so it will likely depends on what happens after the DDoS is over.

[nan1923]

use_browser_cache:true
use_browser_cache_only:true
open_pages_in_browser:true

works for fics for me, but not for anthologies, then I get:

calibre, version 6.17.0
ERROR: Unhandled exception: <b>HTTPErrorFFF</b>:HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:'https://archiveofourown.org/users/login'

calibre 6.17 embedded-python: True
Windows-10-10.0.19045-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19045')
Python 3.10.1
Windows: ('10', '10.0.19045', 'SP0', 'Multiprocessor Free')
Interface language: en_GB
Successfully initialized third party plugins: DeDRM (10, 0, 3) && Count Pages (1, 13, 0) && EpubMerge (2, 15, 0) && EpubSplit (3, 6, 0) && FanFicFare (4, 24, 0) && Favourites Menu (1, 3, 0) && Find Duplicates (1, 10, 8) && Generate Cover (2, 3, 2) && Job Spy (1, 0, 238) && Modify ePub (1, 8, 1) && Quality Check (1, 13, 4) && Reading List (1, 15, 1)
Traceback (most recent call last):
File "calibre_plugins.fanficfare_plugin.fff_plugin" , line 944, in update_anthology
File "calibre_plugins.fanficfare_plugin.fff_plugin" , line 686, in get_urls_from_page
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\geturls.py", line 44, in get_urls_from_page
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\adapters\base_adapter.py", line 459, in get_urls_from_page
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\adapters\adapter_archiveof ourownorg.py", line 593, in before_get_urls_from_page
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\adapters\adapter_archiveof ourownorg.py", line 143, in performLogin
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\requestable.py", line 102, in post_request
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\base_fetcher.py", line 124, in post_request
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\cache_basic.py", line 122, in fetcher_do_request
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\decorators.py", line 102, in fetcher_do_request
File "C:\Users\leono\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\cache_browser.py" , line 97, in fetcher_do_request
fanficfare.exceptions.HTTPErrorFFF: HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:'https://archiveofourown.org/users/login'

and for long fics: Browser Cache Failed to Load with error 'unpack requires a buffer of 4 bytes'

images are also not included, but for the rest it seems to work for now

How would I get Flaresolver to work, after under-attack mode is over and ao3 flaresolver support would be added (or for ff.net)?

[ownedbycats]

Yeah, that looks like a login-restricted story. POST isn't cached.

Flaresolverr from what I remember you enabled it in personal.ini, then downloaded the binary and ran it before updating a fic.

[nan1923]

Originally Posted by ownedbycats

Yeah, that looks like a login-restricted story. POST isn't cached.

Flaresolverr from what I remember you enabled it in personal.ini, then downloaded the binary and ran it before updating a fic.

The series is not login restricted, so that can not be it

Do I run Flaresolverr from commandline then (windows)?

[ownedbycats]

It was command-line. I don't recall it needing any user input -- FFF just passed everything to it. But my memory isn't the best, so I may be mistaken on this.

[nan1923]

Originally Posted by ownedbycats

Yeah, that looks like a login-restricted story. POST isn't cached.

Flaresolverr from what I remember you enabled it in personal.ini, then downloaded the binary and ran it before updating a fic.

Solved: for anthologies and restricted works:

logged in in browser and delete username and password in personal.ini

[nan1923]

Originally Posted by ownedbycats

It was command-line. I don't recall it needing any user input -- FFF just passed everything to it. But my memory isn't the best, so I may be mistaken on this.

ok, thanks.
I'll try it the next time I download from ff.net

[ownedbycats]

Originally Posted by nan1923

Solved: for anthologies and restricted works:

logged in in browser and delete username and password in personal.ini

for future reference, you can put two ##s at the beginning of a line to comment it out

[JimmXinu]

I reiterate: I'm not putting significant effort into finding/creating/documenting solutions for AO3 on FFF until the situation has stabilized. I expect that to be a matter of days, not hours.

My personal opinion (based only on what I've seen publicly) is that donation funded AO3 is much more likely to return to a point downloaders can work than ad funded ffnet was.

But obviously it's not going to be a priority when basic services are still being impacted.

I urge restraint for all users--now is not the time to being hammering the AO3 servers.

[Lys]

I just tried to update one (1) fic from AO3 through FFF and the update went through correctly (giving me the expected return error: "no chapters to be updated, fics already has xx chapters), and it didn't trigger cloudflare like it did yesterday.

I'll wait some days more before trying to update more fics at once, but hopefully, everything is going back to normal