The feed before the history
Wikipedia can flatten a war into dates: 28 February to 17 June 2026, U.S.-Israeli strikes, Iranian retaliation, Hormuz, ceasefire, blockade, memorandum. The feed felt different. It arrived as statements, clips, triumphal captions, warnings, corrections, and arguments about what the same event meant.
So this post is not trying to be the complete war. It is my personal archive of the way the war sounded on X.
The timeline tells me what happened. The tweets tell me what people were being asked to believe while it happened.
1. The opening: Operation Epic Fury
Wikipedia places the order for Operation Epic Fury on 27 February and the opening U.S.-Israeli strikes on 28 February. The tweet record begins with the war being packaged before most people could process the facts.
What I notice now: the first feed already contained both escalation and exit language. Strike hard, then talk about off-ramps. That rhythm never really went away.
2. Retaliation becomes regional
The Wikipedia page describes Iranian strikes on Israel, U.S. bases, and U.S.-aligned Arab countries, plus disruption around the Strait of Hormuz. On X, the regional expansion showed up as a scroll of clips, OSINT maps, casualty claims, and competing victory statements.
The feed made the war look cleaner than the geography. In reality, every new target expanded the number of governments, civilians, air-defense systems, ports, refineries, and insurance markets pulled into the story.
3. The battlefield moves into Hormuz
Wikipedia treats Hormuz as one of the war's central economic pressure points: Iran obstructing passage, the U.S. later announcing a naval blockade, and both sides using the strait as leverage. On X, Hormuz became the symbol everyone could understand without reading a defense brief.
The language was absolute. The physical reality was not. A chokepoint is not controlled by a sentence; it is controlled by ships, mines, drones, insurance, and whether captains believe tomorrow will be calmer than today.
4. The April ceasefire that did not feel like peace
Wikipedia marks 7 April as the first fragile ceasefire, mediated by Pakistan, followed immediately by dispute over whether Lebanon was included. The tweets read like two different wars: the official war being paused and the regional war still moving.
This is the hinge of the tweet archive for me. The same day could be announced as de-escalation by one account and described as a loophole by another. The feed did not contradict itself by accident; the agreement itself was unstable.
5. Lebanon breaks the frame
Wikipedia notes that Israel-Lebanon fighting and Hezbollah activity kept pulling the war away from a simple U.S.-Iran bilateral story. On X, Lebanon became the test of every ceasefire claim.
If a deal says war is ending on all fronts but one front keeps burning, the feed becomes the audit trail. It shows where the diplomatic sentence failed to match the ground.
6. June: the deal becomes content
Wikipedia says the U.S. and Iran announced the Islamabad Memorandum on 14 June, signed it on 17 June, and CENTCOM announced removal of the naval blockade on 18 June. The feed turned this into a competition over ownership of the ending.
The ending was not one message. It was a stack of claims: complete deal, not a peace deal, ceasefire, memorandum, Hormuz reopening, nuclear talks later. That stack is why I trust the timeline more than the victory captions.
7. The argument after the announcement
After the deal posts came the interpretation posts. This is usually where the first draft of history gets loudest: supporters call the outcome peace, critics call it avoidable, diplomats call it fragile, and everyone chooses the comparison that helps their side.
The postwar feed is where the war becomes a lesson before anyone agrees what the lesson is.
My read, after rebuilding this as tweets
- The feed made the war feel more decisive than it was. Official posts were written in absolutes; the timeline is full of reversals and unresolved clauses.
- Hormuz was the cleanest symbol because it compressed war, oil, shipping, and inflation into one map point.
- Lebanon was the stress test. Every claim that the war was ending had to survive what Israel, Hezbollah, Iran, and mediators said about that front.
- The same tweet format carried incompatible roles: command statement, battlefield clip, diplomatic leak, protest, endorsement, and historical verdict.
- Wikipedia is useful here because it slows the feed down. X shows the psychological weather; Wikipedia gives the dated skeleton.
Source spine
- Wikipedia: 2026 Iran war
- Wikipedia: Timeline of the 2026 Iran war
- Embedded X posts are included above as public artifacts from the war narrative.