Mitch Downey :pci: on Nostr: npub1dznhh…v4dfn npub10fp3e…4qqev npub1zyl79…jmw3t npub1vpkys…g092y ...
npub1dznhhga669k20k8rjzmls6lu5uhkus9s3xcg3t2f3quswnc2sdqs5v4dfn (npub1dzn…4dfn) npub10fp3ehl8utp98zgk6lx87uwkfxm9zq6z9varapeuluz9cdf3zfvs94qqev (npub10fp…qqev) npub1zyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92stjmw3t (npub1zyl…mw3t) npub1vpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrsqg092y (npub1vpk…092y) npub1s0l2l0skj3k5czyrxgese57xy6ghmmkjv5hcs9a5ul0d8jrvq8vq6pzquj (npub1s0l…zquj) npub1ln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204q45xyw6 (npub1ln5…xyw6) npub1df6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyqfgns3a (npub1df6…ns3a)
metadata preload request uses the request header "Range: bytes=0-" to request the beginning of the file where metadata is contained, but the actual playback requests will use a different header with a greater than 0 value like "Range: bytes=3145728-".
Would it be possible for OP3 to discard requests when "Range: bytes=0-", but count requests when Range is greater than 0? We'd like to keep the UX benefits of metadata preloading if possible
metadata preload request uses the request header "Range: bytes=0-" to request the beginning of the file where metadata is contained, but the actual playback requests will use a different header with a greater than 0 value like "Range: bytes=3145728-".
Would it be possible for OP3 to discard requests when "Range: bytes=0-", but count requests when Range is greater than 0? We'd like to keep the UX benefits of metadata preloading if possible