RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Claude Mem] Preserve historical timestamps when ingesting archived transcripts

Thread the original timestamp from JSONL transcript entries through the full observation pipeline so that archived sessions retain their real dates instead of the import time. Add resolveEntryTimestamp() to TranscriptEventProcessor and override_timestamp_epoch to ObservationData, PendingMessage, and the /api/sess endpoint.

Original Source

@@thedotmack | 0 pts | 1d ago

**Type:** feature / enhancement request (re-filed from maintainer's own PR during backlog cleanup) ## Summary - Thread the original `timestamp` from JSONL transcript entries through the full observation pipeline so archived sessions get their real dates, not the import time - Add `resolveEntryTimestamp()` to `TranscriptEventProcessor` that checks schema-configured fields and common JSONL timestamp paths - Add `override_timestamp_epoch` to `ObservationData`, `PendingMessage`, and the `/api/sessions/observations` endpoint - `PendingMessageStore.enqueue()` uses the override timestamp for `created_at_epoch` when provided, falling back to `Date.now()` ## Motivation When importing archived transcript JSONL files (e.g., from `~/.claude-mem-backup/archives/`), all observations were stamped with the current time instead of their original dates. This made historical session data useless for timeline queries and date-based search. ## Test plan - [ ] Import an archived JSONL transcript and v

Discussion

Loading comments...