[GUI Plugin] FanFicFare

[DeviOT]

Originally Posted by ovillo

devi, are you using browser cache?

I'm not. Unless I misread, it looked like I couldn't login with fanficfare when using browser cache. This wouldn't really work for me, given that some fics on ao3 are locked to guests.

[JimmXinu]

If you're using Browser Cache, you just need to have logged in manually in the browser.

[DemiGraceling]

How do I get the tags to go into my additional_tags column?
My wattpad section:

[wattpad.com]
use_basic_cache:true
extra_titlepage_entries: language, reads, genre
extra_valid_entries: language, tags, reads, ships, genre
include_in_genre: tags
# Add comma separators for numeric reads. Eg 10000 becomes 10,000
add_to_comma_entries:,reads
keep_in_order_ships: true	


## number of seconds to sleep between calls to the story site.  There
## are reports that sound like site throttling without it.
slow_down_sleep_time:2


extra_titlepage_entries: reads, genre
extra_valid_entries: reads, genre
datechapter_format:%%Y-%%m-%%d %%H:%%M:%%S

## You can set the 'dateUpdated_method' to either:
## - 'modifyDate': This will keep the current behavior, where the
## update date corresponds to any modification made to the content.
## - 'lastPublishedPart': This will set the update date to
## the date of the last published chapter.
dateUpdated_method: modifyDate

# Add comma separators for numeric reads. Eg 10000 becomes 10,000
add_to_comma_entries:,reads


custom_columns_settings:
    reads=>#hits 
    tags=>#additional_tags
    genre=>#additional_tags

[JimmXinu]

Originally Posted by DemiGraceling

How do I get the tags to go into my additional_tags column?
My wattpad section:

...

custom_columns_settings:
    reads=>#hits 
    tags=>#additional_tags
    genre=>#additional_tags

You're overwriting tags with genre. Use the 'a' flag to indicate to add to the column instead of overwriting:

custom_columns_settings:
    reads=>#hits 
    tags=>#additional_tags
    genre=>#additional_tags,a

See comments in defaults.ini.

[ernand]

For some reason, when I download from FFN, the text is set to center instead of left-aligned.
For some reason, this line is set on the div of the chapter:
<div align="center" class="storytextp" id="storytextp" style="padding:0 0.5em 0 0.5em;">

This only shows up on FFN, not when I download from AO3 or RR.

Here is my personal.ini for FFN and epub settings.

Spoiler:

## This is an example of what your personal configuration might look like. Uncomment options by removing the '#' in front of them.

[defaults]
## [defaults] section applies to all formats and sites but may be overridden at several levels. See https://github.com/JimmXinu/FanFicFare/wiki/INI-File for more details.

## windows:
### Chrome:
browser_cache_path:C:\Users\fefue\AppData\Local\Go ogle\Chrome\User Data\Default\Cache\Cache_Data

## Some sites also require the user to confirm they are adult for adult content. Uncomment by removing '#' in front of is_adult.
is_adult:true

## Don't like the numbers at the start of chapter titles on some sites? You can use strip_chapter_numbers to strip them off. Just want to make them all look the same? Strip them off, then add them back on with add_chapter_numbers. Don't like the way it strips numbers or adds them back? See chapter_title_strip_pattern and chapter_title_add_pattern in defaults.ini.
#strip_chapter_numbers:true
#add_chapter_numbers:true

## Some sites/authors/stories use several br tags for scene/section breaks.
## When set replace_xbr_with_hr:X will cause FFF to search for X or more consecutive br tags and replace them with br br hr br.
#replace_xbr_with_hr:3

## Some readers don't show horizontal rule (<hr />) tags correctly.
## This replaces them all with a centered '* * *'. (Note centering doesn't work on some devices either.)
#replace_hr: false

## Some sites/authors/stories use br tags instead of p tags for paragraphs. This feature uses some heuristics to find and replace br paragraphs with p tags while preserving scene breaks.
#replace_br_with_p: false

## Some sites/authors/stories (notably AO3/OTW) add empty p tags where they aren't intended by the author during document upload and not all authors know how/take the time to fix it. This feature removes all "empty" <p> tags, ie, those containing only whitespace or <br> tags. Literally: <p[^>]*>\s*(<br/>)*\s*</p>
remove_empty_p: true

[epub]
## Include images from img tags in the body and summary of stories.
## Images will be converted to jpg for size if possible. Images work in epub format only. To get mobi or other format with images, download as epub and use Calibre to convert.
## true by default, uncomment and set false to not include images.
include_images:true

## Quality level to use when converting images to jpg. Range is 0-100, reasonable values likely to be in the range 70-95.
jpg_quality: 100

## If set false, the summary will have all html stripped for safety. Both this and include_images must be true to get images in the summary.
## true by default, uncomment and set false to not keep summary html.
keep_summary_html:true

## If set true, and there isn't a specific cover image, the first image found in the story will be made the cover image. If keep_summary_html is true, images in the summary will be before any in chapters.
## true by default, uncomment and set false to turn off
make_firstimage_cover:true

