![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
This journal entry describes ways in which people you know may be monitoring the way you use LJ. How often you read their journal, what friends groups you define, and so on.
It's done with what are called "web bugs" - tiny images served from special servers that record this information. You can block the servers that serve the web bugs, but they can always create more servers, so it's a game of "whack-a-mole".
Today I found out about a setting in Firefox that blocks *all* web-bug based tracking, from all websites to all websites, permanently. No longer will people be able to monitor you in this way.
Go to the URL bar and type "about:config". Select the setting "network.http.sendRefererHeader". If it has the value "2", change it to "1". That's it.
Technical details
I'll be setting this on all my browsers ASAP.
It's done with what are called "web bugs" - tiny images served from special servers that record this information. You can block the servers that serve the web bugs, but they can always create more servers, so it's a game of "whack-a-mole".
Today I found out about a setting in Firefox that blocks *all* web-bug based tracking, from all websites to all websites, permanently. No longer will people be able to monitor you in this way.
Go to the URL bar and type "about:config". Select the setting "network.http.sendRefererHeader". If it has the value "2", change it to "1". That's it.
Technical details
I'll be setting this on all my browsers ASAP.
no subject
Date: 2006-05-10 05:25 pm (UTC)no subject
Date: 2006-05-10 05:29 pm (UTC)(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:no subject
Date: 2006-05-10 05:35 pm (UTC)no subject
Date: 2006-05-10 05:41 pm (UTC)no subject
Date: 2006-05-10 05:47 pm (UTC)no subject
Date: 2006-05-10 06:01 pm (UTC)Referrer data is one of the most valuable ways for any webmaster - even the, you know, not evil ones - to learn about what's going on with their site, who's linking to it, and so on. For BloodSpell, it would be absolutely crippling not to be able to tell where our hits were coming from, and would mean I couldn't easily respond to blogs mentioning the film, couldn't correct errors (like people saying I'm not using Creative Commons correctly), and generally couldn't manage my website.
It's going to be a real pain in the arse trying to figure out why people are viewing my websites and where they came from without referrer data. So unless people have a *really* strong need to turn this off, I'd kinda plead with them not to.
no subject
Date: 2006-05-10 06:05 pm (UTC)(no subject)
From:no subject
Date: 2006-05-10 06:09 pm (UTC)(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:no subject
Date: 2006-05-10 06:09 pm (UTC)no subject
Date: 2006-05-10 06:11 pm (UTC)(no subject)
From:no subject
Date: 2006-05-10 06:38 pm (UTC)no subject
Date: 2006-05-10 08:54 pm (UTC)no subject
Date: 2006-05-10 06:41 pm (UTC)i.e. you might block these particular tools, but your IP address will still be sent, and (as you say in the comments) you'll still send a referer header when you click on a link. So the people who really want to tell who's reading will still basically be able to, just with a little more work.
no subject
Date: 2006-05-10 07:33 pm (UTC)no subject
Date: 2006-05-10 06:46 pm (UTC)no subject
Date: 2006-05-10 06:47 pm (UTC)firefalcon.plus.com - - [26/Apr/2006:23:09:35 +0100] "GET /images/get-ff-sm.gif HTTP/1.1" 200 1786 "http://www.solutium.co.uk/index.shtml" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.3"
The GET is the web browser asking for a file, in this case an image "get-ff-sm.gif" in the "images" directory. After the HTTP/1.1 and two numeric fields, it has a string: "http://www.solutium.co.uk/index.shtml" - this is the referring page. Without that, files appear to be being requested randomly, some sites will block access to images without referers to prevent them being accessed except through a web page.
However, applying the suggested change should hopefully not break most sites people use every day, and, in the face of this paranoid tracking of individuals, is one way to get around this.
Personally I use AdBlock Plus (http://adblockplus.mozdev.org/) and NoScript (http://www.noscript.net/whats) with Firefox (http://www.mozilla-europe.org/en/products/firefox/) - that and changing the Options -> Privacy -> Cookies Tab to "for the originating site only" (e.g. only allow a cookie from mysite.com, not advertisers-site-with-banner-on-mysite.com).
I'm not actually bothered if people know I'm reading their journal (although generally I read from my friend's page, so they would potentially get hits every time I open that page, not necessarily actually read it).
(This is mirrored as a comment on KissyCat's post (http://kissycat1000.livejournal.com/486249.html))
no subject
Date: 2006-05-10 07:02 pm (UTC)Not that I'm that bothered where...
(no subject)
From:(no subject)
From:no subject
Date: 2006-05-10 07:11 pm (UTC)Be careful with forging (as opposed to just not sending) referrer headers. I block visitors who send referrer headers for pages that do not actually point to my site (there's a probabilistic thing that checks them when they occur often enough) because until I started doing that, I was getting a significant fraction of my traffic (over 10%) apparently from zombies visiting just for the purpose of putting advertising into my referrer log. I also block the referrer set by "Outpost Firewall", because as well as being syntactically invalid, it consists of an advertisement for the product, so from my point of view, that's spam too.
no subject
Date: 2006-05-10 07:24 pm (UTC)I don't think you need to use these sort of tricks to see what friends groups exist though.
no subject
Date: 2006-05-10 09:09 pm (UTC)filter=number
to use a particular bitmask (individual groups are 1, 2, 4, 8, 16, etc), this only works for yourself. On other people's pages, the group needs to be marked public (private is the default) and you need to know the name. I guess you could use a dictionary attack if you reallllly want to know and think the person has marked them all public.Maybe you have a different trick in mind, but that's the only one I can think of.
no subject
Date: 2006-05-10 07:27 pm (UTC)Soph x
no subject
Date: 2006-05-10 08:43 pm (UTC)no subject
Date: 2006-05-14 10:47 pm (UTC)no subject
Date: 2006-05-11 07:58 am (UTC)Nice tip Thanks ciphergoth :-)
Firelord
no subject
Date: 2006-05-11 08:27 am (UTC)Will give it a try, thanks.
no subject
Date: 2006-05-11 01:03 pm (UTC)Will I still be able to read the posts that I've stopped from monitoring me?
no subject
Date: 2006-05-11 05:46 pm (UTC)Parcel arrived safely, thanks.
Date: 2006-05-17 01:47 pm (UTC)no subject
Date: 2006-12-12 02:40 pm (UTC)no subject
Date: 2006-12-12 04:19 pm (UTC)no subject
Date: 2007-05-09 10:41 pm (UTC)no subject
Date: 2008-04-01 06:04 am (UTC)no subject
Date: 2009-06-10 08:29 am (UTC)no subject
Date: 2009-06-16 10:25 am (UTC)