Ultima

Restricting IP addresses in any way? ipfilter.dat, or the option in Preferences > Web UI?

And exactly what URL are you attempting to access the WebUI via? Are you using an alternative listening port?

Odd that a 2.8GHz computer would be slower than two ~1.6GHz computers, but interesting nevertheless. I'm not sure why this ".41" version would be faster than builds that come after it :\

@jewelisheaven: It would require a change to the backend. Paging doesn't so much lower bandwidth as it does lower memory and CPU usage to generate all the list items. the same amount of bandwidth is used regardless of the number of items shown in the list.

It's not implemented, though it's been requested before.

@Domokun: So you want to see a changelog entry for every build that simply says "- Change: more toolbar tweaks"? I would have thought my previous reply to you made it clear what the changes are... And it continues to mistify me as to why people are updating to unadvertised builds, and yet, complaining about the lack of a changelog. If you want to update to a build that doesn't have a changelog attached, it's your prerogative -- we're not telling anyone to update to the newer build because there's no reason for anyone to do so. @DaVrOS: Very valid complaint regarding client ID whitelisting/blacklisting... Not sure how to respond to that. Regarding stable and build numbers, I've seen programs on both sides of the gamut. Winamp, for example, is v5.55, and yet, Nullsoft has been pumping out new builds of the same version very often as well (2435 in the last few days, followed by 2460 just today, no changelogs or announcements attached). That's not to justify the build increments, but it's just how the cards have fallen due to the way the installer is included with the actual µTorrent executable.

If I had to guess, I'd say that the tracker probably associates your passkey with a certain IP, and if you access the account via different IPs (iPhone, and the computer running µTorrent), it gets confused.

Fair enough.

That's exactly the point: they don't cause an auto-update. As I said, the changes don't affect existing 1.8.2 users, and that's (again) exactly the same thing that happened with 1.8.1: there was no autoupdate from 12616 to 12639. (And it would've been simple enough to verify by this using Help > Check For Updates)

Unless otherwise noted, the changes are installer related tweaks, and are unnecessary for normal users. Honestly, I'm not even sure why people are hitting the executable daily to find a build number change.

Another problem: the skins page is serving files listed under the "Program Icons" tab as BMP files when in fact they are ICO files. Edit: http://forum.utorrent.com/viewtopic.php?id=56909 The Google CSE at the top of the website is broken, which causes problems in the µTorrent search toolbar as well when gui.bypass_search_redirect is set to false and using the default Google search engine. Fixed. Unfixed.

Invalid passkey...? For the tracker announce? If so, then that's not really a MiniUI issue, and is more a tracker issue you'll have to ask the tracker staff about.

Indeed, it's been working fine under vanilla Wine for well over a year now.

There's a page changer at the bottom of the torrent list view. The reason only 50 are shown at a time is because generating list items for too many torrents in one shot can be slow and time consuming. You can modify the limit in Preferences > Web UI > Max. rows per page.

I'll take a look at the bug. Thanks for the report!

Right, but what fatspirit is reporting is that autoupdate is serving build 14984. The problem now is that the message sent with it is outdated, and for build 14908.

You already mentioned the same thing yesterday, and the reason as explained in osmosis's reply still hasn't changed. Edit (2009-04-05) @ below: Okay, gotcha.

If you don't care to use WebUI on a desktop computer, then you can... 1. Download the ZIP file linked in the first post 2. Extract it into some directory (like 'webui' or something) 3. Extract the GZ files' contents into the same directory and remove the GZ files 4. ZIP all of the files in that directory (files inside 'webui', without the actual 'webui' directory) 5. Name the newly-created ZIP file as webui.zip 6. Place this webui.zip in Start > Run > %appdata%\uTorrent Assuming you set WebUI up in Preferences > Web UI, you can then visit http://[iP]:[port]/gui/ using your mobile device, where [iP] is your computer's IP address (the computer running µTorrent), and [port] is the port µTorrent is listening on for incoming connections.

... MiniUI isn't to be installed on the device. It's to be installed as the regular WebUI is to be installed -- on the actual computer running µTorrent. Have you read the instructions in the first post?

I think .postsignature needs to be made slightly distinct from the forum post body (maybe a different background color?). Too many people confuse signatures with post bodies, and respond to the signature instead of the body (case in point).

http://forum.utorrent.com/viewtopic.php?pid=392885#p392885

Yes, it's been reported before. If you need to further discuss it, then discuss it in that thread.

Indeed, such a flag would pretty much be an image as I mentioned. An alternative to using an image would be to use a different color for threads with new posts. Edit: Another curiosity... Along the same lines as what boo mentioned about the footer, why is a site map even needed at the bottom of every page, period? Wouldn't a Site Map page be sufficient? I'm pretty certain users won't be scrolling all the way to the bottom of the page to get to quick links (at that point, it wouldn't be considered "quick" anymore). IMO, all it serves to do is add clutter to every page.

