philc / philc/vimium

Private history filter

Open
#4,856 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
27k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

Now that I frequently use LLMs as search engines, the prompts I use appear in the URLs in my search history, and those can show up as suggestions in Vimium's Vomnibar. I'd like to keep those history items private in case I'm projecting my screen or working at my computer with someone.

This could be accomplished in Vimium by adding the ability to configure a list of patterns to remove from the history suggestions that Vomnibar will surface.

However, those filtered history URLs will still be shown in Chrome's Omnibox if the user happens to be using that. The only way to remove suggestions appearing in the Omnibox is to delete those URLs from history.

At that point, I realized that this is a more general problem than just for Vimium users.

So I made a separate extension here which deletes matching URLs from one's history as soon as they're visited. This keeps them from appearing in both the Vomnibar and Chrome's Omnibox.

I wanted to surface this to Vimium users for comments. Before I circulate this extension more widely, is the separate extension a good solution to this problem? Is anyone using a different approach?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the separate private-history-filter extension linked in the issue; no Vimium files, tests, or entry points are identified. Decide whether history filtering belongs in Vimium or should remain a separate extension, then define concrete implementation and completion criteria before coding.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.