141–150 of 175 posts
> Newly-added seeds can start immediately and verify pieces on demand, instead of needing a full verify before seeding can begin. This is a huge annoyance for me with torrent clients. Files that are 80GB or larger take days to verify before they can seed. Having this feature (which makes sense to do) is a more sane way to do it.
Days? I don't think even my 2nd gen RPi hashes files that slow.
I don't remember why or how I ever picked up uTorrent, but that's the client I've always used. Thinking about torrenting just now, I realize I used to download torrents much more often than I do these days. I guess that's due to greater availability of video content on the streaming platforms and music on Spotify, etc.? What else do people use torrents for from a consumer perspective? Is there a wider everyday use ca…
I use torrents heavily despite subscribing to 4 different streaming services because I live in Canada and we don't yet have Hulu or HBO Max. Plus I also like watching some older movies via 2160p bluray rips and torrents are just the easiest option to do so. That plus it has everything. I use Transmission for torrents and then https://airflow.app/ to cast movies from my Macbook to my Firestick/Chromecast, which I find…
> The entire codebase has been migrated from C to C++. In the process, we've removed thousands of lines of custom code and used standard C++ tools instead. The core's code has shrunk by 18%. The core codebase has been extensively refactored to be more testable and maintainable. I love negative-LOC commits! They warm my heart. As do the people who take the time to make them.
> I love negative-LOC commits! They warm my heart. As do the people who take the time to make them. Agreed, but only if there's adequate test coverage and it's pretty clear how everything should work. Otherwise it's a very stressful experience, working with a seemingly brittle and puzzling codebase.
Earlier quoted context omitted.
It's not anymore. See https://github.com/transmission/transmission/issues/597 , tagged "pr welcome".
sure... the code fix has been around for over 15 years at this point. Its even in their old tracker wiki Replace: /* otherwise go with our random seed / return tr_compareUint16( a->random, b->random ); With: / otherwise download the pieces in order */ return tr_compareUint16( a->piece, b->piece );
Honest question. What kinds of things are people using torrents for in 2023?
> The entire codebase has been migrated from C to C++. In the process, we've removed thousands of lines of custom code and used standard C++ tools instead. The core's code has shrunk by 18%. The core codebase has been extensively refactored to be more testable and maintainable. I love negative-LOC commits! They warm my heart. As do the people who take the time to make them.
3.9M static binary for 2.84
9.0M static binary for 4.0.0
Earlier quoted context omitted.
At my previous job, we re-did some Java stream processing stuff in Clojure. We added functionality, made it more stable and dropped 6K lines of code (out of 18K for that particular component) in the process. It felt like magic...
That's not a fair comparison, rewriting anything in any lisp will dramatically reduce the amount of cruft, both lines of code and complexity.
Earlier quoted context omitted.
sure... the code fix has been around for over 15 years at this point. Its even in their old tracker wiki Replace: /* otherwise go with our random seed / return tr_compareUint16( a->random, b->random ); With: / otherwise download the pieces in order */ return tr_compareUint16( a->piece, b->piece );
Surprisingly trivial. Hopefully, someone who cares about this will contribute!