[GUI Plugin] FanFicFare

[MorbPtact]

Yeah, I have a man in the middle setup (a web filter). I installed it's certificate on the computer, but calibre and all of it's plugins have never worked with it.

Manually using use_ssl_unverified_context worked for that in the past, though.
Sorry to bother you with something that seemingly only affects me

[wildfire070]

I've got the latest test version installed and I think camoufox is working? Or at least it is for the handful of AO3 fic updates I just tested. Other than turning it on in our personal.ini is there anything else we need to do with it? Or is it just automatically configured through calibre?

[fanfictioneer]

The latest test version causes email download to hang for me (the zip in the RR issue works, and I could backport the new RR fix to it without having the same issue, so there might be something else, certificates or whatnot). Sorry for not providing any logs, but there was literally nothing in them about the issue. I also might have been impatient, but it didn't timeout after 10 minutes, so...

[JimmXinu]

Originally Posted by wildfire070

I've got the latest test version installed and I think camoufox is working? Or at least it is for the handful of AO3 fic updates I just tested. Other than turning it on in our personal.ini is there anything else we need to do with it? Or is it just automatically configured through calibre?

That's it.

We're taking advantage of the work Kovid's already put into Calibre to make Camoufox invisibly available.

Originally Posted by fanfictioneer

The latest test version causes email download to hang for me (the zip in the RR issue works, and I could backport the new RR fix to it without having the same issue, so there might be something else, certificates or whatnot). Sorry for not providing any logs, but there was literally nothing in them about the issue. I also might have been impatient, but it didn't timeout after 10 minutes, so...

It might be certificates. A number of certificates where reported compromised and the certifi python package updated accordingly, which I included in FFF.

FFF bundles its own copy of certifi because of the number of users who are (were?) stuck on old calibre or OS versions. I'm not entirely certain it's needed anymore, but it needed more work to remove than just deleting it and I had other priorities so I just updated it.

[Elaine T]

I took Jimmy's advice and set a second browser to use solely for downloads on Ao3.


Now I've gotten one successfully, the others all fail with this error:
[WinError 2] The system cannot find the file specified: 'C:\\Users\\Elaine\\AppData\\Local\\Waterfox\\Prof iles\\ra4tiq7j.default-release\\cache2\\index'




Now when I checked what I'd put in for the file path what I see is:
browser_cache_path:C:\Users\Elaine\AppData\Local\W aterfox\Profiles\ra4tiq7j.default-release\cache2


The only difference is those extra back slashes. Where could they be coming from and how do I fix it?
I don't understand enough to know where to look for the answer, please help.

[JimmXinu]

The double \\ is an artifact of how python prints strings that would be escaped in code. It's not the issue.

I suspect that the browser cache has never been initialized. You probably need to use that browser on a few pages first so it creates the index structures.

[wildfire070]

Updated a batch of 20+ fics from email with Camoufox and so far so good. Haven't gotten a single 525 error. Fingers crossed it continues to run smoothly.

[JimmXinu]

FYI, there's been one report so far of images working worse with AO3 under camoufox.

Image failures aren't loudly reported by FFF because of how varied and common they can be.

[applegaa]

Originally Posted by JimmXinu

New Test Version Posted

