-
Notifications
You must be signed in to change notification settings - Fork 555
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
Support Media RSS #4132
Comments
This seems odd for an RSS client to implement since it would only apply to NNW and no other RSS client. I believe Open RSS feeds show the images inline. Maybe those feeds will work better for you? |
Did some more digging. This is an official RSS specification called Media RSS which I had never heard off. Scouring this issues page a bit, there are multiple requests to add it.
As well as on RSParser:
where there is an open pull request with (at least limited) support Media RSS is a widely accepted standard, otherwise it would not be reported as much. Other RSS readers support it. In #2538 @brentsimmons mentions required volunteer time:
I would love to help here – if it is accepted, that MRSS should be added to NetNewsWire, I'd start by fixing up the RSParser Pull-Request. |
(I would love to see this added.) |
+100 this is a major missing feature to me ... with this, we could combine much more of everything into our daily digital consumption diet (podcasts, YouTube channels etc) without leaving the app. |
Came here to report this bug too. No images show up in any of the Mastodon RSS feeds I follow. Neither on the NNW iOS app nor the macOS app. These images appear fine inside the official Inoreader app. |
Came here to also express my interest in having this supported. 🙂 |
For example Mastodon attaches its images in posts via a
<media:content>
tag, which they decided here and which NNW does not currently display.As the tag is a part of the RSS item, I think it should be displayed as part of this item.
EDIT: At this point I assumed that this was a Mastodon specific bug, subsequently the title was changed and a more complete description is in the third comment.
The text was updated successfully, but these errors were encountered: