fanficfare -o use_browser_cache=true -o use_browser_cache_only=true with Flatpaked Firefox? #985
Comments
|
Everything you've shown here indicates that FFF looked for the appropriate cache files--the cache file names are hashed versions of the cache key which comes from the URL. They are the same for me. But FFF isn't finding those files and your This commonly happens if that's the first ffnet URL you've hit recently and received the Cloudflare screen in between. That changes/doesn't cache the page. Try manually clicking to a different chapter and then back with the buttons on the page--not the browser back button--or clicking to the author page and clicking the story URL there. |
|
It doesn’t like it. I have went back and forth in the story couple of time, even with |
|
I can't think of anything I can do to help with the browser not caching the file. Does it work better with Chrome? Non-flatpak Firefox? I use Firefox on win10 all the time. I don't have time this week for more esoteric approaches, like investigating possible changes/additions to the cache hashing algorithm. |
|
I haven't found anything about Firefox changing their cache hash. I don't think I have anything for you. |
I don’t use Chrome and it works perfectly with non-flatpak Firefox. I am just on the MicroOS (a minimal system with almost no own packages installed, everything in Flatpaks/distrobox). I will investigate further. Please, don’t close, this is certainly a problem. |
|
I can leave it open for now, but I really don't think this is an FFF issue. One idea that occurred to me: are you using a VPN or proxy of some kind? We've seen various weird things happen with those that all go away without them. |
No, nothing like that, wifi to home router connected to VDSL provider. I will try to ask around Flatpak Firefox. |
|
https://support.mozilla.org/cs/questions/1423106 let's see what happens. |
|
I can reproduce even with Firefox v117 from the mozilla tarball and FanFicFare 4.27.0: |
|
Still working for me with that story with the same cache file name. You could try adding |
|
https://paste.opensuse.org/pastes/5b7dfc5489f2 And nothing opens in a browser. And you still haven’t explained to me why this function provides incorrect result (from the Reddit post): with key then it tries key Is it possible that being Flatpaked the algorithm for locating the cache entry somehow changed? |
I don't read reddit, I haven't seen whatever post you are referring to. We've previously established I can't explain your issue.
Seems unlikely to me it would change the actual hash algorithm. IMO, it's more likely it caches in a different location, caches fewer files, or changes the key input changing the You can try using this version of browsercache_firefox2.py (unzip it, replace existing) that will scan your cache dir and output all entries <4 hours old containing the string Using that, I see in my cache a file with an additional element after |
|
Does this give you any new information? |
|
scandir didn't find any cache files at all with fanfiction.net in the last 4 hours. That suggests one or more of:
I'm assuming that you know how to load the story chapters in cache correctly. |
|
Ehhh, … I am sorry, I missed that four hours limit. https://paste.opensuse.org/pastes/175ff08832ed is after I have refreshed the cache. |
|
https://paste.opensuse.org/pastes/2ec711f0af38 this is with |
|
Your cache entries have an additional parameter Because after installing that, I can get cache entries with First, can you open a tab without a container to load the story? If that doesn't work, this version adds |
|
https://paste.opensuse.org/pastes/fc93e68e219c with the page opened outside of any container. |
|
|
Now I am seeing the timestamp appearing in the cache key in your cache entries: So adding just the Some (admittedly brief) further experiments seem to indicate that the timestamped cache entry appears when CloudFlare intervenes. But if you load the page directly, by clicking in the address bar and hitting enter to load the page directly or clicking the author link then the story link on the author page(since it's a single chapter story), the cache page FFF expects is saved. |
|
From what I've seen, I believe this should work for you, if you:
I've added some additional verbiage to the Browser Cache wiki page about reloading the page correctly:
|
|
I am sorry, but no. You can see that I have the page outside of any container: I have reloaded couple of time, ask Firefox to remove all information about the site, certainly no CloudFlare screen was seen anywhere around, and yet: |
|
With |
|
Okay, then it's just not going to work with that browser for now. The question is whether it's worthwhile to re-implement cache scanning and indexing for this one particular browser sub type. |
|
I don't know anything about flatpaked Firefox, but are you using I noticed some time ago that Firefox outside of Flatpak doesn't function with FanFicFare unless it's disabled and Firefox restarted. I didn't report it as I mostly had the option out of habit and I am under impression that enhanced tracking protection is effective enough anyway while incompatible with that option. |
|
Actually, it started to work (probably some caches get replaced), so I was able to refresh plenty of my stories. THANK YOU!!! Except, https://www.fanfiction.net/s/4043066/1/520-Things-I-am-not- … I guess that not complete name confused something: (sorry about too long list of cached files) |
|
In that case, I'm inclined to put this all down to container tabs and cache loading--which can sometimes require reloading/ctrl-shift-reloading pages and sometimes still doesn't work for unknown reasons. |
Actually not, I have it set to false. |
When I try to run FanFicFare from the
mainbranch (specifically fb552c8) to get a story out of the Firefox cache I get this error:Using Firefox (
org.mozilla.firefox) version 115.0.3 from the official Mozilla Flatpak. It seems I have an access to all those directories, but FanFicFare indicates a wrong file there.The text was updated successfully, but these errors were encountered: