Lee

Hi albireo, Yes we are still hiring. How much wxwidgets experience have you got? :)

In agreement with this, but there needs to be a system to stop spam before allowing it.

Possibilities: Limit number of characters per messageOnly a limited number of messages per minuteNo weblinksreCAPTCHA authorisation before sending a message

Agreed. I remember Crise saying there was some message code commented out though, which might mean Big Muscle is working on that.

I'm not sure why this is the case then horus22. Maybe wait till our GUI has been completely re-written to wxwidgets and test it. Unless Big Muscle you have some advice? :)

Hi horus22, Are you hashing when ApexDC++ is open?

PS - Congrats on the Support promotion.

Fixed this Mek.

That's like saying they should go through every setting and set it themselves. It is our responsibility to provide the best default settings for most users. We feel enabling DHT will provide the majority of public hub users with faster downloads, and allow them to collect sources all over the place. This is the true advantage to DHT, and if people don't like that they can disable it. I understand the issue with private hubs and its users, but this is easily monitored and resolved. I know it works because I've seen it. After 6 days, 65% of users in a private hub have already upgraded to 1.3.5 and followed the "You are not allowed in this hub because DHT is enabled, please disable it by following these steps" message. The user count hasn't dropped either.

Nice idea. I will move this to feature requests. :rolleyes:

It's been months in the making, but we're finally able to announce our next major version. 1.3 provides list of changes including merging with the latest StrongDC++ 2.30, 64-bit versions, new features and welcome maintenance fixes. This version includes DHT (disabled by default), acting as a global network across the whole of the Direct Connect network to speed up file transfers and increase sources. Check out the changelog for further additions. As always, feature requests and bug reports are welcome. Download: ApexDC++ 1.3.0 | Plugins for 1.3.0

I think Windows 7 firewall is fine personally. How fast is Comodo at scanning? I've tried MSE before, used a lot of memory but it's a decent free alternative.

Is your entire share getting re-hashed even when you add just one file? Sounds like ApexDC++ doesn't have the correct file permissions to save the hashdata.

Hi dada17, Try using Windows > Close all offline PM messages :rolleyes:

The fundamentals in actually connecting with DHT is different to connecting to another hub from a user stand point. And when you enable DHT, hub still can detect and boot user instantly.

Yeah, it's an issue we have been considering since it was first introduced. Private hubs have had plenty of time to detect and manage DHT users correctly. The benefits to public hub users is brilliant and like you said, not many users would know how to enable it (but would be able to disable it with a message from hub).

Yeah, I will re-upload these tonight. Thanks for the report ;)

How do you mean, so that it could be disabled on a per hub basis? Agreed about experimental, but because it's such an important feature it still should be moved from Advanced and easily accessible.

If you want to start from fresh, just delete your AppData/ApexDC++ settings.

This is something we're discussing in another topic. DHT is a global network of users that is designed to help improve sources and therefore download speed. You can read more about it here. It can also be turned off at your discretion. I'll close this so we can continue receiving feedback in one topic.

Renamed topic title appropriately. Agreed. So make sure you detect that DHT is enabled and disconnect those users. You are banning everybody on 1.3.5 because they *could* be running DHT. No need to ban specific versions, detect and ban the use of the feature. Beowulf: There is no need to stop using ApexDC++. The two solutions you have are to either supply a message to the user on entry, or configure your own client that will be constantly out of sync with development. DHT setting will not be reset again in terms of users upgrading from previous versions. Once a user has disabled DHT, it will never again be enabled without the user's permission. How about moving the option of enabling and disabling DHT into the Sharing settings page? This seems more appropriate than buried in advanced. Big Muscle, what do you think? I'd prefer being able to right click on the DHT status bar like in utorrent and enabling/disabling on the fly though. You managed to take a look at that?

Introduction ApexDC++ is a Peer-2-Peer (P2P) program that connects to the Direct Connect (DC) network. What is P2P? P2P is a term used that describes a network of users that can connect directly to one other and share resources. What is Direct Connect? Direct Connect is a Peer-to-Peer File Sharing protocol that allows users to chat to others via a centralised hub and share files with each other. The beauty of the network is that users can search and download files while chatting to users. DC is made up of multiple clients - ApexDC++, DC++, StrongDC++. Users running either of these programs can download between each other no matter which they choose. The network is centralised, meaning it requires a hub/node where users connect to in order to share and chat. ApexDC++ comes with a ?do=embed' frameborder='0' data-embedContent>>discentralised method of download files - ?do=embed' frameborder='0' data-embedContent>>DHT. The advantage of this is that if a hub is offline, the user can still access users outside of this hub to find more sources. This inevitably will speed up the download process. What is Advanced Direct Connect? Advanced Direct Connect (better known as ADC) is more secure protocol that ApexDC++ (along with StrongDC++ and DC++) is compatible with. ADC supports UTF-8 unicode, better encryption, and has unlimited protocol extensibility. What is Open Source? ApexDC++ and the majority of programs connected to DC are Open Source. This allows cross-compatibility between users and the ability for anybody to use the code to compile. The advantages to this approach are that anybody can contribute to a project and improve it.

Please log this in the new tracker so we can investigate. PS - Try reproduce it with 1.3.5.

When uTorrent came with DHT enabled, private trackers banned it yes. Pretty soon after they made sure that all torrents on private trackers had DHT disabled with a method in place to determine this. We aren't being "elitist". We are sending this information to the hub. A clear message of how to disable this feature is all that is needed. If your users decide not to follow these simple instructions, maybe they feel the hub they are connecting to isn't worth the effort? I think we need more input from you hub owners in our development, rather than once a version is pushed. Maybe we can work something out with that. Mek: It was reset after upgrading to 1.3.5.

The guy has no authority to block or unblock new clients. His hub operator should come and continue this discussion so everyone is happy This topic is not pointless, because we are trying to suggest setting up a system to check DHT .