RSS feed reader favicon seemingly cannot be changed? #8
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi David,
I was wondering if you had any insight into the trouble I've been having with changing the favicon when my site using duckling is shown via an rss reader like newsblur?
I've published many different variations of my site with the same result. I can change the favicon shown when the site is viewed in a browser tab, but the favicon shown from newsblur is still your logo.
The current commit of the config.toml for present.quest shows the facicon I'm explicitly pointing to this favicon. This shows as expected in the browser tab
However, when https://present.quest/atom.xml is tossed into newsblur I am seeing your logo:

I've tried using the
emoji_faviconvar also and I see similar behavior. I copied the partials/favicon.html file out of your theme to make edits to overwrite anything that may be contributing to this, but ended up leaving it unchanged because nothing appears to be the culprit.Your logo files don't appear in my public/ dir after the site is built. The apple-touch-icon.png and favicon.png files in the public dir are mine.
I'm wondering if your logo is referenced somewhere in one of the scss to html templates in a way that tells a reader to pull it from a remote site?
I'm not terribly familiar with html and less so with scss, but I've spent a bit more than a week trying to track this down. I've checked everything I can think that could be causing this behavior. I'd appreciate any insight you might have.
Thanks!
Ethan
No, the image files are the only resources for the favicons. As in my RSS reader, the atom feed shows your logo when added - are you sure that this is not some caching problem of your RSS reader?
Well now I feel exceedingly silly. Thanks for taking the time to look into this. I tried in a different reader. It was a caching issue.