top of page
Search
bodenkova1995

BiglyBT is Probably The Best Torrent Client Ever: Testimonials and Feedback



Probably you are now looking for a uTorrent replacement for mac. A torrent client that does not install crapware or bloatware on your Mac without your consent? A lightweight, fast, and reliable torrent client, as the older uTorrent 2.2.1 was?


In this post, we will go through the top five uTorrent alternatives for mac. These torrent clients do not install bloatware, are fast, free, lightweight, and come with fantastic and unique features




BiglyBT is Probably The Best Torrent Client Ever




Transmission is not only a good uTorrent alternative for mac, but it is actually one of the best torrent clients for Mac computers. The latest version (Transmission 3.0.0) is a fast and free BitTorrent client, using fewer resources than uTorrent (and other clients). The initial release of Transmission was in Sep 2005, and the last stable release was in May 2020.


Transmission also allows remote torrent management with two remotely-controlled clients, Web, and Terminal. In addition, the Transmission Deamon is perfect for deployment on servers, embedded computers, or using it as headless.


qBittorrent is another excellent alternative to uTorrent for mac. It is also a free BitTorrent client as uTorrent is, but a difference is that qBittorrent is fully open-source and based on the Qt 5 toolkit and the libtorrent-rasterbar library. qBittorrent is designed to be the open-source alternative to uTorrent (and other popular proprietary torrent clients). uTorrent users swap to qBittorrent, not only because it is open-source but also because it is highly reliable. In addition, learning how to tweak qBittorrent settings can turn it into one of the safest and fastest BitTorrent clients out there.


Folx by Eltima is another fantastic uTorrent replacement for Mac. This app is both a download manager and torrent client specially designed for Mac. The torrent client is free and fully compatible with the latest macOS versions, including macOS High Sierra, macOS Mojave, and macOS Catalina.


Deluge is another fantastic alternative to uTorrent for Mac. It is a free, open-source, and cross-platform (Linux, Windows, macOS, BSD, and Unix. ) BitTorrent client. One of the biggest highlights of Deluge is that it is the best torrent client for customization. The torrent client can be configured to a new level with different implementations using official and third-party plugins.


BiglyBT is written in Java, and it is based on the original code from Vuze (former Azureus). Aside from allowing users to download torrents, BiglyBT also enables them to convert the downloaded media to different formats. In addition, BiglyBT also allows users to stream the media to streaming TV box sets or game consoles. The torrent client is compatible with Mac OS X 10.11.0 or later.


In our post about the five uTorrent replacements for mac, we went through the torrent clients currently loved by the community for many reasons. Our top two choices for uTorrent alternatives for Mac are Transmission and qBittorrent. But there are also other fantastic alternatives to uTorrent, for instance, Folx, Deluge, and BiglyBT.


Probably you are now looking for a uTorrent replacement for mac. A torrent client that does not install crapware or bloatware on your Mac without your consent? A lightweight, fast, and reliable torrent client, as the older uTorrent 2.2.1 was? uTorrent has been the preferred BitTorrent client for many years. However, more and more people


BitTorrent and uTorrent are both proprietary (closed-source software) BitTorrent clients supported by ads (adware). Both belong to the same company, Rainberry, Inc. (former BitTorrent, Inc.), responsible for the continuous development of the one and only BitTorrent P2P protocol and the two torrent clients, uTorrent and BitTorrent, along with many other products. The difference between BitTorrent


A seedbox lets you keep your whole media gallery on a high-speed server, download new releases as soon as a torrent is released, and share everything safely with others. Still, if you want to watch them, you have to download the files from a seedbox and have a media player on your computer. That is,


