Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[xExtension-ImageProxy]: Missing images in mobile apps #268

Closed
Offerel opened this issue Jan 8, 2025 · 5 comments
Closed

[xExtension-ImageProxy]: Missing images in mobile apps #268

Offerel opened this issue Jan 8, 2025 · 5 comments

Comments

@Offerel
Copy link

Offerel commented Jan 8, 2025

I have been using the ImageProxy extension for a few days now because I noticed that some images were not being displayed in the articles. The problem is now solved in FreshRSS or the WebGUI. The images are usually displayed. In the mobile apps, however, this does not always work. Some images are displayed, others are not. This is not noticeable in ReadYou, but I recently switched to Capy Reader, where the typical symbol for a non-existent or defective image is displayed instead of the image. This leads me to the actual question: When are the images loaded into the cache? Only when I display the article in FreshRSS or as soon as the article is extracted from the feed by FreshRSS in the background process? Below is my current configuration of the extension:

image

In the nginx web server itself, I have not configured anything specifically for the ImageProxy. If I have understood the instructions correctly, I don't need this either if I use https://images.weserv.nl/?url=.

I have also created a question/issue for Capy Reader itself at jocmp/capyreader#696

@Frenzie
Copy link
Member

Frenzie commented Jan 8, 2025

There's no local cache, just potential cache in the proxy.

@Offerel
Copy link
Author

Offerel commented Jan 8, 2025

Yes. I know, its only cached on https://images.weserv.nl/, but the question is: When the image starts to exist in cache?

a) when the article is fetched by my local FreshRSS instance
b) in the moment, when i view/access the article via my local FrshRSS instance

@Frenzie
Copy link
Member

Frenzie commented Jan 8, 2025

Nothing's done at the time of fetching. The extension adjusts the image URLs just before the data is sent to the browser or client. Any potential image loading is done by the browser at that time.

@Offerel
Copy link
Author

Offerel commented Jan 8, 2025

So is assume b) in the moment of view/access. This would explain, why sometimes the image is "broken" on mobile. The article is downloaded/displayed/accessed via the mobile app. Since the image isn't available at the cache in this moment, it could take to long to load the image and some sort of timeout occurs. At least, his is to what conclusion i came now.

@Frenzie
Copy link
Member

Frenzie commented Jan 11, 2025

Closing as per jocmp/capyreader#696 (comment)

@Frenzie Frenzie closed this as completed Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants