- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
Hi everyone,
I am the original author of Searx. I started Hister with a similar motivation: reducing our dependence on external search engines while keeping searches and personal data under our control.
Searx is a metasearch engine that forwards queries to other search providers. Hister takes a different approach. It builds a private full text index from content you choose, then searches that index entirely on your own infrastructure.
Hister can automatically index pages through its Firefox and Chrome extensions. It can also watch local directories, import browser history and bookmarks, index individual URLs, and crawl complete documentation sites.
The feature I find most useful is offline previews. Hister stores the readable content and HTML of indexed pages locally. You can open a result in a clean and sanitized preview beside the search results without visiting the original website again.
Some other features:
- Full text search across web pages, PDFs, docx files, Markdown, OrgMode and text files
- Phrase searches, field filters, date filters, wildcards, negation, aliases, labels, facets, and result priorities
- Optional semantic search using an embeddings endpoint you configure
- Persistent website crawls
- Imports from browser history, Linkwarden, Karakeep, Shaarli, Wallabag, and Linkding
- Web, terminal, command line, HTTP API, and MCP interfaces
- SQLite and PostgreSQL support, plus optional multiple user hosting
Hister cannot replace a global search engine (yet) for subjects you have never encountered because it only searches what you have indexed. My workflow is to search Hister first, then use its shortcut to fall back to traditional search when I need broader web results.
The project is free software under the AGPLv3+ license. It can be installed as a standalone binary or with Docker.
Project: https://github.com/asciimoo/hister
Website and documentation: https://hister.org/
Small read-only demo: https://demo.hister.org/
I’d appreciate feedback, questions, and suggestions as well as joining our growing community.
AI disclosure: AI assisted contributions are not strictly prohibited, but all contributions should be made by humans. More details: https://github.com/asciimoo/hister/blob/master/CONTRIBUTING.md#ai-policy
You must log in or register to comment.
@[email protected] please update the title with the appropriate tag (rule 7) and if AI was involved in development, add the disclosure per rule 8 (sample disclosures can be found here)
Thanks!
Thanks for letting me know. I’ve updated the post.
Awesomely cool and federated search would be a boon later! Hope you keep it going!
Can i use this in my self hosted environment? the docs talk mainly about running it in the terminal
does it have a docker install? found it https://hister.org/docs/dockercan i connect it to other services like paperless, or would i need to manually import files?
I have tried it a bit today and I like it, but I have a few questions
- Is it better to run it in docker or e.g. a LXC in proxmox? If i want to index files, it seems it needs the config.yml file
- After just playing with it for a day, the disk usage is 150 MB. I figure I should use postgres instead of sqlite. Do you have any examples on how to set that up, preferably with docker? I guess I can figure it out, but it might take me some time. I am not familiar with pgvector
can i connect it to other services like paperless, or would i need to manually import files?
Hister supports importing data from a few services, but paperless isn’t supported yet. More details: https://hister.org/docs/import
Is it better to run it in docker or e.g. a LXC in proxmox? If i want to index files, it seems it needs the config.yml file
Docker is perfectly fine. Every settings option from the config file can specified using environment variables. The syntax is
HISTER__[SECTION]__[OPTION]=[VALUE].After just playing with it for a day, the disk usage is 150 MB
Probably most of the disk space is occupied by the Hister binary which contains all the N-grams required to identify ~30 languages. The index should be much smaller.
I figure I should use postgres instead of sqlite.
SQLite is more than enough for personal use, but if you prefer to use postgres, just specify the standard DSN formatted connection data to the
server.databaseconfig option: https://hister.org/docs/configuration#database-backendshow to set that up, preferably with docker
Use the
HISTER__SERVER__DATABASE="host=localhost user=hister password=hister dbname=hister port=5432"environment variable.I am not familiar with pgvector
Hister automatically creates the database model and handles the migrations if required.
Thank you for your response 🙂 I will stick to sqlite
How do i use environment variables to make a indexer? I couldn’t get it to work
i.e. the part with directories https://hister.org/posts/indexing-local-files-with-hister
indexer: directories: - path: ~/Documents filetypes: ['md', 'txt'] - path: ~/code/projects filetypes: ['txt'] excludes: [, 'secret/*', '*key'] - path: ~/notes patterns: ['*.org', 'doc_*', 'README']How do i use environment variables to make a indexer? I couldn’t get it to work
Repeatable config options are not supported from env vars. In this case you have to mount a config file to your container. But, if you want to track local files from docker, you have to mount those files/directories anyway. I suggest to use the standalone binary release if you’d like to track local files, it is way more convenient.
Is there a future where Hister takes on the functions of SearXNG? I.E. new content is discovered through APIs but local or previous content is prioritized?
Currently it is not planned. Hister guarantees that non of your data/query/metadata leaves the service if you use it. As I see, this is a more valuable and unique feature than having an integrated metasearch. There are already great metasearch solutions and Hister provides an easy fallback to search providers, so in my opinion this direction would be more of a sacrifice than an improvement.
Oh I didnt realize there was a fallback option, that’s great.
If anyone else is confused wtf this does, I pointed the clankers at it and asked. Way to bury the lede OP.
See [6] for some missing features (?) that would be nice to clear up.
[1]
- You open a webpage normally.
- The browser extension reads the page that your browser loaded.
- It sends the page text, title, URL, and other details to your Hister server.
- Hister stores and indexes that content.
- Later, you search Hister for words from the page.
- Hister finds the saved page, even when you cannot remember its title or URL.
[2]
so, like a Google search of visited sites and my own drive?
Yes. That is actually a reasonable use case.
If you pointed Hister at:
C:\Documents
it would:
-
Walk the folder tree.
-
Read supported files.
-
Build a full-text index.
-
Watch for changes.
-
Re-index new or edited files automatically.
You could then search for things like:
tax invoice lenovo
lumbar radiculopathy
that python script with sqlite
“Methylphenidate” (exact phrase)
without caring which folder the file lives in.
Is it like Google?
Yes, but only for your own data.
Imagine Google, except the only websites are:
C:\Documents
D:\Notes
your browser history
pages you crawled yourself
You open a browser, type a search, and receive ranked results from your own files instead of the internet.
Can you access it from elsewhere on your LAN?
Yes.
By default it listens only on localhost:
127.0.0.1:4433
However, you can configure it to listen on all network interfaces:
0.0.0.0:4433
Then any device on your LAN can use the web interface or API, provided your firewall allows it. You should also enable an access token or user accounts if you expose it beyond your own PC.
[4] What interests me more for your home setup is that Hister is not just a search engine.
It already exposes:
a web UI,
a REST API,
and an MCP endpoint for AI assistants.
That means you could run one Hister instance on your server, index your documents once, and then:
search them yourself from any device on the LAN,
or let an AI search the same index through MCP.
If I wanted a self-hosted “Google for my own stuff” with minimal setup, Hister is much closer to that goal than Meilisearch. Meilisearch is an indexing engine. Hister is already a complete document search application.
[5]
Yes. By default, Hister stores its data in SQLite:
Search index and metadata: db.sqlite3
Stored HTML previews: separate files on disk
Configuration: YAML
It can also use PostgreSQL instead of SQLite if you want.
Regarding browser history, there are two separate things:
-
Your browser’s history database (Chrome, Firefox, etc.).
-
Hister’s own index.
They are independent after import.
For example:
Monday: You visit example.com.
The extension sends the page to Hister.
Hister stores the text, title, URL, metadata, and optionally the HTML preview.
Tuesday: You clear Chrome’s history.
The Hister copy remains. Clearing your browser history does not delete Hister’s copy. Hister is designed to be a long-term knowledge store, not a mirror of your browser history.
If you want Hister to forget something, you must delete it from Hister itself. The web UI and terminal both support deleting indexed entries.
I actually like that design. If it deleted documents every time you cleared browser history, it would defeat one of its main purposes. It treats browser history as an ingestion source, not as the source of truth.
[6]
From the current documentation:
Are sources timestamped?
Yes.
Each indexed document records at least:
Added timestamp.
Updated timestamp.
For browser pages, the visit timestamp.
URL, title, and metadata.
Is there a TTL (auto-expiry)?
No.
I could not find any TTL, age-based expiry, or retention policy.
Documents remain until you delete them or overwrite them with newer content.
Can I set a maximum database size?
Not that I can find.
There is no option such as:
10 GB maximum.
Delete oldest first.
Keep only the last 365 days.
Limit to 1 million documents.
You can reduce storage by:
Disabling HTML previews.
Limiting indexed file size.
Restricting indexed file types.
Excluding paths or domains.
Can I cleanly delete by topic?
Partly.
You can:
Delete individual documents.
Delete crawl jobs (but not the indexed documents).
Label imported content.
Query by labels and metadata.
Configure rules to stop future indexing.
I did not find built-in support for bulk deletion such as:
“Delete everything about Tesla.”
“Delete all Reddit pages.”
“Delete every page tagged AI.”
The API may allow scripted deletion, but I did not see a first-class “delete by query” feature in the documentation.
Is browser ingestion automatic?
Yes.
That is one of its main features.
Once the browser extension is installed and pointed at your server:
Every page you visit is captured automatically.
The extension extracts the rendered page.
It sends it to Hister.
If the page later changes, the extension periodically checks it and updates the stored copy.
Duplicate visits update the existing document rather than creating a new one.
You do not need to press a button.
My only concern
This project feels like it is missing a lifecycle policy.
For a personal knowledge base, I would want options such as:
Keep browser pages for 90 days.
Keep GitHub forever.
Keep PDFs forever.
Delete pages that nobody has opened for two years.
Maximum database size: 20 GB.
Delete by label or query.
I could not find those features in the current documentation.
The project is very good at collecting information. It appears less mature at managing its lifetime. That would probably become the first thing I wanted if I intended to leave it running for years.
The summary has numerous inaccuracies. Most importantly: it is pretty easy to delete content by topic or age. The
hister deletecommand can accept a search query to remove only matched documents. The same is true on the web UI “actions -> remove all matching documents”. You can quickly filter by age, simply queryupdated:>365d. Combine it with URLs, labels, domains or phrases.Excellent - thanks for clearing that up.
Is there a TTL / max database size per user setting? Say I have 4 users using the server; can I allocate a hard limit of 10GB per user, with 180 day retention rules?
Additionally, is the other parenthetical information materially correct? If not, which points [1 thru to 7] are wrong?
I would like to further recommend Hister but your documentation is somewhat confusing at first blush.
Additionally, is the other parenthetical information materially correct? If not, which points [1 thru to 7] are wrong?
This is one of the problems with relying on AI… it can produce an overwhelming amount of content with errors and inaccuracies throughout. If you don’t review and know the content yourself, you won’t know what it got wrong.
It’s genuinely rude to lazily use AI to produce such a large babble of details and then ask someone else to review it for errors when you haven’t reviewed it yourself. I know you didn’t mean it that way but that’s nonetheless the result. People are going to read your comment and be misled about this project all because they assume AI is accurate and you didn’t review its results.
Edit: Sheesh… I hadn’t even got to your shitty comments that followed. You use AI to make a low effort but highly verbose post and then get mad that the repo author won’t review it in detail for you when you can’t be arsed with reading the docs yourself.
This is one of the problems with relying on AI… it can produce an overwhelming amount of content with errors and inaccuracies throughout. If you don’t review and know the content yourself, you won’t know what it got wrong.
Yep, and this induces anyone who wants to review the resulting slop to need to turn to AI as well to even deal with the amount (or dismiss as a whole).
AI is a viral infection on software development.
Yep… couldn’t agree more. I has its uses but too many people are using it and disconnecting their brain. Going to meetings where people have used it to determine requirements, do analysis or even transform data and then don’t even review the results themselves before presenting and asking us to review them is rage-inducing. “What do you mean it has problems? Where? What’s wrong??” And there’s like 5 things I’ve spotted in 2 minutes and it’s clear they’ve not even reviewed it themselves.
This guy and his long-ass, poorly formatted AI-generated “documentation” no one asked for and then after numerous errors are pointed out… “Will you review the rest?” The audacity!! 😄
This is my final reply in this thread. The developer has said their piece, and I have said mine.
I am a developer. I had genuine interest in this project. I read the Hister documentation and inspected parts of the repository because the documentation did not clearly answer several basic questions I had:
-
How SQLite, Bleve, and stored HTML relate.
-
Whether TTL or storage quotas exist.
-
How browser-history deletion affects stored data.
-
How previews differ from a real web archive.
-
What multi-user isolation actually covers.
Yes, I used AI to assemble a plain-language summary and labelled it accordingly. Not everyone keeps the Hister codebase in their head, not everyone talks in code review and if I had these questions, I’m willing to bet others did too. The AI wrote for a lay audience because I didn’t ask it to do QA, I asked it to ELI-5.
The summary contained errors. Fine. That’s AI for you. However, if neither I nor the AI could find clear answers, that supports my point about opacity.
At no point did I request a line-by-line audit. “Points 2 and 5 are wrong” would have answered the question.
Declining would also have been reasonable. Hell, side stepping it would have been fine too. Instead the dev decided to rudely brush them off.
That tells me about everything I need to know about the project.
Both you and the dev seem be under the impression !selfhosted is a one way distribution channel.
The developer came here, invited questions, then turned the raw prawn when questions arrived.
I didn’t go their their github. I didn’t abuse them. I genuinely want to know more about their project and share it.
They - and now you, ostensibly a happy supporter of Hister - came here.
Your claims about my effort and intent are assumptions followed by personal abuse.
Try and walk a mile in someone elses shoes before calling them low effort and shitty next time.
This could have gone very, very differently. Now, I’m not touching Hister with a 10 foot barge poll and will actively point people to other solutions at every opportune moment.
-
Is there a TTL / max database size per user setting?
As I wrote, you can simply automate deletion by document age. Schedule a delete event on each day with the desired retention time defined as a filter expression. Database size limit isn’t available yet.
Additionally, is the other parenthetical information materially correct? If not, which points [1 thru to 7] are wrong?
No, sorry, I don’t have time to correct a copy of a multiple screens long AI prompt.
I would like to further recommend Hister but your documentation is somewhat confusing at first blush.
Which parts are confusing?
I am happy to narrow it further.
The point is that you came here specifically to invite questions and feedback.
I took the time to read the documentation, ask ChatGPT to summarise what I found, and then reduced my follow-up to a simple request:
«Which of points 1–7 are materially wrong?»
That is not the same as asking you to audit “multiple screens” of AI output.
If the answer is “2 and 5 are incorrect”, or even “I do not have time to review it”, that is perfectly fine.
However, dismissing it as “a multiple screens long AI prompt” does not only not answer the question, it comes off as abrasive.
As for the documentation, the confusing parts are exactly those I listed: retention, lifecycle management, browser ingestion, storage limits, deletion, multi-user behaviour, and, most importantly, what Hister actually is and who it is for.
What’s disappointing is not that you disagreed with the AI summary. AIs are idiots.
It that after inviting questions and feedback, your response to a genuine attempt to understand the project was to dismiss it as “a multiple screens long AI prompt”.
That does not encourage the sort of community engagement you came here to seek.
However, dismissing it as “a multiple screens long AI prompt” does not only not answer the question, it comes off as abrasive.
I think it is more abrasive to copy/paste a poorly formatted LLM output instead of taking the time and summarizing it to a few sentences just as you did in your previous post.
That is not what happened.
I fed your GitHub repository to a clanker because the documentation did not answer my questions. I then shared its summary here.
You replied afterwards and said the summary was wrong. Fair enough. I then asked which specific points were wrong.
You could have answered, declined, or ignored the post.
Instead, you deigned only to dismiss the effort, then blamed me for objecting.
You also asked which parts were confusing, although my previous reply had already listed those issues.
You did not address them then, either.
A prospective user should not need ChatGPT, a cloned repository, and several follow-up questions to understand key functions.
You invited feedback. Your documentation remains unclear on several points, including issues beyond those I listed.
Your responses show that further feedback is not worth my time.
Feedback or questions is appropriate. We don’t need to come in abrasive, and you didn’t need chatgpt to ask a followup, so we don’t need to be antagonistic.
I’ve been running this for a while since I first heard of it, it’s already saved me a few times trying to recall a page for something.
I treat it like a more advanced history and it’s great!
The name reminds me of this crazy nostradamus “documentary “ that used to play on HBO when I was a kid.
Asciimoo always with the cool stuff!
Think I’ll try getting it setup on Kubernetes and using it for searching documentation when programming.
Would you be interested in getting a Kubernetes example in the docs too then? If you have any requirements for it let me know.
I’d appreciate it, thanks. No special requirements. Providing sensible defaults and explaining usage/potential customization options would be great.
If just it was called hipster
and utilized a rapper with backwards facing basecap and bling bling as logoLets see how it stacks up against the big ones
Already installed and loving this idea.
This seems super cool, you can curate your own search index :O
Being able to preview your search results offline is quite neat too!
One question though, how will you solve the issue of “echo chambers”, because from my understanding, it looks like it will only present results that you search for / have searched for, meaning for some people, you could be stuck with results that only support your view of the world.
I mean it kinda looks like that’s by design currently. It’s an indexer for your corners of the web, not a search aggregator to find new ones.
Exactly, the echo chamber phenomenon is mostly problematic for “discovery type” searches while Hister is mainly for “recall type” search.
Implementing federated search/index sharing could be a partial solution to this issue in the long run.
Oh damn this could replace the bookmakers. I have Linkding with the Linkding Injector extension, but this would be next level.
You can view the saved text too, nice. Would it be possible to attach an HTML file from like single file for sites that have heavy image content as part of the “view” button? That’d completely replace Linkding/Karakeep/Linkwarden use cases for me
Understandable if not, that’s ancillary to the text search focus
Oh damn this could replace the bookmakers.
The inspiration for Hister was a bookmarking app, but I realized that I always forget to manually trigger the bookmarking and I miss so many great resources.
Would it be possible to attach an HTML file from like single file
Currently you can import SingleFile HTMLs using the
hister import filecommand, but no further integrations are implemented yet. Although, rendering the exact SinglePage file as a preview can be added relatively quickly. It would be also nice to accept files directly from the SingleFile extension.Thanks for the good suggestion, I’ve added it to my TODO! =]
I have tons of webpages saved using the Firefox built-in page saver, which saves and html file and a corresponding folder for the other resources (images, javascript). Would be cool if these could be imported as well. Though maybe the resource folder can be ignored and the html file can already be imported?
Though maybe the resource folder can be ignored and the html file can already be imported?
It depends. Hister always requires a unique URL for each document. SingleFile snapshots include the original URL of the document as a meta HTML element. I’m not sure if the built-in page saver provides URL information.
Any interested in making this a federated search?
I’ve been toying with the idea of a web-ring style search engine where it uses the fediverse’s post and sub system so that you can subscribe to “indexers” that are made by other users (or even mastodon users themselves) so that you can have highly targeted search engine systems. So, for example, you could make multiple search “scopes” and each of those scopes would follow specific other “sources” and search from them. Likewise, users could provide links and descriptions to add new entries to each scope which would, in essense, work like a fediverse post and then be distributed to all other interested parties.
I haven’t done a lick of implementation yet, but thought I’d share the idea here as I consider doing this more and more every day. The only thing I haven’t figured out yet is images, because ideally that would be a special type of scope view.
Federated search is the direction I’d like to go when the core is mature enough.
I’m still trying to figure out the best approach to make the federation secure (no accidental private/confidential data leak) and easy to use. Related conversations: https://github.com/asciimoo/hister/discussions/432 & https://github.com/asciimoo/hister/issues/387 . I’d appreciate help to figure out an optimal solution.
I’d made a separate comment asking the same question, but glad to know you’re already working on this. Great work btw!
