uosc VS webtorrent

Most of those features are available in OSS tools as well. And for those that are not, there are alternative solutions that might take a bit of work to implement.

I'm not claiming that the OSS tools have feature parity with 1st party frontends, or that they won't require some sacrifices, or effort adjusting. I just think that the trade-off of losing some of the convenience in return for not being tracked and manipulated is well worth it to me, though I can see how it might not be worth it for others.

I do actually think that OSS tools provide a better UX. I can download the media and consume it offline, using any player of choice, on any device, at any time. I find YouTube's recommendations a nuisance, and I can turn those off in Invidious and Piped. Scrubbing in mpv is instantaneous for me for local files and even those served on the LAN, though there is a slight delay when playing directly from YT. There is also a solution for generating thumbnails[1], though I had some issues with it, and didn't end up using it.

At the end of the day, it's a personal choice depending on what you value most, and I'm not trying to convince anyone my choice is inherently better. Thanks for providing your perspective.

[1]: https://github.com/tomasklaen/uosc

Check out uosc, it has a button for the next file.

uosc adds a customisable ui, making mpv more accessible to beginners.

Then another great starting point imo is to just install this script actually. Its a ui script and is really customisable and nice. https://github.com/tomasklaen/uosc

so recently I am using a UI called uosc and I want to add a play/pause button to the control bar, i asked the UI Developer and he said what's shown in the picture: -Can someone show me how to do it correctly ?

You have to use a ui like uosc. https://github.com/tomasklaen/uosc

This one is pretty neat.

Not a gradient but you can change the colour if you use the uosc gui which comes with a bunch of other features.

For beginner, I always suggest them to install uosc because it lowers the learning curves: https://github.com/tomasklaen/uosc

It's because of the kind of content that is shared. BitTorrent serves a lot of content you are not allowed to redistribute, so having an open gateway immediately puts you at risk of aiding the distribution of content. But it does work, someone even made something native to browsers so browsers themselves can share content: https://webtorrent.io/. There are even fuse "gateways" to make it native to your computer and pretend the files exist locally: https://github.com/search?q=bittorrent+fuse&type=repositorie...

IPFS doesn't seem to be used for that kind of content much, it seems to be targeted more towards web-native content (html pages, images, that kind of stuff). It's probably safer for Cloudflare to run this.

title. I have some experience with c++ but not much with torrent libraries. (webtorrent, stremio)

You can stream torrents

If it fits your model, WebTorrent[0] can offload a lot of bandwidth to peers.

[0] https://github.com/webtorrent/webtorrent

Then https://github.com/webtorrent/webtorrent could be used to actually download the videos in browser, the idea being here though, that you would at least seed out as much as you got. Enabling other's to access videos without requiring creators have the infrastructure to push a video to 1000s or more clients at once.

I assume you've seen https://webtorrent.io/ ?