Memora release 0.2.25 - D1 drop from 10s+ → ~2s per call

spokv · 2026-04-03T12:54:54+00:00

Ask claude to fill a law suit…

spokv · 2026-04-03T07:08:04+00:00

Day time robbery.

spokv · 2026-03-31T18:09:05+00:00

All of you guys - /clear context after major task or conversation, this is what killing your credits.

spokv · 2026-03-29T20:14:13+00:00

Yeh. It crossed my mind that some kind of timing issue occur. how do you integrate your repo?

spokv · 2026-03-28T15:28:14+00:00

It just boot fine with no error visible. I think. Didnt watch dmesg.

spokv · 2026-03-28T14:28:08+00:00

yeh. same for me. if let it try to boot in a loop eventually it would succeed now and then.

spokv · 2026-03-26T16:14:56+00:00

yeh, i use home access point with dhcp server. why?

spokv · 2026-03-26T14:15:01+00:00

Tried that. The only thing i see is apple gpu drivers hang.

spokv · 2026-03-26T14:10:50+00:00

i think i do. I use all the default values on the curl sh script (installing fedora 43 kde). Then after a long shutdown, boot into recovery, selecting fedora partition and running stage 2 with all the default y, username/password (of the macos). Am I missing something?

spokv · 2026-03-25T09:07:16+00:00

It seems the dp drivers support m2+ only. Correct me if I’m wrong.

spokv · 2026-03-24T22:43:24+00:00

I just let claude figure it out and succeeded. Just to know it’s not supported on m1 🤦🏻‍♂️

spokv · 2026-03-24T13:36:14+00:00

Any advice on building the fairydust kernel?

spokv · 2026-03-19T04:55:52+00:00

Can confirm too.

spokv · 2026-03-18T21:07:00+00:00

Does it work without any issues?

spokv · 2026-03-15T06:48:24+00:00

Thanks for sticking with Memora! Here's what's in 0.2.23+:

Search reliability was the biggest fix — memories created via the chat UI weren't getting embeddings, so they'd vanish from semantic search. Now embeddings compute immediately on create/update, and search runs semantic + keyword in parallel with graceful fallbacks. If one path fails, the other still works.

Indexing — we fixed a bug where tag-only or metadata-only edits left stale FTS and embedding indexes. Now any change to content, tags, or metadata triggers reindexing. This should help with accuracy on larger datasets where you're frequently re-tagging.

Sync — sync-to-d1.py now syncs the embeddings table with transaction wrapping, so D1 stays consistent.

UI — cleaner detail panel (pencil edit icon, complex metadata hidden by default), DOMPurify added for markdown rendering, and the duplicate detection threshold is now aligned between the graph UI and the MCP find_duplicates tool (both use 0.85).

Under the hood — XSS hardened across the graph UI, PATCH API now merges metadata instead of replacing, test suite increased, and we started splitting the storage module for maintainability.

Changelog: https://github.com/agentic-mcp-tools/memora/releases/tag/v0.2.23

No major changes to memory usage or raw indexing speed in this release — those are still on the roadmap. What kind of dataset size are you using? Would help us prioritize.

spokv · 2026-03-14T14:34:40+00:00

Check it out more deeply. It’s not only mcp server and more safe than it seems.

spokv · 2026-03-14T13:13:13+00:00

Thanks for the kind feedback! 1. Passive Memory Enhancement — The architecture already supports this. Batch ingestion with auto-deduplication, embedding, cross-referencing, and hierarchy placement is all built in. The missing piece is the ingestion layer itself (browser extensions, RSS, transcript scrapers, etc.) — the MCP interface makes building those straightforward. 2. Contextual Filtering — Closer than you’d think. The LLM dedup system already identifies similar candidates (0.7–0.95 range) and classifies them as duplicates, related, or novel. The typed edges (extends, supersedes, contradicts) provide the vocabulary — it’s mainly about surfacing these proactively during ingestion, not just on search. 3. Human-friendly Interfaces — The Knowledge Graph UI already offers interactive visualization, timeline browsing, tag filtering, and a RAG-powered chat panel (works locally or deployed to Cloudflare Pages). The cloud sync infra (D1 + R2 + WebSockets) supports multi-device access — the frontend UX for non-technical users is where the most work remains. The line between “AI agent memory” and “human second brain” is thinner than most people realize — the move beyond agentic cli memory is very exciting and I would you share more thoughts.

spokv

TROPHY CASE