-
Notifications
You must be signed in to change notification settings - Fork 333
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
Bug: Feed entries with <description> element don't have a description #1782
Comments
Looks like it. The upstream dependency river (https://github.com/kayceesrk/river) needs to be extended to properly handle extracting descriptions from the feed. In river's Also, we should consider whether we still need to fall back to the metadata if these tags are not present. |
This needs to be addressed upstream in the dependency river. Here's a corresponding issue: tarides/river#12 |
Not sure if this is the same bug or just related. I use QuiteRSS, and I see entries and titles, but no content/description, and further, the link is just the link to another feed. E.g. https://tarides.com/feed.xml or https://alan.petitepomme.net/cwn/cwn.rss instead of getting to the actual article. |
I think it is different (but maybe related). This issue is about how the rss/atom feeds are scraped and turned into markdown documents with metadata. I don't know how the markdown files are turned into the rss feed and how that might affect what you observe. |
I looked into the feed. I believe it's (mostly) an issue with QuiteRSS. I open an issue there: QuiteRSS/quiterss#1603 |
RSS feeds with a
<description>
element are not populated with a description. See e.g.:ocaml.org/data/planet/robur.coop/miragevpn--tls-crypt-v2.md
Line 3 in ff7b4c3
https://blog.robur.coop/feed.xml
It seems River fetches the page and scrapes html meta headers instead of the nice
<description></description>
served in the feed. For atom feeds I believe the<summary></summary>
element should be used.The text was updated successfully, but these errors were encountered: