Grimoire: Open-Source bookmark manager with extra features

An open-source bookmark manager called Grimoire is drawing interest for its playful “magical” theme and self-hosted design, but many note it’s still early-stage, lacking essentials like browser extensions, imports/exports, and full documentation. Commenters use it as a springboard to debate how people actually use bookmarks today, contrasting minimalist “no bookmarks” habits with elaborate workflows built on tools like Zotero, Raindrop, Pocket, Shiori, and Obsidian-based setups. A recurring theme is frustration with browsers’ weak native bookmark management and a desire for better search, automation, and local archiving—ideally without sacrificing usability or control over one’s “digital brain.”

Project & Feature Set

  • Grimoire is an open‑source, self‑hosted bookmark manager with a strong “magical” theme that some find memorable and appealing.
  • Current state is considered early: documentation is incomplete, and some see it as closer to a polished demo with dashboards and stats than a fully featured tool.
  • Roadmap includes sharing, import/export, bookmarklets, browser extensions, and better docs.
  • Screenshots show card‑style previews and metrics, which some like, but several say a browser extension is essential before they’ll seriously try it.

How People Actually Use (or Don’t Use) Bookmarks

  • A notable group has largely abandoned bookmarks, relying instead on open tabs, search history, or external read‑later tools; some find full abandonment freeing.
  • Others are heavy bookmark users, treating bookmarks as:
    • Long‑term memory and personal archive (often with backups or snapshots).
    • A small set of “speed dials” on the bookmark bar.
    • A flat, tag‑based dump searched later rather than carefully organized hierarchies.
  • Several mention copying page content locally (markdown, Obsidian, Logseq, Zotero snapshots) rather than trusting URLs to persist.

Perceived Failures of Browser Bookmark UX

  • Many see built‑in bookmark managers (folders, basic dialogs) as clumsy and discouraging to use at scale.
  • Search within browser bookmarks is described as inconsistent: some report Firefox working well, others see performance and relevance problems.
  • There is debate on why browsers haven’t improved this:
    • One view: search‑engine‑driven business models discourage powerful bookmarks because they reduce repeated searches.
    • Others argue it’s more about differing user needs and scope creep.

Desired Capabilities & Alternatives

  • Commonly requested features for any bookmark manager:
    • Deep browser integration (extensions, address‑bar search, tags).
    • Local archiving/snapshots and full‑text search, possibly LLM‑augmented.
    • Easy import/export and cross‑device sync.
  • Many alternatives are mentioned (e.g., Raindrop, Shiori, Shaarli, xBrowserSync, Zotero, Pocket/Omnivore, Obsidian+MarkDownload, Logseq), often with trade‑offs around UX, openness, and longevity.

Self‑Hosting, Docker, and Security

  • For self‑hosters, a server component is “just CRUD for links”; the real value is extensions/mobile apps.
  • Docker as the primary install method is polarizing:
    • Some see it as a red flag for dependency bloat.
    • Others prefer Docker for isolation, reproducibility, and easy cleanup.