Google Docs Explosion in numbers of "red box" unblocked

[Precip]

Dear Sir,

I am unclear as to what happened on March 1.  I was editing a document when I noticed the the disconnect icon getting pounding..the red number exceeded 100 in less than an hour.  I have previously used Disconnect with great satisfaction..but it kinda freaked me out to see much activity directed at Disconnect.

I actually reinstalled Chrome, went back to docs and the event repeated itself.  

Every typstroke and click generated an event. This was not happening before. Forgive me, I am not wise in these matters but did I need to reconfigure Disconnect? I understand an update for it came out?

If you could put my mind at ease that would be great.

Thank you,

Precip.

[Precip]

I selected the depersonalized searches, this changed the huge box count number to a blue color. BLOCKED. But why is Google Docs sending out so many targets for Disconnect to Block.

Is there a privacy setting on Docs one needs to activate to prevent this?

Thanks for any help

Precip

[Brian Kennish]

On Tue, Mar 1, 2011 at 7:02 PM, Precip <pre...@earthlink.net> wrote:
> I am unclear as to what happened on March 1.  I was editing a document when
> I noticed the the disconnect icon getting pounding..the red number exceeded
> 100 in less than an hour.

Hey Precip, I checked the changelog -- that's when I wired the
indicator up to show unblocked requests (in red). The flagged requests
include Google and Yahoo setting cookies, which is what's going on in
this case.

On Sat, Mar 5, 2011 at 10:42 PM, Precip <pre...@earthlink.net> wrote:
> I selected the depersonalized searches, this changed the huge box count
> number to a blue color. BLOCKED. But why is Google Docs sending out so many
> targets for Disconnect to Block.

Docs updates cookies on every keystroke, if I remember right. I'm not
sure why, although it's nothing to really be alarmed about.

Oddly enough, I had a dream last night about working around
Disconnect's behavior here that seems more annoying than helpful. If
the workaround still makes sense to me at the end of the day, I'll try
implementing.