Anti-rmDC++ - Page 4
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Anti-rmDC++

Started by plop, 28 February, 2005, 17:41:55

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Naithif

Quote from: Mutor on 09 August, 2006, 02:50:46
slotblocking should be easy to detect. Either one gets a list [or small file] with minislots or not [$MaxedOut].

Most of these clients have option (and default on) to open minislots (and slot blocking does NOT block minislots in them), so file-lists comes down nice and easy, they only block normal download slots, where they always return with "no slots" message... Even in some clients there's and extra option that sometimes enable download, once in given time, so they can "proof" that they can be downloaded from... And if client check goes through undetected, and file list comes down, is there any other way to detect it than via hubside?

Helios

bad idea bloked good client as dcdm and idc

SMF spam blocked by CleanTalk