The tip was to set the blocked-sites destination to "0". Just plain zero, nothing else. No decimals.
If you have 15,000 entries, that knocks about 120 Kb off of 0.0.0.0, and another 30k off of 127.0.0.1.
Compared to 255.255.255.0, that's 180Kb of file less to parse.
NOTE: Tip said it was only for Windows, only up through XP and Server 2003, and would not work on Vista+. IDK. Works fine on XP:
Code: Select all
C:\WINDOWS\system32>ping 0
Pinging 0.0.0.0 with 32 bytes of data:
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Ping statistics for 0.0.0.0:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\WINDOWS\system32>ping www.doubleclick.net
Pinging www.doubleclick.net [0.0.0.0] with 32 bytes of data
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Destination specified is invalid.
Ping statistics for 0.0.0.0:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Guess: Without the decimals, possibly assumes that 0 is a binary (not decimal octet) address, being 000....000 (32 zeros)?
WFM so far. No guarantees. Undocumented. Use at your own risk, or not at all.