The first attack is on people who configure their Bittorrent application to proxy their tracker traffic through Tor. These people are hoping to keep their IP address secret from somebody looking over the list of peers at the tracker. The problem is that several popular Bittorrent clients (the authors call out uTorrent in particular, and I think Vuze does it too) just ignore their socks proxy setting in this case. Choosing to ignore the proxy setting is understandable, since modern tracker designs use the UDP protocol for communication, and socks proxies such as Tor only support the TCP protocol -- so the developers of these applications had a choice between "make it work even when the user sets a proxy that can't be used" and "make it mysteriously fail and frustrate the user". The result is that the Bittorrent applications made a different security decision than some of their users expected, and now it's biting the users.


The attack is actually worse than that: apparently in some cases uTorrent, BitSpirit, and libTorrent simply write your IP address directly into the information they send to the tracker and/or to other peers. Tor is doing its job: Tor is _anonymously_ sending your IP address to the tracker or peer. Nobody knows where you're sending your IP address from. But that probably isn't what you wanted your Bittorrent client to send.


That was the first attack. The second attack builds on the first one to go after Bittorrent users that proxy the rest of their Bittorrent traffic over Tor also: it aims to let an attacking peer (as opposed to tracker) identify you. It turns out that the Bittorrent protocol, at least as implemented by these popular Bittorrent applications, picks a random port to listen on, and it tells that random port to the tracker as well as to each peer it interacts with. Because of the first attack above, the tracker learns both your real IP address and also the random port your client chose. So if your uTorrent client picks 50344 as its port, and then anonymously (via Tor) talks to some other peer, that other peer can go to the tracker, look for everybody who published to the tracker listing port 50344 (with high probability there's only one), and voila, the other peer learns your real IP address. As a bonus, if the Bittorrent peer communications aren't encrypted, the Tor exit relay you pick can also watch the traffic and do the attack.


So what's the fix? There are two answers here. The first answer is "don't run Bittorrent over Tor". We've been saying for years not to run Bittorrent over Tor, because the Tor network can't handle the load; perhaps these attacks will convince more people to listen. The second answer is that if you want your Bittorrent client to actually provide privacy when using a proxy, you need to get the application and protocol developers to fix their applications and protocols. Tor can't keep you safe if your applications leak your identity.


Another answer is to separate streams by destination port. Then all the streams that go to port 80 are on one circuit, and a stream for a different destination port goes on another circuit. We've had that idea lurking in the background for a long time now, but it's actually because of Bittorrent that we haven't implemented it: if a BT client asks us to make 50 streams to 50 different destination ports, I don't want the Tor client to try to make 50 different circuits. That puts too much load on the network. I guess we could special-case it by separating "80" and "not 80", but I'm not sure how effective that would be in practice, first since many other ports (IM, SSH, etc) would want to be special-cased, and second since firewalls are pressuring more and more of the Internet to go over port 80 these days.


We should keep brainstorming about ways to protect users even when their applications are handing over their sensitive information. But in the mean time, I think it's great that these researchers are publishing their results and letting everybody else evaluate the attacks. (If you're a researcher working on Tor attacks or defenses, check out our new research resources page.) The attacks in this paper are serious attacks if you're a Bittorrent user and you're hoping to have some privacy.


Agreed. I use torrents on a regular basis, downloading everything save movies and music available in the United States with it. Never gotten caught, never used protection until very recently (protection being in the form of Peerblock).


"The attack is actually worse than that: apparently in some cases uTorrent, BitSpirit, and libTorrent simply write your IP address directly into the information they send to the tracker and/or to other peers. Tor is doing its job: Tor is _anonymously_ sending your IP address to the tracker or peer. Nobody knows where you're sending your IP address from. But that probably isn't what you wanted your Bittorrent client to send."


Safe from what?The encryption on bittorent is good if your ISP is throttling bittorrent traffic. (It hides your use of bittorrent from them) Your ip address is still shared with the tracker and other users.PeerGuardian blocks known lowlife ip addresses from connecting to you. (RIAA MPAA, etc.) But it will _never_ get them all. (not possible)


