Cas_

question: why? if subs are saya 80MB, then you won't be able to render them anyways because of lag

that's what the createEvent API is for: from any EBML parser output: ```js const stylesMap = [{ style: 'yourstyle' }] function constructSub (subtitle, subtitleIndex, trackNumber) { return { Start: subtitle.time,...

imho jellyfin should parse the subtitles client-side not server-side, what you're suggesting is a lazy fix, rather than a solution and it doesn't sit well with me it's not that...

> It's a seamless optimization for slower networks and hardware, not a lazy fix what I mean by "lazy fix" is that you really should append new subtitles, rather than...

It deletes the existing track and overwrites it with new content, instead of appending new content, which I feel defeats the purpose of this as if the file is large...

> How would the subtitles be parsed client side? you can honestly use any proxy for the file being loaded, eg: This is the code I run every time a...

> **🚨 Potential security issues detected.** Learn more about [Socket for GitHub ↗︎](https://socket.dev?utm_medium=gh) > > To accept the risk, merge this PR and you will not be notified again. >...

not sure what to tell you 

I think this is something to bring up with [node-datachannel,](https://github.com/murat-dogan/node-datachannel/) not webtorrent

> where `simple-peer` is not used it is used, ws trackers were always supported in node.js, simply webrtc wasn't, now that it is, ws trackers work correctly too