LostaFound

How to use LostaFound

Claims, matching and recovery behavior

  1. An item inquiry can become an ownership claim using This may be mine with new private details. The existing messages and original evidence remain private in the same thread. Closed inquiries can restart while the report remains available; closed claims require new claim evidence. Rejected claims stay rejected, including after report renewal. Block a participant to prevent further contact; closing a thread alone is not a block.
  2. Matching alerts scan at most 500 candidates per subscription on each worker pass, continuing from a saved ID cursor and wrapping at the end. Crowded areas can take multiple passes. Updating subscription criteria resets progress; private, blocked and inactive items remain excluded.
  3. Admin photo changes update the item timestamp and gallery revision. If a stale form is rejected, reload and review the new pictures before saving. If a backup worker is interrupted, its abandoned running job becomes Failed on the next worker/new request. Inspect partial recovery output; restores are never retried automatically.
  4. The deployment API explicitly reruns diagnostics, subject to the one-minute cooldown. Scheduled diagnostics still reuse unchanged release results. Website, Android WebView and iPhone web-app screens share these fixes on an online reopen or Refresh; no new native package is needed.

Open feature · All guides