## Some attributes cause problems for EBook readers. By default,
## FanFicFare will remove all attributes except the ones specified from all tags. (The only exception is that <img> tags will also keep src, alt and longdesc attributes. data-orighref is used by internalize_text_links to preserve links when chapters are inserted.)
## Example: To add 'style', 'title' and 'align' to the list to keep, in your personal.ini [defaults] put:
add_to_keep_html_attrs:,style,align
keep_html_attrs:href,name,class,id,colspan,rowspan ,data-orighref


## Most common, I expect will be using this to save username/passwords for different sites. Here are a few examples. See defaults.ini for the full list.

[www.fanfiction.net]
##use_basic_cache:true
use_nsapa_proxy:true
use_cloudscraper:false

## Errors on more common during long downloads. This way, at least the chapters the worked are saved. Often running an update will
## fix the error chapters.
continue_on_chapter_error:true

## browser cache will only be used if use_browser_cache:true and ONLY
## for a few sites. Requires a browser_cache_path set in [defaults].

## use_browser_cache_only:true prevents FFF from falling through to request from the server when a page isn't in the browser cache.
## You can turn this on to be sure you're only using the browser cache.
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

## fanfiction.net's 'cover' images are really just tiny thumbnails.
## Set this to true to never use them.
#never_make_cover: false

## exclude fanfiction.net imageu (old user vs story detect) and default user (d_60_90)
cover_exclusion_regexp/imageu/|d_60_90\.jpg)

## April 2015, ffnet changed their story and user pictures urls to be the same. Now the only way to know if the story image is really the author image is to go get the author image and check.
skip_author_cover:true

## fanfiction.net is blocking people more aggressively. If you download fewer stories less often you can likely get by with reducing this sleep.
slow_down_sleep_time:12

## sites are sensitive to too many hits. Users are sensitive to long waits during the initial metadata collection in the foreground.
## When used, these settings will speed up metadata downloads in the
## foreground linearly.
tweak_fg_sleep:true
min_fg_sleep:4.0
max_fg_sleep:12.0
max_fg_sleep_at_downloads:4

## Extra metadata that this adapter knows about. See [archiveofourown.org]
## for examples of how to use them.
extra_valid_entries:reviews,favs,follows

## ffnet uses 'Pairings', not 'Relationship', stating they don't have to be romantic pairings.
ships_label:Pairings

## Date formats used by FanFicFare. Published and Update don't usually have time, but they do now on ffnet.
## See http://docs.python.org/library/datet...ptime-behavior
## Note that ini format requires % to be escaped as %%.
#dateCreated_format:%%Y-%%m-%%d %%H:%%M:%%S
datePublished_format:%%Y-%%m-%%d %%H:%%M:%%S
dateUpdated_format:%%Y-%%m-%%d %%H:%%M:%%S

## ffnet used to have a tendency to send out update notices in email before all their servers were showing the update on the first chapter. It generates another server request and doesn't seem to be needed lately, so now default it to off.
check_next_chapter:false

## ffnet sometimes doesn't update the metadata on the first chapter immediately. meta_from_last_chapter:true will instruct the adapter to take the metadata from the last chapter instead of chapter 1.
## It can generate another server request and usually isn't necessary, so it defaults to off.
meta_from_last_chapter:false

[JimmXinu]

Originally Posted by ernand

For some reason, when I download from FFN, the text is set to center instead of left-aligned.
For some reason, this line is set on the div of the chapter:
<div align="center" class="storytextp" id="storytextp" style="padding:0 0.5em 0 0.5em;">

This only shows up on FFN, not when I download from AO3 or RR.

...

For some reason, ffnet has that align=center attribute and then overrides it in CSS. No idea why, but it's been that way for at least a decade. Probably 2 by now.

You are seeing it in your FFF output because you have setting:

add_to_keep_html_attrs:,style,align

You can:

1. Remove align from add_to_keep_html_attrs;
2. Move the add_to_keep_html_attrs setting out of [epub] and put it under each [site] you want it for instead, or;
3. Apply the same CSS 'fix' that ffnet does:

   [www.fanfiction.net]
   add_to_output_css:
    .storytext {
      text-align: left;
    }

[JimmXinu]

New Version Released

Version 4.61.0 - 2026-09-01
- Update translations.
- Don't confuse usecache with referer - position vs named params.
- adapter_potionsandsnitches: http->https Closes #1404
- Clear INI Snippet setting between Add URL dialog calls.
- base_xenforo2forum_adapter: Fix non-first post TOC stories using BrowserCache
- base_xenforo2forum_adapter: Reader mode--don't try pages < 1
- Remove python2 support code
- Update included plugin dependencies to Python 3.8 (Calibre 5)

[Chrystalline]

This might be crazy, but, is there a way (or could there be a way) to run story links against the library and blocklist without actually attempting any downloads? Like, input a large list of links and get back a list of only the links that are not found in the library or in the blocklist? I'm not sure which would be more feasible: outputting a text/csv of links to later download, or just adding empty books to the library with no files or metadata other than storylink so I can later select small batches (or more realistically these days, one at a time) to Update Always. I suppose adding as empty books has the advantage of being in the library to skip if another recommendations page includes the same link again.

