Crise

tyoe /w or /winamp in chat :)

Well plain gifs should be supported, not animated ones though...

Sort of, there are two on/off options for bot messages (doesn't work for every bot but it is rather effective still). Check settings > appearance > windows :)

If you don't even bother to properly read what the dialog says, please don't make incorrect statements like this... Also please don't compare the farce that happened with Zion to this, because the situation, reasons and program behavior are nothing like Zion's was at that time. And no we are not victims, this is a result of careful consideration and relates to this change log entry of 1.1.0: Fix: Potential remote exploit fixed (thanks Fartman) Why? Because I don't nor does anyone else wish to handle the potentially limitless amount of bug reports caused by this single crash, created by malicious users with no good intent towards targeted user(s).

You ignore a user, messages are ignored if and only if that user is not an op ie. does not have a key in that hub...

Nope I'm afraid not, at present the plugin stuff, is still WIP...

ApexDC++ (or any DC client for that matter as far as I know) does not support downloading copyrighted material in any way. So there is no apparent reason for us to put our effort in adding features that are useful to only people who do download copyrighted material. As said earlier I have nothing against or for this feature personally, but I have no reason to spend my time adding this feature back in ApexDC++ only to start hunting down the bugs in it.

Well if I remember right that had some bugs, but if someone fixes them for me then I am all for it... my own effort is directed elsewhere for the time being.

Exactly the copy menu does not copy users ip, but the contents (text) of the column named "IP"

Yeah, that is true... I am clueless then.

Not in all cases if I am not mistaken, sometimes even SDC has client pointer in privateframe now (since it was added as an argument to some functions)

I dunno but I am fairly certain that if this is not a bug inherited from SDC the reason is most likely the client pointer in privateframe...

We are in no way against bugmenot accounts, and yes Satan both of us know what they are Although at certain times we may disable bugmenot accounts temporarily (like during the recent opening of some private forum areas to registered users as a special event), but generally we are in no way against them as long as no problems come from them... About the subject of the topic, as Satan stated we did try with 15 long ago and the results were very clear... and also as pointed out until very recently DC++, which can nowadays be considered as the mainstream client for DC, allowed no multisource downloading at all. Even though mods have had different implementations of multisource downloading (some better some worse) for a long time now the main reason why it wasn't common is because many hub owners considered, and many still do, multisource downloading as bad news. This is the case probably because DC has long been and still mainly is first to come first to serve based network eg. no real queuing really exists so if user took more than one slot per file for himself this was considered bad. The 10 segments limit was the original reason why multisourcing got accepted in some hubs to begin with as it was considered good enough compromise between limitless slot hogging and DC++'s single source downloading. Though from what I have heard is that one reason for some hubs to allow clients like SDC and Apex is the fact that they really want to get rid of users that use the old reverseconnect as well as emulating users.

This opera vs FF is a never ending subject... I personally usually use both, though I prefer FF because of extensions like firebug and colorzilla :(

I am not sure if this is relevant but if memory serves NMDC has a limit on how many search results are returned from one user, so this limit may kick in and result the "buggy search code" Satan refers to. It is not that the code is that buggy but that the protocol was designed in the ages past To demonstrate what I mean here is another example, the original DC client (the one that created the original protocol, though it was later greatly enhanced by DC++) didn't hadle more than one search at a time and because of this to this day the fact that DC++ and its variants allow multiple searches and search windows sometimes the results sent and received end up in wrong windows etc.

You can't...

hmm... I too tried with few solutions similar to that one, but for some reason I can no longer remember it did not work out as I had planned...

Well interfaces are a common way of doing app<->dll communication, when the link between dll and exe has to be available at random moment... if you don't count that winshit COM thingy. Yes, I am aware that there are ways superior to interfaces, just look at adch++ f.ex. but they are not something that can be easily added to an app that builds on top of another (or in this case a few). What I mean to say is that to a programmer the process of creating such dll is not as complex as you might make it sound, considering that sample is provided. Easy solution, since each plugin has to be GPL'ed (as they have to use GPL code to function) if someone wants to release a wide spread plugin (eg. "official" plugin) Someone who knows the revision used can easily compile them for distribution. Yeah this is no good solution but will have to cut it, until I find my way around the issue, and based on my tests that will not be just using pod's (plain old data types) instead of strings.

It will change don't worry, however, this isn't very reliable detection to begin with and there is no changing that...

look at the code, I was too lazy to explain changes to this feature in depth, as those who use it (ie. those who the changes affect to) will have to have knowledge of programming anyways, and the changes that do matter to them the most are the ones in PluginStructure.h... As for the changes you can't see by looking at the .h file, they are just different ways of doing some things, that I believe are better than the previous way (or simply a matter of personal preference). ps: and since no one seems to bother with plugins does it really matter...

Well you can avoid the promt with 1.1.0 simply by logging on as a user that is not considered an admin...

Yes...

This is from another topic regarding this...

well it might also be default configuration error, or depend on some other app/hardware/driver... the issue is that while I probably update apex most often (and hardly ever make clean install since I am lazy) I would know if there is an obvious issue of this kind compared to previous versions (at least as far as upgrades go)

No matter what I do I can not reproduce this, at present I am on vista though so haven't had chance to try XP...