Crise

Management
  • Content count

    2,992
  • Joined

  • Last visited

About Crise

  • Rank
    Developer

Contact Methods

  • Website URL
    http://www.apexdc.net
  • ICQ
    0

Profile Information

  • Gender
    Male

Previous Fields

  • Favourite DC++ client?
    ApexDC++

Recent Profile Visitors

52,623 profile views
  1. ApexDC++ 1.6.3 maintenance update available

    I have updated the first post with instructions for a workaround for the time being. New version will be made available as soon as there is a verified fix for the problem. Relevant link: https://bugs.launchpad.net/dcplusplus/+bug/1656050
  2. ApexDC++ 1.6.3 maintenance update available

    1.6.2 is on sourceforge, the page is linked from the download page. This is an issue with zlib upgrade. It affects all dcpp based clients with the new zlib as far as I know.
  3. ApexDC++ 1.6.3 maintenance update available

    Not being affected by an exploit because a client is old isn't the same thing as not needing updates. It is just dumb luck most of the time. But you are right, that is off-topic.Also, being aware and doing something about an issue are two different things.. Why was it unclear... if another client can't decompress a filelist from the latest version of ApexDC yet that version can decompress its own filelists and another randomly picked client can decompress filelists from it then obviously I have to know which clients the issue manifests with. Also, there is always the possibility it is an issue specific to a single user, or multiple users with something in common when it comes to their shared files, (it could be as simple as the filelist that was generated being corrupted while being written to disk by chance), I am looking for information to reproduce the problem which your original post did not give me. Update: I just finished doing connectivity tests, and ApexDC 1.6.3 generated filelists download and open just fine using RSX++ and Zion++. So, it is definitely not a general issue with 1.6.3 (all involved clients in active mode using default settings).
  4. ApexDC++ 1.6.3 maintenance update available

    I am not yelling at all. Zion, last updated in 2007, and RSX++, last updated in 2011, to be frank I am surprised this is the first issue you have encountered with newer clients. I will do what I can, however, if I can reproduce this issue with the latest version of DC++ then as far as I am concerned it is something that has to be taken care of upstream. No need to be so hostile all I did was as a simple diagnostic question, because for one your post was unclear on which clients were encountering an issue.
  5. ApexDC++ 1.6.3 maintenance update available

    Can you tell me which clients the users people are seeing this from are uaing? (exact versions). Seems to be a backwards compatibility issue with zlib most likely.
  6. ApexDC++ 1.6.3 maintenance update available

    I do use it, although only for chatting, and that is enough for me. If I am going to patch in security updates for my personal use I might as well put the builds out there available for everyone. I don't exactly disagree with you entirely on the state of DC, however, there are still plenty of people who do use it. Like I said in an earlier post, it can not compete as a p2p application, but it does offer something that most other p2p applications do not (and it does so, in my opinion, better than f.ex. IRC, personal servers are easier to set up and if you do need to send files it is way more user friendly). Mainstream p2p, if there is or ever was such a thing, I definitely concur with you DC is far past its time in the spotlight. But at the end of the day, that is understandable, the software was developed when terabyte was a large amount of data and most normal people didn't even know what a petabyte was. DC is not dead though, it just so happens it no longer has large scale public appeal (at least in most of Europe and USA, not sure what the situation is out there in Asia etc.). PS: DC++ is a piece of software, DC is the network (technically even that isn't correct DC being originally a shorthand for NMDC, but it now also covers ADC).
  7. ApexDC++ 1.6.3 maintenance update available

    The code is technically open source even now, as any DC++ derivative should be, just that it is not being actively distributed just as the builds aren't (anyone who has had access to the builds in the past has been, and still is, able to request the source code for any build they have access to, as per GPL's requirement of equivalent access). It will probably eventually end up out there in the open, however, it is literally years behind at this point. Not that it means all that much, considering the cadence of updates on the windows side has also dropped. I know that opening it up might have some benefits at the same time I'd rather not put something out there, generally available, that is in a state not representative of what ApexDC is on windows (generally when it comes to wxWidgets version of ApexDC, it is like taking one step forward on other platforms but taking two steps back when your point of comparison is the windows version). It was never in a state where I could take it up as my daily driver on windows, which is probably one big contributor as to why I wasn't very motivated to work on its problems. I am not sure if I have previously said this here, but in retrospect if I had to make a cross-platform DC client I would probably take the ApexDC core gut the UI out of it and expand the current very barebones web server that it has to actually be modern and fully usable set of API's to which I could then build web based UI for in relatively short time. I believe at least one other client has done this (AirDC) and, even though hindsight is 20/20, it is really the way we should have approached this aspect as well. If only because building web based user interfaces has come a long way in the past few years and it is comparatively extremely fast to building something more native (and the technologies involved are generally very well supported). To give the above a bit of context, my use of DC today is entirely for discussion, it has basically taken the same role as IRC would for most people, the P2P aspect of it is honestly completely secondary to me at this point (also, the performance the protocols can support just can't compete with other ways of distributing files these days).
  8. Thumbnail view

    Depends, such a feature is in theory possible... having said that it would most likely require either creative use of the protocols as they exist right now or extending the network protocols to add this behavior . So, in short. Even if it was done it would only at best work between two other clients that implement this same feature in the exact same way.
  9. ApexDC++ 1.6.3 maintenance update available

    As much as I would wish to say otherwise, that project has been stalled for quite some time now, and minor releases like this one are basically everything I have time for at the moment. On windows, I can put out a small release efficiently, whereas for other platforms my ability to even test changes and make builds available is limited. This works, however, the way people should actually address this issue is by changing the "Balloon Popups" options in ApexDC settings to their preferences instead. Yes, the title of the page is technically not correct anymore but once up on a time it was.
  10. It has been quite a while again. We are pleased to announce the immediate availability of 1.6.3 a maintenance update continuing in the same vein as the two before it. This time the focus is on updating third party dependencies and build tools with the latest security updates and patches. Notably the binaries distributed for the Windows XP operating system had a configuration issue for the previous version and this has now been addressed for our friends still in the past. A full list of changes are available on here. As usual we strongly recommend upgrading to 1.6.3 as soon as possible, regardless of which version of Windows you happen to be running. For the people who need the XP compatible binaries, we would like to give this remainder about changes introduced in release packaging with the previous version. Download: ApexDC++ 1.6.3 Update: 1.6.3 has an issue with compressed transfers, that affects connectivity, turning off the setting "Enable safe and compressed transfers" should avoid this issue on 1.6.3. Alternatively you can hold off upgrading until a fix is available.
  11. i want to change ip address to specific address

    You have your answer then, the hub is not a generally available public hub, ergo you are not supposed to be able to connect to it... and as for getting around that my initial reply covered that already. If you are dead set on finding out how to access this hub, the only people who can answer you are the people running it. Chances are though, if you don't already know how then it is not something you can even do. This is clearly a hub set up by an ISP in some country (I don't know which, nor do I want to), so they have a vested interest in keeping people not part of their network out of it.
  12. i want to change ip address to specific address

    Hi, You can generally not go shopping for a specific IP address... one from a specific country or state yes, but that is generally about the granularity you can have using VPN services. If an ISP happens to also sell VPN services then that way it might be possible to get an external IP in their ranges, however, otherwise not really. Usually hubs with IP address restrictions have those restrictions for a reason, for instance because traffic outside of their ISP's own network costs the users money by volume. So a chances of you finding a way to get your IP address in their allowed range is literally close to zero. If anything you should try and find out why the hub has this limitation, that should tell you also how to get access to an IP in their allowed list (although, as I said, I'd wager it is not something you can just do very easily).
  13. ApexDC 1.6.2 has crashed

    Looking into it some more, it is likely there is an issue with the way openssl is being compiled with 1.6.1 and newer, I will see to it that this is addressed for XP builds with the next version, however, I can't promise it will remedy the issue as I have no access to test on windows XP.
  14. ApexDC 1.6.2 has crashed

    My first instinct, as a workaround, would be to disable the bandwidth limiter if you are using that... as for the crash itself I will have to look into it more.
  15. when logging into adcs hub ...

    Can you tell me which hub software that is... it should be simple to fix, but I have never encountered that before.