[GUI Plugin] FanFicFare

[ownedbycats]

Download the file somewhere you can find it. Go to Preferences > Plugins > Load plugin from file. Find the file. Restart Calibre.

(Sometimes I wish that test versions were optionally available from the plugin updater—albeit with a dozen THIS IS A TEST VERSION AND THINGS MIGHT BREAK popups to make sure it sinks in for certain users—but that would probably be a lot of extra work.)

[JimmXinu]

Originally Posted by bpothier

StoriesOnline "dupe" story ID/URL re-use issue...
(wall of text)
(I can already imagine JimmXinu's dislike for SoL flaring up, so maybe someone else has an idea/fix? )

Because of course they do.

And this is real problem you've seen happen? The same ID number reused? More than once?

Interestingly, it looks like your modified URLs actually still work if you click on them. IE, you can use one to get to the story with that number on the site. https://domain/s/####-anything-you-want seems to work.

So adding something to the story ID and URL might work. But it would involve changing the story ID and URL during metadata fetch which some other adapters do and can be a bit clumsy.

I don't have the energy right now to do more than vaguely speculate.

[tricklem]

Originally Posted by ownedbycats

Download the file somewhere you can find it. Go to Preferences > Plugins > Load plugin from file. Find the file. Restart Calibre.

(Sometimes I wish that test versions were optionally available from the plugin updater—albeit with a dozen THIS IS A TEST VERSION AND THINGS MIGHT BREAK popups to make sure it sinks in for certain users—but that would probably be a lot of extra work.)

Awesome. Thank you it worked.

[ownedbycats]

Originally Posted by JimmXinu

Because of course they do.

And this is real problem you've seen happen? The same ID number reused? More than once?

Yikes. Re-using a primary key/uid is just not not...good practice. In the worst cases, it can even be a security issue.

[bigwoof]

Testing the Cloudflare aware test client and it seems to work!!

Thank you @JimmXinu for getting this working! It is much appreciated and I hope you have a great holiday break to make up for the stress of this massive change breaking probably the most popular connector right before Christmas..... :-) :-)

[tgoold]

@JimmXinu

Just tried to update some fics in Calibre with FanficFare. Was working just fine on the last update of books (Dec. 17). Today, I had a bunch of books from Archive Of Our Own, and one from Fanfiction.Net. The AO3 books updated, no problem, but it seems FFNet has changed something on their backend. The message I got was in the log was as follows:

Status
Title
Author
Comment
URL
Error
O Mine Enemy
Kirby Lane
HTTP Error 403: Forbidden
https://www.fanfiction.net/s/3514260/1/

When I tried downloading another FFNet story (one that I hadn't downloaded before), the title and author fields both read "unknown"; everything else was the same.

Thank you for this marvellous plugin, by the way! I appreciate everything you do to keep it up to date and working!

[ownedbycats]

See post #4997.

tl;dr for the last few pages and the GitHub thread: FFnet was being attacked by bots and installed Cloudflare. Cloudflare thinks FFF is a bot attacking the site and blocks it. Jim made a test version of FFF that doesn't get blocked.

The test version only really works on 5.x. Older versions just produced a lot of OpenSSL errors whenever downloading from FFnet.

If you're using Calibre 4.23 and don't want to upgrade for whatever reason, my suggestion is to grab the portable version of 5, load up the test version of FFF in it, open your library, update, and then switch back to main Calibre for your reading pleasure. Do not share libraries if you're using any version below 4.23 or things will break.

[bigwoof]

[QUOTE=tgoold;4072630]
> Just tried to update some fics in Calibre with FanficFare. Was working just
> fine on the last update of books (Dec. 17). Today, I had a bunch of books
> from Archive Of Our Own, and one from Fanfiction.Net. The AO3 books
> updated, no problem, but it seems FFNet has changed something on their
> backend. The message I got was in the log was as follows:

Fictionpress just started using Cloudflare and that broke everything. You need to use the test FanFicFare client posted a few pages back that uses a Cloudflare aware download library for FFF.

[ownedbycats]

Originally Posted by ownedbycats

add_to_replace_metadata:
## Changes breaks to paragraphs in comments for better formatting
 description=><br/>=></p><p>
 description=><p>=><p align="justify">

The second line doesn't work. Did I break the syntax?

Turns out it was working. I just had comments set to "new only" and was testing it by using update metadata.

[Mandabar]

Originally Posted by ownedbycats

See post #4997.

tl;dr for the last few pages and the GitHub thread: FFnet was being attacked by bots and installed Cloudflare. Cloudflare thinks FFF is a bot attacking the site and blocks it. Jim made a test version of FFF that doesn't get blocked.

The test version only really works on 5.x. Older versions just produced a lot of OpenSSL errors whenever downloading from FFnet.

If you're using Calibre 4.23 and don't want to upgrade for whatever reason, my suggestion is to grab the portable version of 5, load up the test version of FFF in it, open your library, update, and then switch back to main Calibre for your reading pleasure. Do not share libraries if you're using any version below 4.23 or things will break.

Huh, I never thought of doing a separate installation to keep just for DeDRM.

Originally Posted by JimmXinu

It is unfortunate, but entirely possible, that ffnet support may not be possible in older versions of Calibre from now on.

I want to note that I'm running 4.23 and tested the test version. I did an update of ONE fanfiction.net fiction and it worked correctly, now trying to do a more comprehensive update see if the result holds true.

Update: It did! Tried to update my entire in-progress library and no 403 or other coded failures. I should mention my personal.ini does have the attempted client and delay:8 changes added in, though I don't think they apply to a cloudscraper attempt.

[BetterRed]

Moderator Notice
@JimmXinu - I merged a thread into here ==>> 5006

Its been hidden by all the chatter since

BR

[ghost9876222]

work on 3.48

[Atherton25]

Originally Posted by JimmXinu

Because of course they do.

And this is real problem you've seen happen? The same ID number reused? More than once?

Jumping in just to let you know that it is a real problem (though not a major one for me). Personally I've seen it happen about 3 times since I started using FFF to download SOL stuff.

Basically what I've determined is when an old story gets removed/deleted for any reason that old ID gets recycled back into service. Not sure how long it takes, but the last time I had it happen the story had only been gone for (at most) 3 weeks based on the download time (so not long). I spotted it because I got a duplicate story on a newly released story I was downloading.

For me it's not hard to track down. I keep an 'ID' column for StoryID's for reasons similar to this or to track down some story's I've had in the past that I had ID's for but no name or the name changed for some dumbass reason. Searching the URL ID is annoying and I can't remember how to do it without looking it up half the time. Just removed the old story URL to get the new one as I've done in the past. It hasn't really bothered me because I don't get a lot of SOL stuff, but it has happened.

[Ytierian]

Originally Posted by JimmXinu

It is unfortunate, but entirely possible, that ffnet support may not be possible in older versions of Calibre from now on.

This would be extremely unfortunate. I'm stuck on an older computer (no money to upgrade) so Win-7 is my life now. Since V5 of Calibre won't work on Win-7, I'm stuck at V4.23.

I can work around the issue using the 'Save as eBook' plugin for Firefox, but it's clunky.

[Mandabar]

Originally Posted by Ytierian

This would be extremely unfortunate. I'm stuck on an older computer (no money to upgrade) so Win-7 is my life now. Since V5 of Calibre won't work on Win-7, I'm stuck at V4.23

I can't guarantee it, but as I posted above here it is working on my install of calibre 4.23 (Haven't upgraded due to DeDRM lagging behind in development).