Fe₂🦀₃⋅H₂🦀 Nozakero Matty-kun d Twitch can get away with it because they ...

Why Nostr? What is Njump?

npub1w7…rpc4w

2023-10-21 01:02:29

in reply to nevent1q…f23s

Fe₂🦀₃⋅H₂🦀 (npub1y6t…9wl9) Nozakero (npub1dph…t7jj) Matty-kun (npub13v6…hy07) d (npub15fk…j9gr) Twitch can get away with it because they specialize in live, low latency content. It doesn’t really take all that much effort to bake ads into streaming video. Basically every contemporary video hosting site uses a streaming method where the client gets a playlist file that points to a bunch of ~1 second .ts video files and stitches them together locally. It’s simple enough to just replace some of the original .ts files with ad ones. Although, once you start serving the same file multiple times, this trick becomes easy to circumvent as ads are most likely going to change between watches, so a client can just keep re-downloading the playlist and discarding .ts files that are rarely present. Even if you keep all the URLs the same and replace the bytes that the server sends, a client can still just check the first couple of them and work off of that. Clients can also get together and generate and store their own playlists via consensus (imagine an ad blocker that works like sponsor block but completely automatically).

Author Public Key

npub1w7x9m8xutlezyzmu7d78d8ygzk6sdpncfuuds8jsz2wnwk8f52dqkrpc4w

Show more details

Published at

2023-10-21 01:02:29

Kind type

1 Short Text Note

Event JSON

{ "id": "a3dcd69038e1cf111027283ca7f7cf43d64f521ffbeaf0ad50dcdd8576025c7f", "pubkey": "778c5d9cdc5ff2220b7cf37c769c8815b50686784f38d81e50129d3758e9a29a", "created_at": 1697850149, "kind": 1, "tags": [ [ "p", "26976d1f3f3270311c86a59315751d66bd770aa35a929529271fca721afee1af", "wss://relay.mostr.pub" ], [ "p", "686fc46eeac9cfcc7a6bfa61291b2082d8707c55c45e2e032f139ce0194647b6", "wss://relay.mostr.pub" ], [ "p", "8b347916be2cb3ab9687c9eb78a8d05224c045bce5b416bdd50169965eb0f45c", "wss://relay.mostr.pub" ], [ "p", "a26d9180040977fbfa673374da58b057b2be33bd1b2615301969e2d7171a7c42", "wss://relay.mostr.pub" ], [ "e", "e0f57c62ffde4a7030366d302c9b52a3e8017ec556773ce0e4e7a4cd26919e9c", "wss://relay.mostr.pub", "reply" ], [ "proxy", "https://social.singing.dog/objects/475e76c3-4ed2-4467-aa07-e75121d95b0f", "activitypub" ] ], "content": "nostr:npub1y6tk68elxfcrz8yx5kf32agav67hwz4rt2ff22f8rl98yxh7uxhsx69wl9 nostr:npub1dphugmh2e88uc7ntlfsjjxeqstv8qlz4c30zuqe0zwwwqx2xg7mqhut7jj nostr:npub13v68j9479je6h958e84h32xs2gjvq3duuk6pd0w4q95evh4s73wqk2hy07 nostr:npub15fkerqqyp9mlh7n8xd6d5k9s27etuvaarvnp2vqed83dw9c603pqs5j9gr Twitch can get away with it because they specialize in live, low latency content. It doesn’t really take all that much effort to bake ads into streaming video. Basically every contemporary video hosting site uses a streaming method where the client gets a playlist file that points to a bunch of ~1 second .ts video files and stitches them together locally. It’s simple enough to just replace some of the original .ts files with ad ones. Although, once you start serving the same file multiple times, this trick becomes easy to circumvent as ads are most likely going to change between watches, so a client can just keep re-downloading the playlist and discarding .ts files that are rarely present. Even if you keep all the URLs the same and replace the bytes that the server sends, a client can still just check the first couple of them and work off of that. Clients can also get together and generate and store their own playlists via consensus (imagine an ad blocker that works like sponsor block but completely automatically).", "sig": "2b2cd86c4035ed1fb1a91cd18ad2080945975b1bf52096e5cf98e9670d6ce4444ebbd1068714a895f690d7600cf86b0fab2525487971d089d71664b0ab17d70f" }