Mixer pipeline

The mixer is the client-side stage that turns stored corpora into the scrollable Home feed.

Data flow

┌─────────────────┐     ┌──────────────────────┐
│ Live X API      │     │ Grok topic ticks     │
│ (refresh)       │     │ (background)         │
└────────┬────────┘     └──────────┬───────────┘
         │                         │
         v                         v
┌─────────────────┐     ┌──────────────────────┐
│ ifixedx_local   │     │ thefeedtrix_local    │
│ posts           │     │ tf_canonical_posts   │
└────────┬────────┘     └──────────┬───────────┘
         │                         │
         └──────────┬──────────────┘
                    v
         mergeFeedWithUnseenCanonicalFirst
                    │
                    v
         buildMixerFeedPostsBase (tab / time / topics)
                    │
                    v
              feedPosts (UI)

Layers

Live layer

  • In-memory platform / refined from last API response.

  • Persisted to posts via persistComparePayload.

  • Rehydrated on Home open — no manual Load required after first ingest.

Pipetrix layer

  • Canonical store: deduped tweets from all ingest paths.

  • Background Grok fills topic buckets (tf_posts) then canonical ingest.

  • Subscribed reactively — UI updates when new rows land.

Remix rules (Home)

  1. Unseen canonical first (newest), optionally shuffled with feedRemixEpoch / page-load salt.

  2. Live corpus appended without id collisions.

  3. Seen canonical tail (unless “include seen” enabled).

Explore and other pages merge canonical without the unseen-first preference.

Refresh source vs mixer

Control

Effect

Timeline refresh source

Which API repopulates the live layer

Top / Latest / Media tabs

Which ranked list and time window

iFixedX rank chip

platform_style vs refined ordering