libtorrent
webtorrent-desktop
libtorrent | webtorrent-desktop | |
---|---|---|
37 | 18 | |
5,026 | 9,584 | |
- | 0.4% | |
8.2 | 6.7 | |
7 days ago | about 1 month ago | |
C++ | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libtorrent
-
Why is QBitTorrent so worshipped? Genuinely asking from someone who has used uTorrent for a few years.
I had a longer answer, but qBittorrent is great and has a great webui/server model if you're running a separate linux box to run it in. If you're on windows, grab 4.3.9 or 4.6.2 with libtorrent 1.x. RSS stuff is nice too. Libtorrent 2.x has issues on Windows currently (read these threads if you want to know more - https://github.com/arvidn/libtorrent/pull/7013 - https://github.com/arvidn/libtorrent/issues/6667#issuecomment-1804035311 ). Please don't bug Arvid about it though. Libtorrent 2.x gets us Bittorrent v2, which is a good thing.
-
Is v4.5.0 usable again? There have been connection / speed issues with v4.4.x
Latest libtorrent v1.2 branch changelog: https://github.com/arvidn/libtorrent/blob/RC_2_0/ChangeLog
- Unstable or zero speed and speed loops downloading with qBittorrent 4.5.0, but fast seeding; now using uTorrent for downloading
-
Do we have any developers willing to greatly help BitTorrent community [Interesting challenge]
You can support this feature by writing a comment in https://github.com/arvidn/libtorrent/issues/7252
Where users could finally download files that were present in other swarms. This would decentralize network more, swarms with valuable files wouldn't die fast, even when updating a torrent, where info hash differs, say tv series, adding new episode, all the previous seeds of swarm could contribute bandwidth and resistance to new swarms, there were nice proposals at libtorrent project (library which many clients we know use), as f.e. not announcing that a peer has files to not overwhelm network, but announcing that he wants them.
-
Anyone have any experience with writing their own torrent client?
How much of it do you want to do yourself vs how much do you want to use pre-made libraries for? Many popular clients rely on libtorrent which is a C++ torrent library: https://github.com/arvidn/libtorrent
- qBittorrent on Btrfs
-
Quick Sync and playing HDR on my new Win10 Plex build?
FWIW, it seems like there'll be an update to libtorrent very soon that'll address the memory issue.
-
qBittorrent 4.4.5 memory leak on LinuxServer.io Docker container?
Here is a link to an issue I found on the libtorrent repo discussing the issue.
-
Transmission 4.0.0 beta 1 is out
Many!
https://webtorrent.io/faq
Notable ones include Libtorrent[1], Peertube[2], and their own Webtorrent Desktop[3].
1. https://github.com/arvidn/libtorrent/issues/223
2. https://peertube-viewer.com/posts/2021-02-20-peertube-viewer...
3. https://webtorrent.io/desktop/
webtorrent-desktop
-
Ask HN: What could make torrenting more popular again?
- https://webtorrent.io/desktop
Do you have any ideas on what could popularize the technology again?
-
Transfer 1TB+ files using only the browser, completely free without ads. Also completely anonymous and encrypted. WebRTC is cool.
Made me think of https://webtorrent.io/desktop/
- Piracy Website where i can pay for quality streaming?
- Opinião: Qual e o melhor serviço de streamings pra vocês atualmente?
- most lightweight torrent client?
-
WebTorrent
Disclosure: I'm the author of WebTorrent.
It's so fulfilling to see WebTorrent still popping up on Hacker News after all these years. I started the project in 2013 and devoted most of my 20s to working on it, ultimately becoming a full-time open source maintainer, and writing hundreds of npm packages including buffer (https://github.com/feross/buffer), simple-peer (https://github.com/feross/simple-peer), and StandardJS (https://standardjs.com/).
I started WebTorrent with the goal of extending the BitTorrent protocol to become more web-friendly, allowing any browser to become a peer in the torrent network. Within less than a year of starting the project, I got WebTorrent fully working. And it worked _well_, beating many native torrent apps in terms of raw download speed and the ability to stream videos within seconds of adding a torrent.
WebTorrent never got as much attention as the cryptocurrency projects selling tokens throughout the mid-2010s, even though WebTorrent actually worked and had more real users than almost all of them :) I was never tempted to add a crypto-token to WebTorrent, despite many well-meaning friends telling me to do it. Nonetheless, WebTorrent served as an accessible on-ramp to the world of decentralized tech, along with other projects like Dat (https://dat-ecosystem.org/) and Secure Scuttlebutt (https://scuttlebutt.nz/).
But WebTorrent is more than a protocol extension to BitTorrent. We built a popular desktop torrent client, WebTorrent Desktop (https://webtorrent.io/desktop/), which supports powerful features like instant video streaming.
We also build a `webtorrent` JavaScript package (see https://socket.dev/npm/package/webtorrent) which implements the full BitTorrent/WebTorrent protocol in JavaScript. This implementation uses TCP, UDP, and/or WebRTC for peer-to-peer transport in any environment – whether Node.js (TCP/UDP), Electron (TCP/UDP/WebRTC), or the web browser (WebRTC). In the browser, the `webtorrent` package uses WebRTC which doesn’t require a browser plugin, extension, or any kind of installation to work.
If you’re building a website and want to fetch files from a torrent, you can use `webtorrent` to do that directly client-side, in a decentralized manner. The WebTorrent Workshop (https://webtorrent.github.io/workshop/) is helpful for getting started and teaches you how to download and stream a torrent into an HTML page in just 10 lines of code.
Now that WebTorrent is fully supported in nearly all the most popular torrent clients, including uTorrent, dare I say that we succeeded? It's been a long and winding journey, but I'm glad to have played a role in making this happen. Special shoutouts to all the open source contributors over the years, especially Diego R Baquero, Alex Morais,
P.S. If you're curious what I'm up to now, I'm building Socket (https://socket.dev). And there's actually a WebTorrent connection, too. Socket came out of a prior product we built called Wormhole (https://wormhole.app), an end-to-end encrypted file transfer application built using WebTorrent under-the-hood (Show HN thread: https://news.ycombinator.com/item?id=26666142). Like Firefox Send before it, security was a primary goal of Wormhole (see security details here: https://wormhole.app/security). But one area where we were lacking was in how we audited our open source dependencies. Like most teams building a JavaScript app, we had a large node_modules folder filled with lots of constantly updating third-party code. The risk of a software supply chain attack was huge, especially with 30% of our visitors coming from China. As most teams do, we enforced code review for all our first-party code. But similar to most teams, we were pulling in third-party dependencies and dependency updates without even glancing at the code (this is something that almost every company does today). We knew we needed to do better for our users. We looked around for a solution to analyze the risk of open source packages but none existed. So we decided to build Socket.
Socket helps developers ship faster and spend less time on security busywork by helping them safely find, audit, and manage OSS. Socket provides a comprehensive open source risk analysis. By analyzing the full picture – from maintainers and how they behave, to open-source codebases and how they evolve – we enable developers and security teams to identify risk from malware, hidden code, typo-squatting, misleading packages, permission creep, unmaintained or abandoned packages, and poor security practices. For one quick example, take a look at the risks we identified in this Angular.js calendar library: https://socket.dev/npm/package/angular-calendar/issues/0.30....
- What would make you start using torrent sites again?
-
Transmission 4.0.0 beta 1 is out
Many!
https://webtorrent.io/faq
Notable ones include Libtorrent[1], Peertube[2], and their own Webtorrent Desktop[3].
1. https://github.com/arvidn/libtorrent/issues/223
2. https://peertube-viewer.com/posts/2021-02-20-peertube-viewer...
3. https://webtorrent.io/desktop/
-
Digital Commons
WebTorrent
-
Choose your companion wisely.
just use https://webtorrent.io/desktop/ and stream the 1080p torrent directly.
What are some alternatives?
qBittorrent - qBittorrent BitTorrent client
webtorrent - ⚡️ Streaming torrent client for the web
BiglyBT - Feature-filled Bittorrent client based on the Azureus open source project
udemy-downloader-gui - A desktop application for downloading Udemy Courses
libutp - uTorrent Transport Protocol library
iohook - Node.js global keyboard and mouse listener.
jech/dht - BitTorrent DHT library
webrtc-video-conference - WebRTC video conference app
qbittorrent-nox-static - A bash script which builds a fully static qbittorent-nox binary with current dependencies to use on any Linux OS
ufonet - UFONet - Denial of Service Toolkit
checkn1x - Light (~50MB) images for jailbreaking iOS devices
electricShine - Create Standalone Installable Shiny Apps