![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/h1ChnLuBHr.png)
Because it’s actually really hard to achieve technically. When ads are served outside the stream you can easily serve different ads to different viewers based on their profiles. When the ads are baked into the stream you can either
A) Create a whole bunch of different copies of the video asset with different ads baked in and then rotate these on a regular basis. Which would be expensive to update and store and limit the range of adverts that could be served to a particular user.
B) Dynamically create a stream on the users request, which while possible means standard CDN caching isn’t going to work so there’s a distribution challenge.
Or some other alternative they’ve come up with. I’d be really interest to know what their approach is here.
43% of Google traffic is now ipv6 and steadily growing
https://www.google.com/intl/en/ipv6/statistics.html
CGNAT is only a temporary band aid for reaching services that are yet to present themselves on IPV6. It’s relatively expensive to operate.
IpV6 might be largely pointless on a LAN, and sure NAT is fine there, but ipv6 already running large chunks of the world’s mobile infrastructure. It’s not going anywhere.