2026-10-28
- Update bundled certifi to 2026.10.23
- Plugin only: use_camoufox option using Calibre recipes.py Browser.
- adapter_royalroadcom: Fix for dateUpdated in new UI, thanks VictorVow(#1445)
- adapter_royalroadcom: Increase default sleep time.

After I finished my nightly update, I noticed that I had a lot of stories where Last Updated was earlier than Last Read. (I set Last Read to Last Updated rather than the current date, so that shouldn't happen.)

Looking through it, the most common date is 17 Oct 2026, despite all of those stories having updated within the last 24 hours. However, I also found dates like 30 Oct 2023, 29 Oct 2024, and 22 Nov 2025. Those stories didn't even have a chapter released on those dates.

The only two that got the correct date only have 10 chapters. All of the rest had well over that.

I also added two new stories, with 13 and 25 chapters, and they got the correct dates.

I didn't notice until I was done, so I can't do anything with debug mode tonight. I'll plan to collect the logs when I run my updates tomorrow night.

[ownedbycats]

Note that AO3 is undergoing maintenance, so it won't work until its finished.

[JimmXinu]

Originally Posted by applegaa

After I finished my nightly update, I noticed that I had a lot of stories where Last Updated was earlier than Last Read. (I set Last Read to Last Updated rather than the current date, so that shouldn't happen.)

Maybe from this: royalroad: use last chapter date when JSON-LD dateModified is stale ?

Without knowing what site and story URLs you see this with, it's hard for me to even look at it...

[applegaa]

Originally Posted by JimmXinu

Maybe from this: royalroad: use last chapter date when JSON-LD dateModified is stale ?

Without knowing what site and story URLs you see this with, it's hard for me to even look at it...

Sorry, I thought I had included it was RoyalRoad.

I was going to wait and post an actual debug log tonight, but it makes sense that you could test and get the same dates. It was late and I didn't think about that. So, here are some examples along with the date from SavedMetaData:

https://www.royalroad.com/fiction/197033
<p><span class='label'>Updated</span>: <div class='metadata datetime' id='dateUpdated'>2026-10-17T02:21:06.442556+00:00</div><p>

https://www.royalroad.com/fiction/197028
<p><span class='label'>Updated</span>: <div class='metadata datetime' id='dateUpdated'>2026-10-17T02:33:24.782812+00:00</div><p>

https://www.royalroad.com/fiction/197038
<p><span class='label'>Updated</span>: <div class='metadata datetime' id='dateUpdated'>2026-10-17T02:29:25.652822+00:00</div><p>

https://www.royalroad.com/fiction/195137
<p><span class='label'>Updated</span>: <div class='metadata datetime' id='dateUpdated'>2026-10-04T02:42:37.417229+00:00</div><p>

https://www.royalroad.com/fiction/35372
<p><span class='label'>Updated</span>: <div class='metadata datetime' id='dateUpdated'>2025-11-22T02:37:34.805182+00:00</div><p>

[JimmXinu]

Originally Posted by ownedbycats

Note that AO3 is undergoing maintenance, so it won't work until its finished.

AO3 maintenance is in progress. We expect it to take at least 12 hours, but it may take longer. We will provide updates as necessary.

(emphasize mine)

Good heavens.

What are they doing that needs 12+ hours??

[JimmXinu]

Originally Posted by applegaa

Sorry, I thought I had included it was RoyalRoad.

I was going to wait and post an actual debug log tonight, but it makes sense that you could test and get the same dates. It was late and I didn't think about that. So, here are some examples along with the date from SavedMetaData:

Okay, I think I see it; has to do with chapter list pagination. This only affects RR's Legacy UI. The 1445 change already fixed it for the Redesign UI code.

I will apply the same sort of fix -- take oldest and newest chapter timestamps across all chapters as datePublished and dateUpdated instead of the existing code which takes them from first and last chapter on the first page.

I'll have a test version with this change out later today. In the meantime, it should work better if you change your account to the Redesign UI. FFF will not support both forever.

[applegaa]

Originally Posted by JimmXinu

Okay, I think I see it; has to do with chapter list pagination. This only affects RR's Legacy UI. The 1445 change already fixed it for the Redesign UI code.

I will apply the same sort of fix -- take oldest and newest chapter timestamps across all chapters as datePublished and dateUpdated instead of the existing code which takes them from first and last chapter on the first page.

I'll have a test version with this change out later today. In the meantime, it should work better if you change your account to the Redesign UI. FFF will not support both forever.

Thanks!

I only recently created an account on the site, and I didn't think to add the login to FFF. I can definitely do that.

EDIT: After adding my login information, I tested two stories that got the wrong date last night. One had a new chapter and the other I updated the metadata from the site. Both gave the correct date for Last Updated.