Re^3: State-of-the-art in Harvester Blocking

What prevents them from simultaneously acquiring a dozen session IDs each from a different IP (via an anonymous proxy or something of the sort) though? Implementing this will complicate your code without particularly hindering the harvester.

Makeshifts last the longest.

Comment on Re^3: State-of-the-art in Harvester Blocking

Replies are listed 'Best First'.
Re: Re^3: State-of-the-art in Harvester Blocking by perrin (Chancellor) on Nov 23, 2003 at 22:00 UTC
In practice, very few harvesters are savvy enough to figure out what's going on and determined enough to build an effectively coordinated system for rotating the IDs. The session ID approach will stop most people.	[reply]
Re: Re^3: State-of-the-art in Harvester Blocking by sgifford (Prior) on Nov 23, 2003 at 17:58 UTC
Good point...I hadn't thought about a harvester doing multiple sessions in parallel, because that's not how they've been doing it thus far.	[reply]