FanFicFare VS otwarchive

See the specific GitHub issue for AO3's new Cloudflare implementation here. Then also see the browser cache feature wiki page on GitHub here.

If you're using Calibre, there is fanficfare that can grab and update the files from Ao3. Can grab from Fanficfare-github. I also rec the Kobo touch extended and kobo utilities. I keep a epub and kepub copy as storage isn't an issue for me, but I believe there's a way to have it convert on transfer.

So, I know about FanFicFare plugin and I know about the CloudFlare issue, pretty much blocking the plugin from working correctly. I have FanFicFare v4.24.0, so I'm trying to use the cache method. I followed the steps here, but what do I do now?

Right, so there is a workaround but it's a pain in the ass. Not hard, just... tedious.

Just PSA: it is on AO3, so Fanficfare works just fine.

https://github.com/JimmXinu/FanFicFare together with https://github.com/nsapa/fanfictionnet_ff_proxy … yeah, not for the weak-willed. Also, alias ff_cache=fanficfare -o use_browser_cache=true -o use_browser_cache_only=true works (with proper configuration).

It works very well, and is continually maintained by the developer. If you use it with fanfiction.net, you have to set it up to use your browser cache (there are instructions here: https://github.com/JimmXinu/FanFicFare/wiki/BrowserCacheFeature). That reminds me, there is another app you could use called FanFictionDownloader (www.fanfictiondownloader.net), but it's not integrated with Calibre like FanfictionFare. Yet other options are the WebToEpub plugin. I use it in FireFox, but it might be available for other browsers. But for the most part FanFictionFare (FFF) is the best, and works with AO3 as well as fanfiction.net (and many others).

Just download EPub (either with FanFicFare on a regular computer or via EPub download directly) and read it offline. There are number of EPub readers for all platforms and they usually work much more reliably than AO3/FFnet applications, your are not bound just to one server, and you gradually develop your own offline library of texts, so you won’t be ever that person who complains here that they went to the chapter 56 of a novel and it was taken down by the author.

Thanks! It came from the Image set AO3 uses. Not sure where that is actually used/if it ever actually is used though

It wasn't really "swept under the rug", it's just that none of the volunteers decided to work on it. AO3 is entirely run by volunteers, so it's not really anyone's fault that this is taking 14 years to resolve. If you think it's that serious, you can write the code yourself and submit it, but don't take it for granted that this is someone else's responsibility.

Since 5th December 2010. You should probably try to get your email back.

How to set up a dev environment: https://github.com/otwcode/otwarchive/wiki

Source: AO3-6365 Update muted users limit

Everybody who wants to complain about the horrible nightmare world of AO3 is hereby invited to get off their asses and make their own archive with blackjack and hookers. You can find the code here. You are welcome to use it.

It's Ruby on Rails. Repository

For reference, here's the post that says that a unique IP address can only add one hit per 24 hours. Here's the pull request on github. I'm not sure why the FAQ hasn't been updated to reflect that, but as far as I can tell, the 24 hour system is still in place.

On a related note, Ao3's code is open-source and they're on GitHub, so like, if you're a programming nerd and really want a feature added maybe send a pull request or something.