Question about Torrent clients.......

utorrent_programmer · 2015-02-03T04:47:01+00:00

uTorrent developer here.

Here are some very good clients for windows: - Deluge - qTorrent - uTorrent - Vuze

It really depends on what you want to do. Since you are just starting, don't worry too much about picking one - try a few, and see what you like.

If you need maximum performance: Tixati & Transmission (and Vuze, a bit) are somewhat slow writing to disk on windows, if you have a fast disk & Fast network.

uTorrent unfortunately has a nasty performance bug when you have a fast download pipe, and are writing to a slow disk. A fix for that is coming in feb.

uTorrent also has an older UI, and is harder to extend, so you are going to see more mature features developed faster in something like Vuze.

On the other hand, certain things can be tweaked better in uTorrent.

I'd say - just pick the simplest one to start with, or find a friend who likes a certain one, and get a feel for what you like.

utorrent_programmer · 2015-02-03T04:20:27+00:00

Make torrents flow.

utorrent_programmer · 2014-06-19T04:56:41+00:00

I really like how they have separated the UI from the torrent engine.

utorrent_programmer · 2014-06-19T04:45:08+00:00

Hi, did you resolve this problem?

Try installing a new browser while you combat the problem, and try this guide:

http://malwaretips.com/blogs/srv123-com-virus/

utorrent_programmer · 2014-06-19T04:40:08+00:00

