Jump to content

WebReaper

Established Members
  • Posts

    285
  • Joined

  • Last visited

Everything posted by WebReaper

  1. IE6 isn't supported because of MS's lack of adherence to standards in that version of the browser, and because of the way the webui is implemented. It won't happen because MS isn't going to go back and fix IE6 to make it adhere to the standards. The WebUI works just fine in IE7 (which MS will be releasing to all IE users as a 'security update' once it's out of beta). That's all you need to know.
  2. For all the people slagging the lack of support for IE6, as ICleolion says, slag MS for not supporting it. On the other hand, the webui works beautifully under IE7 RC1.
  3. Aye. Look at MS's release dates and their slippage. If they can't manage it, why should Ludde be able to?
  4. Could be worth popping up the 'About' dialog the first time they run the app. That's what I do with www.webreaper.net - I have a warning dialog about some stuff the first time the app's run.
  5. I use uTorrent behind a dg834 and have done for a few months. No problems (and I've been using all the betas, and now 1.6 stable).
  6. Aye. Stop leeching and your download will increase.
  7. And what's wrong with that? Ludde's only got a finite amount of development time, and the whole point of the feature request forum is to find out what priority new stuff should have. If you post a possible feature and 200 people immediately jump on the thread and say "yeah, good one, I'd love that" then he'll prioritise it higher. If 50 people jump on a thread and say "you can do that anyway, via a->b->c, and besides, it's pointless because of xyz" then he's going to prioritise it lower. Whilst (as Firon said in another post) this is not a democracy, it's got to be helpful to the developer to know whether to spend time developing a feature which the majority of users want, and whether not to spend time developing a feature which is really just a workaround for a rare scenario and which isn't required because the functionality already exists - albeit via another mechanism. To be honest, I can't see why you'd need to regularly change the number of queued torrents anyway. If the torrents have enough seeders to max out your connection, then messing with the queue length won't download them any faster. And if you're having to increase the queue length so a particular torrent gets downloaded sooner because the others ahead of it in the queue don't have enough seeders, surely you can just hit 'Force Start' and away you go? I've been running bittorrent clients for years (and uTorrent for 3-4 months) and have never had to change the queue length once.
  8. What a stupid reason not to post in the features forum. I've never seen anyone unncessarily post negative comments about features.
  9. Any reason why you're so impatient?
  10. I'm using Firefox, and I saw 463 just fine.
  11. Agreed. Can't we make it uTorrent-green?
  12. It's a beta! I'm sure the logging will get reduced in the final version.
  13. Lots of good apps listed in this thread. I'll add one: Offline Browser/Site-ripper: Webreaper
×
×
  • Create New...