Ultima

You would have to edit resume.dat (pay attention to the warnings in the first post). I guess you can modify the have key in the respective torrent listed in resume.dat (binary key, viewed as binary) and set it to 0xFF... (where each, and only each, character after the`0x' needs to be changed to an `F'). So if the have value for the torrent is 0xDEADBEEF, it should be changed to 0xFFFFFFFF.

The screenshot should be self-explanatory, but whatever. Those tabs at the top don't highlight properly when the forum is selected, so it's slightly inconsistent (no biggie). Edit: So it seems fixed now

Elaborate.

Yeah, Trac is down due to server maintenance. You'll notice a new site design is moving into this site, and all kinds of things are in flux on the web server at the moment. 1. Never seen that happen. 2. Anything related to download locations are unimplemented in the WebUI backend. For one thing, security and privacy concerns need to be mitigated before they can be implemented.

Random observations: - Forum posts need separators between the post body and the post signature. - More than just spacing between sentences, whitespace in general feels overused all over the place. Way too much padding for HTML elements in each forum post, for example. - The toolbar at the top of every page feels disconnected from the rest of the page. Like, there's a rounded toolbar on top, and then there's a rounded page title thingamajig. (see this if you're not sure what I'm referring to -- green thing being toolbar, blue thing being title thingamajig). It feels like the "toolbar" can be better integrated with the rest of the page, especially considering the fact that it's exactly as wide as the page contents. - The id="brdwelcome" div (which contains the extremely useful "Show new posts since last visit" link, among other things) is hidden behind the id="announce" div. - There is no differentiation between threads with new posts and threads without. That is, forum thread links used to be bolded for threads with new posts, and regular (unbolded) for threads without. Now, all thread links are bolded, which makes it a huge pain to browse. - The skins page needs the ability to sort by date (newest first, or whatever) (forgot that we already mentioned it above xD) - See the FAQ's General section. See the 9th link in the table of contents ("Is it possible to make µTorrent load a torrent from the commandline?")? It links to a different question ("How can I make µTorrent auto-load torrents from a specified folder?")

µTorrent crash dumps should only be partial dumps of the µTorrent process's memory only.

Honestly, almost any as[0-9]+.net resolved IP is a UK IP.

The dumps look busted. What OS are you using?

Internationalization is... somewhere on my radar, but very far off from the top of my list of priorities.

Indeed, I guess it must've been from androidandme Work on MiniUI has stagnated because of a lack of contiguous free time to work on it. Will get back to it whenever I can.

Port forwarded and all? Firewall rule recreated?

Hah, I recommended the same to Firon earlier today

Well um... there's a page selector at the bottom of the torrent jobs list. And it's configurable in the WebUI preferences.

You can ignore it. If you'd prefer not to see the error, then disable the "Add Windows Firewall exception" option in Preferences > Connection.

When you open a .torrent file in BEncode Editor, a key called info is in plain view. That is the said dictionary, whose hash is the torrent's (aptly named) infohash. As DWK mentioned, you'll find the announce/announce-list keys to be outside (and above) the info dictionary.

Preferences > Queueing > Limit the upload rate to (kB/s): [0: stop]

A port got backburnered because of a lack of motivation, time, and some other mundane details that I need to work out on the current versions (commandline editing especially) before I can proceed. I still haven't completely given up on it (though that isn't a guarantee that it'll be completed). Thanks for the complement and interest though

The WebUI API hasn't changed in the least as of late because WebUI isn't currently the focus of development. I'll try to find a time to bug the devs about WebUI, but it won't be any time soon -- at least not until uTP development stabilizes. And ticket #2 likely won't be going anywhere without more discussion and fleshing out of details regarding possible solutions/workarounds to the security implications associated with custom paths from remote locations.

Magnet URIs aren't currently supported in the WebUI API. Will add to the bug tracker though.

That'd probably be Blackberry or service carrier issue. I'm not too familiar with the problem, but if you can't figure it out, then perhaps you can try another browser, like Opera Mini (which runs fine on Blackberry anyway). To be sure, you can access your WebUI from other computers outside of your network, right? Port forwarded and all?

@w32sobig: uTP wasn't designed to evade throttling, and isn't purported to do so. That it's not doing as you expect is because you're expecting it to do other than it was meant to. Your situation is outside this topic's scope, so if you want, discuss your ISP throttling issue in another thread.

Yes, you always have to if you want external access.

Indeed. I've already gotten v0.6.1 Unicode off of Avira and AVG's definitions, but I'm not sure about any other version. The reason for the false positive is that the antivirus softwares don't like UPX and/or AutoIt. I honestly can't do anything about the vendors' prejudice against them, and I don't have the time or energy to kill trying to get them to stop forgetting that a programming language and an executable packer don't imply malware. So here's the lowdown: if your antivirus is complaining about a virus, send the executable into the antivirus vendor for analysis as a false positive.

Oh, it can definitely be quite dramatic. I've seen plenty of cases where speeds are slow (sub-10KiB/s), only to jump to 100+ KiB/s immediately after a simple port forwarding. @chupakabra: Broken link.

@erstwhile: You can merge in the 0.7.0 WIP.