Big Muscle

Member
  • Content count

    702
  • Joined

  • Last visited

Everything posted by Big Muscle

  1. it's not bug... windows are and will be maximized only
  2. Multi-Part? Download Issue

    it is not being worked on... it has already been done.
  3. Multi-Part? Download Issue

    it's already there. I tested on LAN with speed over 8MB/s and it works nicely :)
  4. Multi-Source - bigger in the future ?

    No, because it's not needed. It will only eat all slots in network and anyone couldn't download.
  5. Why forcing ApexDC++ update?

    I think that you don't understand the purpose of Beta version. Once you wanted to use it, then you agree with testing process. If you don't want to test beta version, don't use any beta version. It's easy. Beta versions are for testers and if you are normal user, don't use it.
  6. Public Development Starting

    ermm, sorry but we are following situation: when did the Linux come to the world? before 20 years? maybe... and every Linux user said "Linux will win as OS and everyone will use it". Now in 2008, the Linux users say still the same sentence and for that long time (maybe 20 years) Linux got only very small percent of usage on desktop PCs. (Server PCs is different story, because this application isn't for servers but for workstations)
  7. Public Development Starting

    still not MS problem. Win32 API is Microsoft's work so it doesn't have to give the code to anyone.
  8. Public Development Starting

    it's not Microsoft's problem. It's Linux who doesn't support Win32 API and therefore a lot of application don't work there.
  9. Public Development Starting

    I would make client part to compile in Linux, but windows part? uhmm... no! and btw time to realize MS Windows is the future and Linux is dying :D
  10. Public Development Starting

    Sorry, but your post is really a mess. DC protocol specification you post is not the real specification. It's just because no specification for DC protocol exist. So we can't talk about compatibility with DC specification. DC compatibility means that the client is able to connect to DC hubs and is able to cooperate with clients in there. And I have no problem with DC++ (and its mods).
  11. 1.0.0B4 crash, merklecheckoutputstream...

    TTH in crash report is TTH of your ApexDC++ binary to detect if you have legal copy of this application :crying:
  12. Dynamic resource usage

    StrongDC++ already decrese its priority on minimize and that's all what can be done. And about Idle processes? There's nothing below Idle priority (and priority 0 is reserved for pages zeroizing in memory management)
  13. Huh?

    Why? Windows Firewall is very good.
  14. Multiply Search

    Having search interval doesn't mean we can send as many search requests as we like.
  15. Programmers make clients to develop the DC network, so it's up to them to ensure that network won't be destroyed by stupid users. And this is exactly the reason why it won't be implemented. Hub A: min share 5 GB Hub B: min share 15 GB Hub C: min share 40 GB now user being in hubs A,B,C needs to share 40 GB, so it provides great amount of data also in hubs A and B. Implementing hub-dependent share would allow him to share only 5 GB in hub A and only 15 GB in hub B. So his upload would decrease dramatically and amount of shared data in network would decrease too.
  16. The reason of not implementing is that it can be abused for destroying the network => users will share only a minimum amount on each hub to decrease their upload.
  17. Managing segment speeds?

    of course, look at Settings > Limits
  18. Temp Sharing

    You are teoretically right. But not practically. In our country, OPs kick nearly everyone who shares any legal useful material and ignore illegal but unuseful stuff. and I will repear for the last time. It's user's free choice to select this client and it's user's free choice to download the files. So nobody can say that he doesn't agree with activities of this client.
  19. Temp Sharing

    because they share only stupid unuseful stuff, so nobody could download from them
  20. Temp Sharing

    But you chose it as free act. And you agreed with this. Or, have you been forced to download the stuff? Have you been forced to use this client? I guess NO.
  21. Temp Sharing

    Yes, there will be option to disable it => if you don't download anything, it won't share the downloading stuff. And it doesn't do anything without your agreement. You decided as free act to use this app for sharing. Following has been written many times but I'll repeat it: THIS APPLICATION ISN'T FOR DOWNLOADING. IT IS FOR SHARING. EVERYONE HAS RIGHTS TO DOWNLOAD THE SAME THING YOU WANT TO DOWNLOAD. AND IF YOU DON'T WANT TO SHARE THIS STUFF, THEN GO AWAY FROM SHARING WORLD!
  22. Temp Sharing

    yes, it will be changed => Partial File Sharing will be OFFICIALLY enabled also when segmented downloading is disabled
  23. ApexDC++ 0.4.0: Upload Slots Bug !

    no, it doesn't override it. The "Slots" settings means the minimum number of slot which will be opened.
  24. ApexDC++ 0.4.0: Upload Slots Bug !

    then don't visit 25 hubs
  25. Remove displaying of limiter?

    You can't... if you want to fake your connection speed, other users should know about it!