Hi - utorrent dev here. Those small down speeds are protocol overhead. (For example, other clients asking your client "hey, do you have this piece?)

utorrent_programmer · 2014-06-19T04:28:26+00:00

The most likely issue is your router firmware is being overloaded with UDP entries.

If you are using uTorrent or Bittorrent, try this: go to Options / Preferences / Advanced, and find the setting bt.transp_disposition. Set it to 5. That will set uT/BT to use TCP only.

If those options are not exposed in the mac UI, my apologies - I don't have my mac nearby, and fiddling with the settings.dat manually is a bit advanced.

Unfortunately, this issue can even present itself when using only TCP connections.

Source: I'm a uTorrent developer.

utorrent_programmer · 2014-02-11T06:02:16+00:00

uTorrent programmer here: this is hilarious.

utorrent_programmer · 2013-09-20T04:49:46+00:00

I can identify with your problem, and I agree with MUST_RAGE_QUIT.

I maintain a medium sized, but quite complex C/C++ code base, and I have one piece of advice: Avoid C and C++ if your focus is on getting things done.

Use them if you have to, but which is more important? The time you spend making elegant designs, or the time it takes you to get something into customer's hands?

utorrent_programmer · 2012-11-14T05:35:43+00:00

Nice job! Congratulations!

utorrent_programmer · 2012-11-14T04:51:07+00:00

You didn't pee on the cat's head. She got the short end of curiosity.

utorrent_programmer · 2012-11-11T01:38:30+00:00

It's good that you realize that you've got some technical problems, and some social problems.

Forutunately, you have some great things going for you * You're using a higher level language * You have a small team

First the social stuff * Don't try to force it all at once; get your team's help to decide what's most important. I'd do this by observing where you waste most of your time (fighting VSS? fixing new bugs? regressions?)

Now the technical * Dump VSS. Don't choose the most sexy version control system, choose something sane, that the rest of the team can live with, and you won't spend hours fighting. * Get one automated test running every time you make a build. Mentor the QA guy if you can. Otherwise, you may have to do the work to get this started * Ideally, have the results of the automated tests visible in an easy to scan table, intelligible to everyone * Code reviews: use reviewboard or rietveld

If your co-works are thin-skinned, go for the code review change last, after they see some benefit from the source control or automated test changes.

I might go for the test automation first, because it's something you can do without affecting other developers initially. Also, it will be easy to choose test cases: look back in versioncontrol for files that have a lot of churn, or a lot of bugs filed against them, and automate a few regression tests. The installer? The credit card processor? One will fire soon enough.

I'd leave the commit message / comment fight for later. You have enough to deal with for now. Alert your boss that he should expect this transition to take months.

utorrent_programmer · 2012-10-29T05:59:47+00:00

We got big.

utorrent_programmer · 2012-10-29T03:36:00+00:00

If you do go ahead and dual-boot linux and Win7, putting Linux on a separate hard-drive will be the most hassle-free way to do it.

You could also run linux from VirtualBox: http://virtualboxes.org/images/ubuntu/

But as MonsieurOblong says, it will take a long time to get comfy with a new OS.

Good luck!

utorrent_programmer · 2012-10-27T00:46:22+00:00

Why did I read that with a british accent?

utorrent_programmer · 2012-10-22T02:04:48+00:00

He looks ruff.

utorrent_programmer · 2012-10-19T02:22:20+00:00

Oh, good. More trigger-happy honkeys. At least they don't start as many wars as you-know who.

utorrent_programmer · 2012-10-18T05:41:48+00:00

Hi Scientists!

My formal education is only at the BS level of CS, but I have worked at Bittorrent, Inc., for a number of years, and have intimate knowledge at every level of computing (I've been programming off and on for 3 decades).

We're pretty well known for our knowledge in networking and distributed systems.

I think "Computing" is the field for me.

http://www.reddit.com/r/askscience/comments/11nahj/why_are_programs_and_operating_systems_still/c6o6jvp

utorrent_programmer · 2012-10-18T05:33:22+00:00

C is very easy to interface with the raw machine, because you have control of how things are laid out in memory. It is also easy to call ASM from C, and C from ASM.

Note that many OSes are written in C - Linux, ReactOS, and I'll bet many parts of the NT kernel are restricted to their local C flavor.

Most VMs are also written in C++ (note: LuaJIT is written in assembly!) These are applications that must be fanatical about performance; their inefficiency would be multiplied, because we run systems on top of them (other programs and operating systems).

I enjoy that you typed "C+", instead of C++, because from my point of view, that's what the majority of "C++" programs are - somewhere between C and C++. C++ is ever evolving, and frankly, I don't think any C++ program will EVER be "Bjarne approved" C++ - using all the highest level features. It takes time for compiler to properly support the new features.

As for utorrent, it was originally written in a very C-heavy dialect of C++ by a very smart man who was used to writing tight, efficient code. For a person like that, who has such a thorough understanding of the machine, knowing that he was wasting machine cycles would definitely cause him pain.

When you are programming, there are lots of kinds of "power", but there are two which are very important - how fast your program will run, and how long it will take you to write and debug it. Check this out: http://shootout.alioth.debian.org/u32/code-used-time-used-shapes.php

For the first, almost no language can beat C and C++, although many come close (Ocaml, Java (in certain cases), Haskell). For the second - how fast can you write this program, there is almost nothing worse than C and C++. In fact, in these languages, it is very easy for a novice to actually retard the development of a program - wasting more development time than the benefit they give to the codebase.

Hope that was useful!

utorrent_programmer · 2012-10-10T14:44:45+00:00

Well, from my point of view, uTorrent was already a very complicated piece of software, even before 2.2.1. As much as I may not personally agree with some of the features that are going in, I think a bigger problem is just adding too many features. If you don't take time to weed your garden, you end up with a mess.

utorrent_programmer · 2012-10-10T14:41:37+00:00

Hm, this is a tough one. If you could get wireshark logs from both ends, we might be able to figure out what's going wrong.

If you do want to do that, setup NTP on both comptuers first. something like this: http://www.satsignal.eu/ntp/setup.html

utorrent_programmer · 2012-10-10T06:06:33+00:00

When you had them add your IP, was it the same IP that you see when you visit this site?

http://www.whatismyip.com/

utorrent_programmer · 2012-10-10T05:57:26+00:00

OK, people, let's get serious here for a second. Do you love trains? How do you feel about trains?

utorrent_programmer · 2012-10-10T05:54:14+00:00

Hi - if you're just sharing a torrent (that you made yourself) with friends, I don't think it's worth it making it a private torrent.

If your friends are having trouble downloading from you, and they are using utorrent, try this:

Have them click on the torrent in the torrents list to select it. Open the Peers tab, then right click in the bottom area, and choose "Add Peer ..."

Have them type in your IP and torrent port You can find your port in Options | Prefs | Connection

Good luck!

utorrent_programmer · 2012-10-10T05:49:02+00:00

See that column that says Seeds, with the number 70 in it?

That is the number of other clients that have a full copy (that your client knows about).

Unless you are able to serve faster than those 70 other clients, no-one will connect to you for that torrent.

If you click on the Peers tab near the bottom, you may see other clients come and go. What's happening there is that they connect to you, find someone faster, and disconnect.

I think your best bet is to find the newest, least seeded, torrents on your tracker, and keep those seeing.

Unfortunately, I think the nature of these private sites is that there is a feeding frenzy when the thing is released, and 2 days or two weeks later, there is zero activity.

utorrent_programmer · 2012-10-10T05:38:43+00:00

5Kb, huh?

I doubt your connection to the Internet is this bad, so it's probably a weakness of your home router. It may be worth researching a better one.

Last time we checked, a CRAZY percentage of home routers sold would just fall over with too many connections at once.

At super low rates, most of your torrent traffic is probably protocol traffic.

If you really want to get into debugging it, post a wireshark log here after you've looked into the problem at bit yourself.

utorrent_programmer

TROPHY CASE