: I think I've figured out why I get the Collusion behavior I do. Instead of blocking referrer by default, I had it said to spoof to a google.com address. I normally hit google.dk, so while referrer links pointed to www.google.com/somethingsomething
, I had never actually visited that address.
I think that could explain why Collusion shows a bubble for each site, but pointing to nothing.
After I visited google.ae (to make sure it existed) and set the spoofed referrer to hxx
p://google.ae/search?q=midget+nazi+porn , all visited sites after that link to (surprise surprise) google.ae. This does look quite festive, but it also means Collusion is extremely slow - and the graph isn't very useful for spotting actual referrer problems. I guess it
would be saner to block by default rather than spoofing, but... spoofing is funnier Amazon creepy ...
Or perhaps what I really want is an "advanced" mode that lets me do some regex matching That'd be nice....I look forward to "f0dder's Referer Mangler"
I think I already have some ideas for improvements, but I'm already spread pretty thin, and have never looked at extension development before. And I'd hate forking an extension, making some changes, and then not keeping it up to date. I also kinda think some of the ideas I have would be too large in scope for the RefControl author wanting to include it in his pretty lightweight plugin.
I'll mull a bit over this
EDIT: just reset Collusion and changed default RefControl action to block, visiting new sites pops up the individual bubbles again. I think I'll keep the setting at block - easier to see connections that way. And while Collusion slows to a crawl even with just the individual bubbles, adding edges (and the "node pull" that incurs) makes it even slower