I get lists of links from a variety of methods/sources, and I used to run them in smaller batches with super high sleep times and Skip-If-Found, but with the recent server blocking, that's unpredictable, though sometimes I can still get through. If there were a way to filter the lists first without hitting the servers, I'd love to do that.

[JimmXinu]

You mean like the existing Reject List feature?

Open FFF config, look in the lower right corner of the General tab.

[Elaine T]

I have a new error from Ao3. Is it something I can control, or should I just wait for it to get fixed on their end? If it matters, I was trying to update an anthology.


calibre, version 9.13.0
ERROR: Unhandled exception: <b>FailedToDownload</b>:Failed getting login token from token_dispenser.json

[Chrystalline]

Originally Posted by JimmXinu

You mean like the existing Reject List feature?

Open FFF config, look in the lower right corner of the General tab.

I mean comparing a list of links copied from recommendations pages against the existing Reject List and the Library database as if downloading, but without actually doing the download, so as to filter out redundant links without hitting the site servers. I already have a Reject List, but I do not see a way to compare links against that list without doing the downloads.

I know the Reject List can be viewed, and I know the Library can export columns to CSV, but I don't know how to filter the compiled links without just downloading, which obviously has to be done in smaller batches to avoid hammering servers. If I could filter them all first, it would save time on download attempts.

[JimmXinu]

Originally Posted by Chrystalline

I mean comparing a list of links copied from recommendations pages against the existing Reject List and the Library database as if downloading, but without actually doing the download, so as to filter out redundant links without hitting the site servers. I already have a Reject List, but I do not see a way to compare links against that list without doing the downloads.

For most cases, a story URL being in FFF's Reject List does prevent hitting the site.

The only case where it doesn't, is if the link you are getting and the canonical story link saved in the Reject List are different. And even then, there's some story URL normalization code for common sites. Eg, ffnet stories with and without story title in the URL.


To do exactly what you ask: Find all the rejects (or non-rejects) without trying to do any downloads (a sort of 'dry run download'), using FFF specifically, my only idea (which is not a good idea) would be to download the list with networking turned off and look at which failed due to network failure and which were Rejected.

Unless other users speak up, I don't see a 'dry run download' feature being used commonly enough, especially vs how often it would confuse users and I'd have to explain it.

But I would be willing to add a 'Download Reject List to CSV' feature, if you want it.

[whiteowl]

The SB/SV forums do use spoiler tag. I see three options for them in defaults.ini, but they do not do what I want.

I would prefer to have a text/image under the spoiler button as an open text, surrounded with a before-after texts. Something like

***** spoiler: a button title
A text under the spoiler
***** spoiler: complete

Currently, if we have all three options (remove_spoilers, legend_spoilers, details_spoilers) If all these options are false - the spoiler is shown as a button, which still can be pressed but it does not do anything.

The remove_spoiler, simply removes spoiler.

The legend_spoilers and details_spoilers create a box around the "spoiler", but if author hid an image under it - it all become very ugly...

So, none of the options do it "pretty" right now.

What I'd like to have is a text (not a button!) above the spoiler and (optional) footer, marking conclusion of the spoiler.

Is it doable?

[JimmXinu]

Originally Posted by whiteowl

...

What I'd like to have is a text (not a button!) above the spoiler and (optional) footer, marking conclusion of the spoiler.

Is it doable?

I would try picking one of legend_spoilers or details_spoilers and doing something like this in CSS:

.bbCodeSpoilerContainer:before {
    content:"Some text before"
}

.bbCodeSpoilerContainer:after {
    content:"Some text after"
}

Experiment in Calibre's Edit book until you have CSS you like, then add it to FFF's add_to_output_css setting.

[whiteowl]

It can work for a fully textual spoilers. But not for a spoiler which contain an image.

The legend_spoilers and details_spoilers create a box around the "spoiler". The issue of the box is that the calibre's Viewer is trying to show that box in one go, but fails (since the image is big). So it shows the top line of the box on one page, the image scaled to page on another page and bottom line of the box on the third page.

... wait. After thinking like that, I realize that my primary issue is that the "spoiler" box is actually split into three pages. So I did some playing with CSS. And resized the spoiler box, as well as an image inside it. My current settings are:

[base_xenforoforum]

legend_spoilers: true

[base_xenforoforum:epub]

add_to_output_css:
 .bbCodeSpoilerContainer { border: none; padding: 2px; width: 100%%; height: 90%%; }
 .bbCodeSpoilerContainer img { width: 100%%; height: 98%%; object-fit: contain; object-position: 1%% 0px; }

Now, the Viewer is able to scale an image inside the page, with some texts around it. So for posts where author did a one-sentence introduction and hid a big image in the spoiler - that whole post now fits one page in the Viewer.

As example, I am playing with https://forums.spacebattles.com/thre...ngeon.1169649/

I am, kind of, satisfied.