Use what you remember
An account removes unrelated authors from the results. A date range narrows an event. A phrase helps when a screenshot or saved quote includes the exact wording.
Start with one of these queries. Read the candidates before adding another condition.
Use the account's handle after `from:`, without the @. A display name may identify several different people.
| Your clue | Query to adapt | Next step |
|---|---|---|
| Account and topic | from:OpenAI GPT-4o | Add a date range if there are too many results. |
| Account and a phrase | from:OpenAI "voice and vision" | Drop the quotes if the wording is approximate. |
| Date and topic | GPT-4o since:2024-05-13 until:2024-05-14 | Look for the author you remember. |
| Only the account | from:OpenAI | Add the rough month, a word, or a media filter. |
Set the date range, including its end
`since:2024-05-13 until:2024-05-14` includes May 13 and stops before May 14. For one day, set `until:` to the following day. For a month, use the first day of the month and the first day of the next month.
A post's displayed day can change with the viewer's timezone. If a screenshot says May 13 but the one-day query is empty, try `since:2024-05-12 until:2024-05-15`. That covers the previous day, the remembered day, and the following day.
In CarryFeed Advanced Search, the From date and To date fields compose these operators. The To date is the first day outside the range.
| Period you remember | Date portion |
|---|---|
| May 13, 2024 | since:2024-05-13 until:2024-05-14 |
| A day either side of May 13 | since:2024-05-12 until:2024-05-15 |
| May 2024 | since:2024-05-01 until:2024-06-01 |
An old launch post: from query to source
A saved CarryFeed search check from July 2, 2026 used `from:OpenAI GPT-4o since:2024-05-13 until:2024-05-14`. The local /api/search request returned HTTP 200 and 12 results. The first five candidates are listed below; their saved excerpts describe several different parts of the launch.
If you remember an announcement about who would receive access, the first candidate is the useful match. The other four concern demonstrations and audience requests. Matching the account and date alone would leave you with several plausible posts; the wording of your question separates them.
The source post has ID 1790130708612088054 and a publication timestamp of May 13, 2024 at 21:23:14 UTC. In a timezone eight hours ahead, that timestamp falls on May 14. This is why widening a remembered date can help.
Open the candidate and compare its account, wording, date, and attachments with your memory. Once it matches, copy the status URL. You can return to that link without repeating the search.
The 12-result count and order belong to the July 2 capture. When repeating the query, keep the matching post URL and your own search date even if the result count has changed.
| Candidate | What the saved excerpt describes |
|---|---|
| 1. GPT-4o access announcement | Access beginning for all users that day; new voice and vision capabilities planned for ChatGPT Plus in the coming weeks. |
| 2. Vision audience request | A live audience request involving GPT-4o vision. |
| 3. Realtime translation request | A live audience request involving realtime translation. |
| 4. Vision demonstration | A live demonstration of GPT-4o vision. |
| 5. Voice variation demonstration | A live demonstration of GPT-4o voice variation. |
Add an attachment clue when the results are noisy
If you remember a chart, use `from:handle filter:images`; for a demo clip, try `filter:videos`. Add the date range when you know it. If those filters remove all candidates, go back to the account and dates and inspect the attachments.
For a linked report, try `from:handle filter:links` with distinctive words from the report title. A remembered domain can help too, though short links and redirects can make it a weak filter.
| Remembered attachment | Query shape |
|---|---|
| Photo or chart | from:handle filter:images since:YYYY-MM-DD until:YYYY-MM-DD |
| Video | from:handle filter:videos topic |
| Article or report | from:handle filter:links title-words |
| Campaign hashtag | from:handle #tag since:YYYY-MM-DD |
If the post still does not appear
If you already have the direct status URL, open it first. A readable post gives you the source even if it never appears in the query results.
Otherwise, keep your best clue and loosen one condition. A short search trail helps you see which change worked.
X documents search restrictions that can affect results. If a broad query still produces nothing, record the query as unresolved rather than repeatedly adding filters.
| What failed | Change next |
|---|---|
| One-day search | Include the previous and following day, then try a week. |
| Quoted phrase | Remove quotes or keep two distinctive words. |
| Media or link filter | Remove it and inspect the account/date results. |
| Everything under one handle | Check the original link or account identity for a renamed handle. |
| Direct source is protected or unavailable | Use authorized X access if you have it, or choose another public source. |
Keep the URL with the note you needed
For a quick note, the final post URL and the reason you saved it are usually enough. Add the query when another person may need to retrace the search. Add the source date when timing matters.
The example below is a reusable note for the OpenAI post. Fill in the capture date only when you actually read or save it.
Open the found link in the Twitter Viewer to read the returned text and export Markdown. For an AI task, the ChatGPT source guide shows a compact prompt that keeps the link with the summary.
source_url: https://x.com/OpenAI/status/1790130708612088054
posted_at: 2024-05-13 21:23:14 UTC
query: from:OpenAI GPT-4o since:2024-05-13 until:2024-05-14
why_saved: Announcement of GPT-4o access and the planned voice/vision rollout.
captured_on: [date you opened the source]