[lionhearted]

> I use an extensive cookie domain blocklist and that's all there and functional.

Care to share a rough overview of sites you're blocking, and a little of your reasoning? I tried putting fairly restrictive settings on Firefox one time to see how browsing differed - I noted a lot of sites didn't work without explicit permissions, so that's sort of a hassle. Beyond that, is it privacy considerations? Do you work in a field that you wouldn't want your browsing habits logged and cross-referenced? Vagueness on answer is ok, I'm just kind of curious what your reasoning is, and if there's any utility to me building some kind of blocklist for myself.

[stanleydrew]

I know you weren't asking me, but I have a similar setup. I block everything by default and only enable specific cookies when necessary for functionality. Same with javascript, which Chrome makes pretty easy. I don't have any specific reason except that it feels cleaner not to send a bunch of data over the wire that isn't really necessary.

[joey_bananas]

So, how do you do that then? Some extension I assume?

[stanleydrew]

Nope, the functionality's just built into Chrome. It's actually really easy and convenient.

[mtigas]

I allow by default and simply block a (large) number of stat tracking domains and other dubious sites. (Generally I just compiled a large domain list of advertising / stat bug / malware domains, rather than actively patrol my cookies for domains I wanted to block.)

I’ve toyed with doing it the other way around (block by default, use whitelist) but generally it’s too much of a hassle.

This is all more or less a carryover from when I used to be really privacy paranoid — I don’t really have a valid reason outside of that these days. Force of habit. :)