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

Feed icon #83

Open
uGeek opened this issue Mar 13, 2024 · 6 comments
Open

Feed icon #83

uGeek opened this issue Mar 13, 2024 · 6 comments

Comments

@uGeek
Copy link

uGeek commented Mar 13, 2024

You could add the icon variable In the configuration file, currently there is the title, description even the RSS type but when you subscribe to a Feed generated with the merge option it does not have an image.

@shouya
Copy link
Owner

shouya commented Mar 14, 2024

Sure, let me think about how to do it. For the time being, have you tried modifying the resulting feed with modify_feed?

Here's an example (suppose your feed format is rss, not atom):

      - modify_feed: |
          feed.image = {
            "description": null,
            "height": null,
            "link": "",
            "title": "",
            "url": "https://statics.ccma.cat/multimedia/jpg/6/4/1697466540346.jpg",
            "width": null
          }

@shouya
Copy link
Owner

shouya commented Mar 15, 2024

As I did more research on the topic, I found that the feed image isn't the same as the feed icon. It turns out there is no standard in how the feed's icon should be specified in the feed itself.

According to this stackoverflow answer, most feed readers will just load the icon using the favicon of the main site. This means setting feed.image may not be very effective.

The answer also offers an idea to get around the issue. Suppose you're making a feed for http://example.com, you can make sure the link field of the source is set to http://example.com. Then the feed reader may find the icon at http://example.com/favicon.ico.

@uGeek
Copy link
Author

uGeek commented Mar 16, 2024

A long time ago I created the feed for both my blog and my podcast. Feed icon URL was here:

<image>
<url>https://ugeek.github.io/ugeek.png</url>
<title>uGeek Blog </title>
<link>https://ugeek.github.io/blog</link>
</image>

Here:

<image>
<url>https://ugeek.github.io/ugeek.png</url>

My feed in my case is:

<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel>
<title>uGeek Blog </title>
<link>https://ugeek.github.io/blog</link>
<description>Blog de Tecnología, Android, GNU Linux, Servidores, y mucho más. Blog vinculado al Blog del Podcast de uGeek</description>
<image>
<url>https://ugeek.github.io/ugeek.png</url>
<title>uGeek Blog </title>
<link>https://ugeek.github.io/blog</link>
</image>
<language>es</language>

@shouya
Copy link
Owner

shouya commented Mar 16, 2024

According to the stackoverflow answer I linked, the <image> tag is not really interpreted by feed readers as the icon of the feed. The favicon of the website specified in <link> is instead used. Unfortunately, there is nothing we can do by changing the feed itself to make the feed reader use a specific icon.

The following measures are my suggested attempts to make the feed reader find the icon correctly.

First, I noticed that the favicon of https://ugeek.github.io seem broken. See https://github.com/uGeek/ugeek.github.io/blob/main/index.html#L20-L23. Could you try fix it and see if the icon is shown correctly?

If that still doesn't work, I suggest you to try to make https://ugeek.github.io/favicon.ico point to a valid favicon and see if that works.

@uGeek
Copy link
Author

uGeek commented Mar 16, 2024

Therefore, being broken, the URL indicated on the tag is correct and it adopts that icon as correct. https://ugeek.github.io/ugeek.png

@uGeek
Copy link
Author

uGeek commented Mar 16, 2024

But you're right. I just subscribed and the icon does not appear. So that tag is not valid.

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