Have you tried reloading the page? I haven't yet implemented page updating, so a torrent removal isn't immediately evident until you reload the page (Reload button, or refresh the page).

Other observations/suggestions: GENERAL: - Is this circled header really necessary? I can easily see the entire site design being perfectly usable and coherent without it (and the whitespace above it). It's essentially duplicating information already shown by the website header's tabs (mostly anyway, assuming this gets fixed), and is causing the odd disconnect that I mentioned here. The only problem with removing it would be that the forum header's "Index | User list | Rules | Search | Profile | Logout" links would go with it, but they can always be merged with the #brdwelcome div. - [2009-03-21 @ 10:26] Along the same lines as what boo mentioned about the footer, why is a site map even needed at the bottom of every page, period? Wouldn't a Site Map page be sufficient? I'm pretty certain users won't be scrolling all the way to the bottom of the page to get to quick links (at that point, it wouldn't be considered "quick" anymore). IMO, all it serves to do is add clutter to every page. FORUM: - The "Homepage" and "IRC" links can now be removed from the forum header, since they're already accessible from the website header. - The lack of spacing (or other division of some sort) seen here surprised/confused me for a second. Perhaps some padding/margins need to be added? - I don't know if it was intentional, but a bit more than the left half of the gray post header is an anchor. I'm not really sure why it needs to be half. Having only the timestamp clickable (or alternatively, the entire header clickable) would make more sense. - Can the "Report | Edit" links (in the ".postfootright" divs) be moved over to the right side again? It feels awkward with it on the left-hand side (or, er, middle of the page). Messes with my muscle memory ;D - Why are form buttons so ginormous? D: - The post preview page is really messed up (just try it yourself to see ). - The redirection page after a post is submitted/edited is somewhat... plain. It's mostly unimportant, but I guess the point is that it's just inconsistent with the rest of the forum. - The unbolding of threads without new posts is definitely an improvement, but I guess the distinction still isn't quite that clear unless you look carefully. Under the other forum skins, there are images to the left of each thread indicating the read status of the thread, where threads with new posts are colored differently from threads without. Perhaps a page should be taken out of those skins and status images should be reintroduced for threads? I guess I overestimated the utility of the bolding, and underestimated the utility of the thread status images. DOCUMENTATION: - The text on the Documentation page is somewhat... large. It looks inconsistent with the rest of the site, and almost out of place. - There should be a short (one or two line) blurb at the top of each sub-page linked from the Documentation page (much like where "Check out guides, get ..." is on the main Documentation page). NOTE that the "µTorrent Connection Setup Guide" page already has such a blurb, but it isn't styled in the same way as on the main Documentation page. - While the site is still actively being redesigned, I'm thinking... maybe the on-site guides should be styled more consistently with the "µTorrent Connection Setup Guide" page's style (images next to and a divider between each section, etc.)? SKINS: - The skins page's "Show" combobox redirects to "toolbar?order=[ORDER]&limit=[LIMIT]". Yes, you're seeing that correctly, it's redirecting to a URL with the & HTML entity, which is causing it to fail. When you remove the extra amp; from the URL, the skin count is (unsurprisingly) used correctly. - The skin submissions page... I realize that because it's just a simple form, it shouldn't need to be that wide, but even still, the large whitespace on the right of the form is irksome...