Article thumbnails do not render in feeds pulled from Google Reader API

[Yutin9]

Describe the bug
When using FreshRSS's Google Reader API in fluentflame-reader, article thumbnails fail to display as they normally would when browsing feeds.
This has been tested comparing the feed parsed by fluentflame-reader itself vs parsed via the API.
As a side note, and something that would probably be better mentioned in another issue, the Fever API does not work at all, and leads to the settings of the program being inaccessible (it simply hangs at trying to load the entries through the API, this persists through restarting the program, I am not sure if this is an issue isolated to my system however). The Fever API seems to still work fine on Fluent Reader, for reference.

To Reproduce
Steps to reproduce the behavior:

1. Access the Google Reader API in FreshRSS with fluentflame-reader
2. Articles render with title, a cropped description and no thumbnail

Expected behaviour
Articles with thumbnails render the image previews properly, as is the case with Fluent Reader.

Screenshots
Screenshot of fluentflame-reader with the issue described (this is the Google API pulled from a FreshRSS instance I am running)

Screenshot of the expected behaviour for this feed (Note: this is the feed loaded via fluentflame-reader locally, so it doesn't have any inherent issue rendering thumbnails)

As an addition, this is Fluent Reader, also fetching the output of this same feed from the Google API

Platform (please complete the following information):

• OS: Windows 10 21H2
• Version: 2.1.0

Additional context
This could be noted as an extension of issue #120

[CrystalSplitter]

Articles with thumbnails render the image previews properly, as is the case with Fluent Reader.

Thumbnails are primarily extracted through opengraph, and I don't think the Google Reader API correctly scrapes thumbnails anymore since moving to the canvas based thumbnail system. I'd need some network responses to fix this to know what to test on.

Fever API does not work at all

Hmm. I thought I did fix this in #120. I specifically tested FeverAPI with FreshRSS (and only FreshRSS, and only FeverAPI). And you're using 2.1.0, which should be the version that fixed this? This one is baffling to me. Network responses would be ideal to fix this, because I can't exactly test this without using your FeverAPI instance.

[CrystalSplitter]

You know what it might be about the FeverAPI is that it's hitting the rate limit I implemented--it may be too low or simply not working correctly. Would you be willing to conduct a test from a developer build?

[CrystalSplitter]

As for greader thumbs, could you test this? #142 No idea if it works, can't test it myself currently.

[CrystalSplitter]

#142 has been merged, as I managed to test the GReader endpoint on FreshRSS. It worked fine, so merging. I'm still not sure what's causing the hanging with FeverAPI, if you have any knowledge.

[Yutin9]

I'm still not sure what's causing the hanging with FeverAPI, if you have any knowledge.

I'm not so sure myself, I'll test the new pull request for Greader, and check logs to see if anything of note shows up for the Fever API

[Yutin9]

I can confirm the new build renders thumbnails correctly now, thank you. 👍

It seems to struggle with loading thumbnails when feeds are highly populated, but I assume this is due to how OpenGraph fetches them and not a consequence of the actual code (i'm comparing it to Fluent Reader, which obviously doesn't use OpenGraph and doesn't struggle with heavily populated feeds from the API). But as long as the amount of articles loaded at once are not a large amount it works fine.

On the Fever API, and general testing, is there somewhere the program generally stores logs? I'd have liked to post some when it crashes or hangs indefinitely, but couldn't find any relevant output.

[CrystalSplitter]

It seems to struggle with loading thumbnails when feeds are highly populated, but I assume this is due to how OpenGraph fetches them and not a consequence of the actual code (i'm comparing it to Fluent Reader, which obviously doesn't use OpenGraph and doesn't struggle with heavily populated feeds from the API). But as long as the amount of articles loaded at once are not a large amount it works fine.

Hmm. We may want to try having these load in the background. How many articles are you loading anyways here? A few thousand? tens of thousands? hundreds of thousands? millions?

The reasons we use opengraph are because images in the articles themselves can cause huge performance hits on rendering calls. This was a big problem we encountered in the original Fluent Reader.

On the Fever API, and general testing, is there somewhere the program generally stores logs? I'd have liked to post some when it crashes or hangs indefinitely, but couldn't find any relevant output.

You must build it from source, see https://github.com/FluentFlame/fluentflame-reader/blob/master/docs/BUILDING.md

[Yutin9]

Hmm. We may want to try having these load in the background. How many articles are you loading anyways here? A few thousand? tens of thousands? hundreds of thousands? millions?

about 10000 as it is currently, if I were to choose the unlimited option.

And as an addendum: After further testing the Fever API seems to work fine in this version, I hadn't tested it prior which is why it went unmentioned. If anything similar comes up again I'll simply build from source and check logs before posting an issue, for now I think this can be marked closed. Thanks.