Yihu History Guide: Find Replies & Compare Originals

Missing a reply? Check loaded pages, omitted text and authorized originals before trying again. Preview Yihu’s sample brief, review privacy, then explore App Store setup.

Preview privacy before you try

The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.

Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide

US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.

Check saved material before deciding to record or compare again

Source reply history is not a local full-archive search engine. Current target history loads read-only in pages of at most five; UI loads at most 100 entries. Longer text can be text_omitted with a pointer to the original. Existing authorized tools handle external archives. No match does not establish that an operation, material or feedback never existed.

Different from change-material retention

Retention maps conclusions to originals. Here retrieval coverage and manual comparison of matches matter. No index, archive database, restore service or full-text API is created.

Check Existing boundary Review Not established
Source history Target/current-source checks before loading Identity, target and access Global organization/task search
Pages Up to five with cursor rules Loaded/total and remaining pages First page is complete
UI cap At most 100 loaded Unloaded scope/original entries Nothing exists beyond cap
Omitted text text_omitted can indicate longer original Authorized original full text Empty display means empty original
Version consistency Paging checks totals/target version Recheck changes through original entry point Arbitrary-time pages form a stable whole
External archive Separate authorized tools Locations/date/version/alias coverage App has cross-account global indexing
Manual comparison Original references/version/actual text Same names, conditions and unknowns Similar prose means same approval/execution
No match Access/omission/loading/scope can limit results Record coverage and gaps Never occurred or safe to retry

Synthetic retrieval record

Location: loaded history for one sample target. Coverage: first five entries. Unknown: remaining pages/omitted text. Result: no match within this scope only.

Query/location/version/coverage are editorial labels, not app-issued search certificates. Do not publish private archives or expand third-party access to find full text. Similar words are not receipts, retrieval time is not event time, and no match cannot justify retrying uncertain operations.

FAQ

Does a 100-entry cap mean only 100 exist at the source?

No. UI loading differs from source total/unloaded scope. Unloaded is not absent.

Does a five-entry page include every task?

No. It is target history pagination, not global task search or a complete archive.

Can empty text with text_omitted be treated as an empty original?

No. Content was omitted; inspect the authorized original.

Can pages from different versions be freely combined?

No. Existing paging checks consistency. Mark cross-version manual material instead of claiming a stable whole.

Does no match prove nothing was sent?

No. Check coverage/prior evidence; no match bypasses neither reservations nor uncertainty.

Does Yihu supply archive full-text search and restore?

No such capability is added. External archives use existing authorized tools; source history remains read-only.

Reading and source

Change-material retention · Completion evidence · Time meanings · Confirmation scope · Start · Privacy

Loading cap/omission UI · Pagination/consistency model