[GUI Plugin] FanFicFare

[ownedbycats]

It's working for me, but slow.

[mimicxz]

Originally Posted by jesscat

Ah, I didn’t see that, thanks! The archive itself and stories were loading for me with no problem so I didn’t think to look. Yes I’ll try again later and see if that solves the issue.

I found that the accuracy of Google Translate Free called by FFF has dropped a lot.
There are many words that are translated incorrectly, which seems to happen when LLM is used to split the words into tokens, not the single word..
This does not appear in the web translate version. Is there a way to fix this?

Regards

[readx]

literotica com changed their german and portuguese sites to https

Moderator Notice
links deleted

Could FFF please be updated to reflect the change.
Thanks

[JimmXinu]

Originally Posted by mimicxz

I found that the accuracy of Google Translate Free called by FFF has dropped a lot.
There are many words that are translated incorrectly, which seems to happen when LLM is used to split the words into tokens, not the single word..
This does not appear in the web translate version. Is there a way to fix this?

Are you in the correct thread? FFF doesn't call Google Translate.

[booster-t]

Originally Posted by jesscat

... Today when I tried [AO3], I got this 525 server error, which is not the 403 others have received. Nothing has changed in calibre or FFF configurations on my end, and I am up to date on FFF and calibre versions. Any suggestions? I'm getting this for every story I try to download.

I'm having the same issue PLUS the fetching operation takes forever now.

Stephen

[ovillo]

for the last day it's been basically impossible to download anthologies from Ao3 due to those 525 errors

[JimmXinu]

New Test Version Posted

2025-02-13
- adapter_literotica: http->https
- adapter_literotica: Site changes for non-www domains.

Originally Posted by readx

literotica com changed their german and portuguese sites to https

literotica has 9 sub domains ('www','german','spanish','french','dutch','italia n','romanian','portuguese','other') that are all treated the same.

FFF used to use http or https, whichever it was given in the story URL. Changing that to switch http to https across the board is easy, and a quick check does show https works with all the known domains.

OTOH, it looks like all domains other than www have different HTML now.

I've tried to fix it, but I don't read that site, especially in other languages, so my test set was fairly small.

[readx]

Thanks for the Test Version, works great.
The two subdomains are the only ones listed as examples in the SupportedSites on github. So I didn't try the other ones.

[steltek]

Originally Posted by booster-t

I'm having the same issue PLUS the fetching operation takes forever now.

Stephen

Originally Posted by ovillo

for the last day it's been basically impossible to download anthologies from Ao3 due to those 525 errors

This is all Cloudflare related. I've seen all the same issues with both these type errors and the download delays fetching metadata, both before and after A03's database maintenance. In fact, I've even had some fics throw "Unknown" errors as well.

The same fics will immediately download if I activate my VPN service and download them through a different IP address (which, I routinely don't do, using it only for testing purposes to ensure I don't have some other problem, in order to keep my VPN IP from getting blacklisted by Cloudflare). Overall, I've found Cloudflare on A03 to be very sensitive, and I don't consider myself a huge volume downloader (I spread 4-10 fic updates out over an 18 hour period each day).

@JimmXinu, out of curiosity, on A03 updates does FFF just update by downloading new chapters, or does it re-download the entire fic?

[JimmXinu]

Originally Posted by steltek

@JimmXinu, out of curiosity, on A03 updates does FFF just update by downloading new chapters, or does it re-download the entire fic?

## AO3 offers a page to download the entire work at once.  This can
## save a lot of network traffic if there are many chapters.
## True by built-in default.
#use_view_full_work:true

You can turn it off with use_view_full_work:false.

No, there isn't a way to differentiate between new downloads and updates.

[steltek]

Originally Posted by JimmXinu

## AO3 offers a page to download the entire work at once.  This can
## save a lot of network traffic if there are many chapters.
## True by built-in default.
#use_view_full_work:true

You can turn it off with use_view_full_work:false.

No, there isn't a way to differentiate between new downloads and updates.

Thanks for that, as it lines up with my suspicions as to how FFF was working on A03.

[ownedbycats]

I get 525 on regular download.

I see this: https://developers.cloudflare.com/su...ndshake-failed

Full or Full (Strict) SSL is set in the Overview tab of your Cloudflare SSL/TLS app.

Full : Cloudflare matches the browser request protocol when connecting to the origin. If the browser uses HTTP, Cloudflare connects to the origin via HTTP; if HTTPS, Cloudflare uses HTTPS without validating the origin’s certificate. This mode is common for origins that use self-signed or otherwise invalid certificates.
Full (strict) : Similar to Full Mode, but with added validation of the origin server’s certificate, which can be issued by a public CA like Let’s Encrypt or by Cloudflare Origin CA.

Can anything done about it on FFF's side if this?

[Lys]

I tried to update a single fic (with/without VPN) from AO3 and I got 525 error for both cases, as well.

Yesterday I managed to run the update for 5/6 fics at once without errors (the whole process was just slow).

[Anyssia]

If I'm not messing up, I use this under [archiveofourown.org] in personal.ini to make a ToC.

## AO3 chapters have 'date' available for each chapter.
## These can be used with custom output (see
## https://github.com/JimmXinu/FanFicFare/wiki/CustomOutput ) or with
## chapter_title_*_pattern settings.
## Examples for html & epub:
#<html>
#tocpage_entry:
# <a href="#section${index04}">${chapter}</a> ${date}<br />
#<epub>
tocpage_entry:
 <a href="file${index04}.xhtml">${chapter}</a> ${date}<br /><br />

It works for chaptered fics, but does anyone knows if there is a way to force Calibre/FFF to make a ToC even for one-shot fanfics, please?


(also, +1 with a 525 error on anthologies)

[Subtext]

I finally managed to update my anthologies by increasing the "slow_down_sleep_time" in ini, it takes ages to start and finish but I didn't get any 525 errors!