Well, i ain't very sure about the headline!!! I think that it could be cool to have a new bit-torrent application made to work with TOR!!! You could even call it "TORrent"!!! It's very easy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!I think that something of missing in Tor is a robust publishing system to share documents, in a way to resist to the shut-down of a single server!!!! i think it to be the main flaw of WikiLeaks too!!! but also of Wikipedia, and every normal website: in the inner idea of a very well working Internet, there is the concept of decentralization!!!!!! but that concept has been almost forgotten!!!!A super cool P2P system is another thing missing in TOR!!!!!!!At this time, i don't think a P2P system internal to TOR to be very useful, but in the future it'll be very necessary!!!!!! So, you'd better to think about making one!!!!!!!!!!!!!!!!!!I think that the bittorrent client for TOR should work only within the TOR network!!! You can have some "hidden services" (those addresses ending with ".onion") to work as HTTP-trackers!!!! So that all TORrent clients will have only tracker addresses to contact within the TOR network!!! All TORrent clients should be enabled as internal tor nodes, for the whole TOR network (to share the global network load too!!!) and every client should start one "hidden service" to accept incoming connections!!! Yeah, i think this could actually work!!!!! So, you can send your .onion address to the Tracker, and at the same time download the list of others peers sharing your same file!!!! You can then connect to the .onion hidden service of the others peers, and the others will do the same after having read your .onion address from the tracker!!!!!!I'm sure, in this way, you'll have everything: a safe & secure bittorrent and a lot of bandwidth (because the lack of ExitNodes won't be important) to be used also for others purposes (so, when you are downloading/uploading something, but there is some free bandwidth, your node can be used also for the normal usage of TOR)!!!!!!!!!!!!!!!!!You can have the torrent client to automatically set the upload and download speed limit to 1/4 of the bandwidth set to be used for the same upload and download channel of your node!!!!!! it's because i think that when you are using .onion addresses your connection pass through four nodes (or three?!!! i saw once they were four nodes!!!!!!!!!!!). In this way, you can avoid to have a congestion in the network!!! Because if you share a file at 1MB/sec... it'll take 1MB*4nodes=4MB/sec of bandwidth to handle the bits stream!!!!!! So you need to go 1/4 slower to don't break the balance!!!!!!I've got this idea, after reading this blog entry and another one on torrentfreak i read yesterday!!!!You should read this article too!!! It's on TF, and it's entitled Child Pornography Is Great, Anti-Pirates Say ( ). the whole article can be summarized in these two quotes:Johan Schlüter of the Danish Anti-Piracy Group enthusiastically said:Child pornography is great. It is great because politicians understand child pornography. By playing that card, we can get them to act, and start blocking sites. And once they have done that, we can get them to start blocking file sharing sites.and Christian Engstrom (Pirate Party) heroically answered:The big film and record companies want censorship of the net, and they are perfectly willing to cynically use child porn as an excuse to get it.Well, in don't want to enter in the discussion of child porn!!! (it's normal if pro-copyright organizations enjoy it!!!! they're usual to do the wrong things!!!!!!!!) But i want to very enter into the discussion of FILE SHARING and COPYRIGHT!!!!!! It isn't a fault of american people; but america's extremist capitalism and imperialism are evil, and they must be fought!!! this is what pirate parties are actually doing!!!! and the intellectual property is only one excuse to add filters, censorship systems, to the Internet!!! to allow politicians (read puppets bribed by lobbyists), to control the flow of information, and thus your life!!!!!!!! This is why i think that Tor, as it's a system made to be used against censorship and for political reasons, is perfect to be extended to be ready to be used as an alternative to the current centralized bit-torrent!!!!!!!!!!!!!!!!!!!!! I'm sure that the RIAA and the MPAA, won't be happy nor agree with me; but it's a their fault, they didn't bribed me yet!!!!!!!!!!!!! hahah!!!!!!!!!!!!!!!!!!!!!bee!!!!!!!!!!!!!!! 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comments


bottom of page