compression too weird, back to mp4

Author: Sheraff

public/blog-assets/tanstack-router-signal-graph/after-granular-store-graph-2.mp4

@@ -44,7 +44,7 @@ Routing is not one thing that changes all at once. A navigation changes specific
 The old model captured those pieces of state, but it flattened them into one main subscription surface. This is where the mismatch becomes visible:
 
 <figure>
-<video src="/blog-assets/tanstack-router-signal-graph/before-granular-store-graph-2.webm" playsinline loop autoplay muted></video>
+<video src="/blog-assets/tanstack-router-signal-graph/before-granular-store-graph-2.mp4" playsinline loop autoplay muted></video>
 <figcaption>
 A video showing that on every stateful event in the core of the router, changes are propagated to every subscription across the entire application.
 </figcaption>
@@ -67,7 +67,7 @@ The broad surface is split into smaller stores with narrower responsibilities.
 The new picture looks like this:
 
 <figure>
-<video src="/blog-assets/tanstack-router-signal-graph/after-granular-store-graph-2.webm" playsinline loop autoplay muted></video>
+<video src="/blog-assets/tanstack-router-signal-graph/after-granular-store-graph-2.mp4" playsinline loop autoplay muted></video>
 <figcaption>
 A video showing that on each stateful event in the core of the router, only a specific subset of subscribers are updated in the application.
 </figcaption>