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

Cache favicons instead of fetching from Google at every page view #453

Open
jcharaoui opened this issue May 6, 2014 · 8 comments
Open

Comments

@jcharaoui
Copy link
Contributor

Please have Bookie cache favicons instead of fetching them from Google every time a page is displayed.

@anarcat
Copy link
Contributor

anarcat commented May 6, 2014

in fact, why are they at google in the first place?

@mitechie
Copy link
Member

mitechie commented May 6, 2014

So the favicons are through google because they provide the lookup for the pages. Google runs them through a CDN and if you reload the page and watch the network developer tools you should see the favicons loaded from the cache. This was the most performant way to display them as they're from a different network, don't hit browser number of connection limits as fast, and Google CDNs a lot better than I can.

The screenshot belows shows them showing from the cache.

favicon_cache

@mitechie mitechie closed this as completed May 6, 2014
@anarcat
Copy link
Contributor

anarcat commented May 6, 2014

uh, well the point here would be to not rely on google for content. isn't that the point of a "self hosted solution"?

i understand you may make that policy decision for your hosted service, but please provide this as an option for people that want to host that content themselves.

@mitechie
Copy link
Member

mitechie commented May 6, 2014

anarcat, sure thing. I'm open to a bug to either turn off or change the source of the favicons. The self hosted solution doesn't rely on them for data. It degrades nicely. This bug was filed about caching those icons which I demonstrated they are cached. Please file a new issue for other concerns and thanks for the feedback.

@mitechie
Copy link
Member

mitechie commented May 6, 2014

Just to further make sure I express that I do appreciate the self hosted concerns and did take them into account when I added the feature.

  • The favicons only specify a domain to google (so doesn't leak your bookmark urls)
  • They're not required for UX (not click targets/etc)
  • They're made to be performant using their cache.
  • They're not tied to any stored data so losing them does not jeopardize anything that you might want backed up and such.

@jcharaoui
Copy link
Contributor Author

I'm sorry, I might not have been clear in my original post : by "have Bookie cache" I mean have Bookie serve the favicons from it's database, same as the article content is saved into Bookie's database. The app can tell the browser to cache the icons, that's fine, but my main issue is that I think Bookie should be able to serve them from its own database.

@mitechie
Copy link
Member

mitechie commented May 6, 2014

jcharaoui ok I'll reopen this as a bug to host favicons. I think the first step will just be a config option in the ini to just not display them at first. Thanks for updating the issue.

@mitechie mitechie reopened this May 6, 2014
@anarcat
Copy link
Contributor

anarcat commented May 7, 2014

thanks!

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

3 participants