Neat user/repo/issue/commit hovercards for GitHub.
Why Chrome warns me the extension might read my browser history?
It’s because GitHub Hovercard uses
webNavigationmodule to dynamically inject content scripts (to support GitHub Enterprise). See #34. GitHub Hovercard won’t track or record any of these private data.
Why can GitHub Hovercard’s demo page find out I have installed the extension or not?
In Chrome/Opera it’s allowed to get this information through the API while in Firefox the extension will add a special attribute (
data-github-hovercard) to the page’s
bodyelement so that the demo page can find out if the user has installed GitHub Hovercard. It’s all about user experience and the extension itself won’t track or record these data.
Why access token doesn’t work?
Now GitHub Hovercard is saving user’s private access token into
localStoragehas a limit of 5MB and the problem might be other extensions have consumed too much storage that GitHub Hovercard failed to save access tokens.
For browser extension versions, GitHub Hovercard provide following options:
Use this option to set custom domains for your GitHub Enterprise service. Note that you don’t need to set
github.combecause it’s always included. You may be asked to grant additional permissions for those domains.
If you don’t want the hovercards to pop up instantly, you may set a delay before they try to retrieve data and appear.
For unauthenticated requests, GitHub API has a fairly low request limit.
In later versions I might introduce access tokens to increase this limit. Working on it.
Authentication is supported from v0.0.7.