Why Nostr? What is Njump?
2024-03-09 02:15:58
in reply to

Mitch Downey :pci: on Nostr: npub1dznhh…v4dfn npub10fp3e…4qqev npub1zyl79…jmw3t npub1vpkys…g092y ...



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
Author Public Key
npub1yfr5d05qj3qzz84kntze3c8accyz0unwczgm0fxuypuqdnenkwuqew6g6v