[GUI Plugin] FanFicFare

[ThreeLizards]

Yes, I did have it set to -1. What do I set the bowser cache to?

Alright, I tried it with the 4 and it keeps timing out or something, an error is thrown

[culytera]

Originally Posted by ThreeLizards

Yes, I did have it set to -1. What do I set the bowser cache to?

Alright, I tried it with the 4 and it keeps timing out or something, an error is thrown

Clear your browser's cache then try another download of the same work that threw an error.

[ernand]

Does anyone know if the Ao3 fic update got fixed?
I have been using the cache method since it stopped working, but I am now having issues downloading chapters with images.

The chapter gets downloaded, but it can't download the images. My browser tries to open each image, but it stops after 4 images have been opened.
https://i.imgur.com/o091hOW.png

This is the fic I am trying to download:
https://archiveofourown.org/works/65...iew_adult=true

These are the settings I have for AO3:
##fixes for the website
use_archiveofourown_gay:false
use_browser_cache:true
use_browser_cache_only:true
browser_cache_age_limit:4.0
open_pages_in_browser:true
slow_down_sleep_time:2

edit: question, does FFF "downscale" the images in the fics? Just noticed the renaming FFF adds to the images and the extension, and that the resolution is different from the source on the fic page.

[ThreeLizards]

Oh! Deleting the cache worked! Thank you! Guess I'll need to do that every so often

[texasnightowl]

Originally Posted by ernand

Does anyone know if the Ao3 fic update got fixed?
I have been using the cache method since it stopped working, but I am now having issues downloading chapters with images.

The chapter gets downloaded, but it can't download the images. My browser tries to open each image, but it stops after 4 images have been opened.
https://i.imgur.com/o091hOW.png

I've had issues even with the previous alternate domain method and stories with lots of images. I would usually end up stopping the job and then editing my personal.ini to omit images for the particular stories.

example:
[https://archiveofourown.org/works/#####/chapters/#####]
include_images:false

So I don't know if browser method is any worse than previously because if a story had lots of images I had issues anyway.

if the images are truly necessary to the story, I would probably try just downloading directly from AO3 website and not fff.

[bigwoof]

Originally Posted by vorm

Here is a zip with the plugin and extension source code. There is a readme of how to install/use it also. Enjoy.

Thank you! This works very well!!

[JimmXinu]

Originally Posted by ernand

The chapter gets downloaded, but it can't download the images. My browser tries to open each image, but it stops after 4 images have been opened.
https://i.imgur.com/o091hOW.png

imgur and other large image hosting sites have had various protections against direct or 'excessive' access even longer than other sites. Notice how if you use this image link in browser, you don't get the image, you get a page containing the image.

FFF has some options for helping with that, but they won't help while using BrowserCache.

Not sure why you quoted an imgur image, the linked story doesn't have any. In that case, it's the dropbox hosted images that are marked 'no-cache' failing.

I don't have a good solution for that. You could try using a browser extension to force caching, but you need to understand what you're doing. See #1312

I've been good using direct access on AO3 lately.

As for the opens-four-and-stops, that's a BC feature to not open a billion tabs if things aren't working.

Originally Posted by ernand

edit: question, does FFF "downscale" the images in the fics? Just noticed the renaming FFF adds to the images and the extension, and that the resolution is different from the source on the fic page.

When FFF came about, eInk book readers were much more limited, large images filled their storage and could slow or crash rendering. Non-jpgs didn't work. Even now the screen resolutions are far smaller than other devices.

By default, FFF converts images to jpg, removes transparency, and resizes to fit with 580x725.

There are several FFF settings about images, search for 'image' and 'img' in plugin-defaults.ini.

Set no_image_processing:true under [epub] if you want no processing at all.

[wildfire070]

For the logpage, is there a way to limit it to the most recent 1 or 2 updates?

[JimmXinu]

Originally Posted by wildfire070

For the logpage, is there a way to limit it to the most recent 1 or 2 updates?

No.

Logpage handling is pretty primitive--FFF doesn't actually parse the HTML log completely. Because it's configurable, it's hard to make assumptions about what's in there.

[ernand]

The Imgur link was to show the inside of the epub after it updated (FFF would update the fic but fail to fetch the images of the updated chapter). It shows the broken pictures and the text it used inside the img tag.

But thanks for the information.
I "fixed" it by downloading the epub version from AO3, then transferring the images using the Calibre editor. The image resolutions are not the same as the OG (4000x2100px), but they are twice as big as what FFF provided. (The fic I downloaded is a comic, so the FFF image processing made it hard to read the handwritten dialogue.)

[DNSB]

Originally Posted by ernand

The Imgur link was to show the inside of the epub after it updated (FFF would update the fic but fail to fetch the images of the updated chapter). It shows the broken pictures and the text it used inside the img tag.

The problem is that if you used MobileRead attachments, the images are here and will still be here later plus you do not have the issue where Imgur blocks third-party access to their images (you can open the image in a local web browser but not using a third party to access the image).

Not to mention that some countries are not even able to access Imgur (the UK for one example).

[ernand]

A heads up. I just tried and was able to update Ao3 without using the browser Cache.
Seems it's back to normal.

[Elaine T]

Originally Posted by ernand

A heads up. I just tried and was able to update Ao3 without using the browser Cache.
Seems it's back to normal.

I had to change my sleep time setting to 6 and then I could stop using the browser cache. Since I did that I haven't had problems.

[JimmXinu]

New Version Released

Version 4.60.0 - 2026-08-01
- Update translations.
- base_xenforo2forum_adapter: When capitalize_forumtags don't capitaloize right after numbers. 1990s 1st, 2nd, etc
- base_otw_adapter: Save and use if served full work initially
- base_otw_adapter: Save a network req if need to login.
- adapter_asianfanficscom: Fixes for major site changes
- base_otw_adapter: Don't require open_pages_in_browser to skip login.
- base_xenforo2forum_adapter: Look both forward and backward when post not found in reader page. #1395
- adapter_sofurrycom: Revisit login url after 404, thanks dbhmw #1385
- Add option keep_img_tags - keep <img> tags when include_images:false
- adapter_sofurrycom: More fixes for site change, thanks, dbhmw #1386
- adapter_sofurrycom: Fixes for site change, thanks, dbhmw #1384 and #600
- adapter_test1: Handle bool settings in [teststory:] better
- INI Snippet: Repopulate the combobox in AddNewDialog() when shown in case of library change.
- adapter_pmdfanfiction: Fix downloading chapters for stories with chapter groups - Thanks, BlizzardBricks
- Better error message for open_pages_in_browser_tries_limit exceeded
- Add avif image type to image processing.

[Tharos]

The SOL admin stated the following in a forum post:

Whenever a reader accesses a story, the system sets a cached bit of info containing the reader's id, and the story's id for 15 seconds. It only allows accesses to this story while the cache is valid.

Every time there is a new story/chapter request, the delivery system checks for this cached data and if it exists, and the story id is different, then it throws the error, otherwise, it refreshes the cache and delivers the requested text.

Someone asked why there are so many 503 error messages.

Does it make sense here to increase the `slow_down_sleep_time` to 15 seconds? Within the same story, that’s not really necessary. But if I’m updating more than one story, then I suppose it is. Or am I misunderstanding something here?