[GUI Plugin] FanFicFare

[JimmXinu]

New Test Version Posted

2023-07-12
- Apply mark_new_chapters to new story chapters in Anthologies. #977
- Allow mark_new_chapters when 1 chapter in case it changes.
- Increase sleep times between cache checks using open_pages_in_browser.

[ownedbycats]

Is the last one another anti-hammer measure?

[JimmXinu]

I was needing more time for open_pages_in_browser on ffnet a few days before AO3's issues.

[ownedbycats]

https://archiveofourown.org/admin_posts/26449

from the post (emphasis theirs):

• We attempted several different mitigation and blocking methods and settings changes to counter the attack. These brought the site up intermittently, but were not enough to contain the attack. Eventually, we implemented Cloudflare's Under Attack mode as a temporary—and extremely effective—solution. Cloudflare is a service that provides added security between our servers and the internet. Under Attack mode is not meant to be a permanent part of the Archive's setup. All content remains on our servers.
  
• You may be seeing a Captcha challenge when you access an AO3 page. That happens so that the Archive can make sure you're a human and not a robot. We know it's annoying, and we're sorry! We also know some browsers and older devices aren't currently able to access AO3. These measures are temporary and will be reassessed once the attack has stopped.

so Jim's personal opinion was right

My FFF downloads have been working as usual, though from previous behaviour seen elsewhere I suspect it may depend on where the user is located (I'm in Canada).

my personal opinion/advice (which may or may not be endorsed by Jim): download your stories as usual, though perhaps not a whole bunch at once. If you get an error, wait a few hours before retrying.

[JimmXinu]

I would further speculate that AO3 might end up keeping CloudFlare long term, but at a lower level that full "Under Attack" mode.

Which would likely still intrude on us more often than in past.

[ownedbycats]

The edit note on the admin post seems to imply that (emphasis mine):

Edited July 12, 2023, 19:20 UTC: Clarified which of Cloudflare's services is not intended to be a permanent part of the Archive's setup.

[ownedbycats]

Mostly out of curiosity: I had a story that was one fic, but three separate multi-chaptered 'volumes', so I modified the ToC to make it nested. (Then put it on the reject list to prevent accidental overwrites.)

Is there any existing method for replacing something like "Volume 1 -" in the chapter title with a nested entry rather than doing it all manually?

Looking at the toc.ncx afterwards, I couldn't differentiate between the top and second-level ToC entries, so maybe not.

[JimmXinu]

No, FFF can't do anything like that.

[ownedbycats]

Originally Posted by ownedbycats

After Calibre added the extra data folder, I've taken to putting a copy of the downloaded cover in it for backup.

@JimmXinu - Would it be possible to automatically do this for a new download? Probably not worth the effort.

For anyone else who may find this useful, this can be done with Action Chains (edit: also read the few posts afterwards - using the template as-is may have an unintended effect)

[JimmXinu]

New Test Version Posted

2023-07-15
- Add anthology_merge_keepsingletocs option, requires new EpubMerge.

This goes with the change in the previous test version:
- Apply mark_new_chapters to new story chapters in Anthologies. #977

In short, Chirishman pointed out that the default EpubMerge/anthology anthology behavior of skipping TOC sub-entries for stories with only one chapter could conceal the '(new)' chapter markings.

Since that code was actually in EpubMerge, you need this new EpubMerge test version to use anthology_merge_keepsingletocs.

Discussion:
https://github.com/JimmXinu/EpubMerge/pull/10
https://github.com/JimmXinu/FanFicFare/issues/977

From defaults.ini:

Spoiler:

## (Plugin Only) - When mark_new_chapters:true, new stories added to
## an existing anthology will have *all* chapters marked (new).  If
## set to latestonly, existing (new) marks will only be removed when
## that particular story within the anthology is updated--either
## because it has new chapter(s) or you are using Update Always.
##
## By default, EpubMerge only creates one TOC entry for a story that
## has only one chapter (not counting titlepage and logpage).  Because
## that TOC entry is the story title, the *chapter* title doesn't
## appear in the anthology TOC.  Setting
## anthology_merge_keepsingletocs:true will keep the full TOC for all
## anthology stories, even when only one chapter.  Helpful to see
## (new) marks in TOC when mark_new_chapters:true
#anthology_merge_keepsingletocs:false

[ownedbycats]

My brain farted again: What's the method for re-downloading a specific old chapter?

Perhaps it may be helpful to add to the FAQ.

[JimmXinu]

The method for non-technical users would be 'Overwrite Always' mode.

Technical users can delete the specific chapter from the epub with the tool of their choice and invoke Update.

Question, yes. Frequent? Doesn't feel like it. Once every few years maybe?

[ownedbycats]

Maybe an addition to the Update Mode page? If that's okay, I can make the edit.

[JimmXinu]

FAQ would be better than the Update Mode page. Or the little used UserContributedContent.

[Jager956]

Not sure what is going on with storiesonline. I usually download stories that looks interesting and read them when I have time. Today I found out that anything downloaded since beginning of June have this inside:
---
There is more of this chapter...
The source of this story is Storiesonline
To read the complete story you need to be logged in:
---

I saw some updates for SOL in test version and tried also with latest test version of plugin. Same issue. Doesn't matter if I try to update only one story or multiple.

What looks like helped is:
I increased slow_down_sleep_time:6
I removed all epub files from those titles and redownloaded all of them. Previously I tried update epub always, but that did not updated them (it said added 0 chapters of X in job status).
For now It looks like they are all there...

Not sure what will happen next time when I update stories that are still in progress...