Marmot-TS
    Preparing search index...

    A persistent GroupRumorHistoryBackend backed by any GenericKeyValueStore. Each rumor is stored under its own key (the rumor id), which makes addRumor idempotent: re-ingesting the same group message (e.g. during relay backfill) re-derives the same rumor id and overwrites the identical value rather than creating a duplicate timeline entry.

    Queries load every stored rumor and filter/sort in memory, so each query is O(n) in the number of stored rumors. This is intentionally simple and is good enough for client-side group history; swap in a indexed store if a group accumulates enough messages for the linear scan to matter.

    Implements

    Index