Skip to main content

Browser Extension

Nogon was formerly known as Hister. Updating the extension preserves your saved server URL, access token, and indexing preferences.

The Nogon browser extension is the primary way to automatically index your browsing history. It runs silently in the background, sending page content to your Nogon server as you browse.

Installation

The extension only communicates with your Nogon server, it never contacts any third-party services or the websites you visit (except for downloading the page’s favicon while collecting page data).

qutebrowser

If your package provides the hister command, use that name in place of nogon below.

The qutebrowser companion submits the rendered page title, text, HTML, and favicon to Nogon, then monitors changes made by single page applications. Pages served from the configured Nogon base URL are ignored.

The built in nogon companion qutebrowser command receives tab, navigation, and DOM update events through the local Qt WebEngine DevTools endpoint. Extraction runs in an isolated JavaScript world, then the companion submits the rendered content directly to Nogon. The access token is never injected into the inspected page.

Close all qutebrowser processes, then start qutebrowser with a loopback only debugging endpoint:

QTWEBENGINE_REMOTE_DEBUGGING=127.0.0.1:9222 qutebrowser

Run the companion in a separate terminal:

nogon companion qutebrowser

The command uses server.base_url and app.access_token from the normal Nogon configuration. Global --server-url, --token, and --client-timeout options can override the destination settings:

nogon --server-url http://127.0.0.1:4433 
  --token 'replace-with-app-access-token' 
  companion qutebrowser

The DevTools endpoint defaults to http://127.0.0.1:9222. Use --devtools-url, --label, --initial-delay, --debounce, or --max-wait after the qutebrowser subcommand to change its behavior. Run the command with --help for every option. Newly loaded pages are submitted after one second. Later content changes use a ten second quiet period, with a maximum wait of thirty seconds for continuously changing pages.

Remote debugging provides complete access to open browser pages. The companion accepts only a localhost or loopback IP DevTools endpoint. Never expose the Qt WebEngine debugging port to a network.

Features

Automatic Page Indexing

The extension captures visible pages, including the page title, full text, HTML, and favicon, then sends them to your Nogon server via its API. Pages opened in a background tab are captured when you view them.

Turn off Automatic indexing in the extension popup to pause automatic capture. A thick red border around the toolbar icon and the tooltip “Nogon: automatic indexing is off” indicate this setting. You can still index pages manually.

When a page provides a <link rel="canonical"> URL, the extension uses it for indexing if it is an HTTP or HTTPS URL with exactly the same hostname as the visited page. Relative canonical URLs are resolved against the document base URL. Other domains and subdomains, invalid URLs, and URLs containing credentials are ignored. URL fragments are removed. Automatic indexing checks allow and skip rules against both the visited URL and the canonical URL.

While a page remains visible, the extension checks for changes at intervals starting at 30 seconds. The interval doubles when nothing changes, up to five minutes. Navigation within a page waits for one second of quiet before a check, and automatic checks and submissions remain at least 30 seconds apart within that page. Rapid navigation can therefore capture only the latest page state.

Changes to text, title, favicon, or page metadata trigger an update. Cosmetic markup changes alone wait for a preview check, at most once every five minutes, so animations and changing HTML attributes do not continuously trigger indexing. Each submission includes the current full HTML for extraction and previews.

When you hide a tab, the extension captures one final snapshot and stops polling. If that snapshot has changed, it is submitted after any remaining submission delay. Showing the tab again resumes checks using fresh content. Closing the tab or navigating away flushes changed content immediately to the extension’s background process, bypassing the remaining delay. Unchanged content is not submitted again. Manual indexing also submits immediately and bypasses these delays.

To capture only selected websites, add allow patterns on the Nogon Rules page. A URL must match at least one allow pattern when the list is nonempty, and skip rules take precedence. The extension checks both lists before uploading pages or PDFs. Patterns that JavaScript cannot evaluate are checked by the server when the page is submitted.

Pages served with an unsuccessful HTTP status (4xx or 5xx) are not indexed automatically, so error pages such as “404 Not Found” stay out of the index. The extension reads the status of every main frame response with the webRequest API, which works in both Chromium based browsers and Firefox. Manual reindex overrides this check.

Manual Reindex

Manual indexing immediately submits the current page or PDF, even when automatic indexing is disabled or allow or skip rules exclude it. The indexing keyboard shortcut does the same. This is useful when you exclude a domain from automatic indexing but want to save an individual page from it.

Manual indexing saves an allow and skip rule override with the document, so it survives an index rebuild. It leaves your indexing rules and automatic indexing setting intact; later automatic submissions still respect them. Sensitive content checks and normal access restrictions still apply.

Keyboard Shortcuts

The extension defines browser level shortcuts for common indexing actions.

ActionWindows and LinuxmacOSNotes
Index current pageCtrl+ICommand+IRuns even when automatic indexing is disabled.
Disable indexing for current pageCtrl+BCommand+BAdds a skip rule for the exact current URL.
Disable indexing for current domainCtrl+YCommand+YAdds a skip rule for the current origin, including scheme and domain.

Browser shortcuts can be changed in the browser extension shortcut settings. In Chrome, Chromium, and Edge, open chrome://extensions/shortcuts. In Firefox, open about:addons, choose the extension shortcut settings, then edit the Nogon shortcuts.

Search Engine Result Tracking

The extension detects when you click on a search result in Google or DuckDuckGo and records the query alongside the result’s title and URL to provide that result for the same query in the future.

Indexed Page Indicator

The optional indexed page indicator checks the active page against your Nogon server. It is disabled by default.

Options Page

Connection Settings

Server URL
Config option

Full URL of the Nogon server, including its scheme and port.

Type string
Default http://127.0.0.1:4433/
Custom Headers
Config option

Additional HTTP headers included with every request. Use them for reverse proxy authentication or other server requirements.

Type map[string]string
Default (none)
Access Token
Config option

Optional global or personal access token used to authenticate extension requests.

Type string
Default (none)
Submit as public documents
Config option

Stores newly indexed pages as public documents with user ID zero. This setting appears after authentication.

Type bool
Default Off

The extension checks the server connection before saving settings.

Authentication

The extension supports global or personal access tokens and browser session authentication.

Browser session authentication requires an existing login to the Nogon web interface in the same browser when user handling is enabled.

The extension shares the active web session. Logging out revokes that session; a personal access token authenticates independently.

Submit as public documents makes newly indexed pages visible as public documents instead of storing them only under your user account.

Troubleshooting

The extension icon shows a ! badge

The last attempt to send page data to the server failed. Open the popup to see the error. Common causes:

  • The Nogon server is not running: start it with nogon listen.
  • The Server URL is wrong: confirm it matches the address printed when the server starts (default http://127.0.0.1:4433/).
  • User handling is enabled but the extension is not authenticated: configure an access token or use an active browser session.

Pages are not being indexed

  • Make sure Automatic indexing is enabled in the popup.
  • Check that the server is reachable and the URL is correct (see above).
  • If user handling is enabled, make sure you have authenticated the extension (see above).
  • Some pages (browser-internal pages like chrome://…, about:…) cannot be accessed by extensions and are silently skipped.