Special Analysis:
A Comment on Cookies
A "cookie" in computer terminology is a small file written onto a computer user's hard-drive. The cookie is usually created by a javascript routine embedded in the code of the Webpage. When a person goes to a Website, it is very likely that the server holding the files for that site will put one or more of these cookies into a special directory on the visitor's computer. Not surprisingly, the directory in which these cookies are saved is called "Cookies," and each user of a particular computer will have his or her own sub-directory with this name.
A cookie contains information in text and code. This information allows the host server of the Website to know certain things about the user, especially about that user's previous interaction with the Website. For example, a simple cookie might be nothing more than a notification of when the user last visited the Website. That way, when the user visits again, the server knows the person has been there before. This might be useful for something like, say, a new versus returning visitor welcome message or site introduction window.
Note, by the way, that the word "person," here, is a bit fuzzy. For the most part, a server sees a computer, not a human being. Cookies can personalize the interaction to some extent, but a server computer generally can't tell who is on a visiting computer. The visiting computer, itself, is uniquely and clearly identified by its so-called "IP address," where the "IP" stands for "Internet protocol." The human at the computer could identify himself or herself by certain information entered on, say, a form; but even then, there is still a lack of complete certainty at the server level regarding who exactly is sitting at the machine during a given session. Eventually (and quite possibly now with very sophisticated programs), the actual person will be identifiable, but that's not much of an issue for the time being. For all intents and purposes, only the computer can be identified with any degree of certainty by a server. A cookie can help narrow down who exactly is on a computer. If two people use the same computer but have different accounts on it, then the cookie set for one user would not be in the "Cookies" folder of the other person; hence, a server that had already tagged the IP address of the computer could further narrow down the actual user by reading a previously set cookie that only one of them had.
There are many ways to classify cookies. Simple cookies generally store a cache of information based upon the very appearance of the visitor at the site or upon options and preferences the user has specified once there. An example of the latter is when a visitor can select certain display preferences (like color scheme, size of fonts, etc.) for a Website. That information would be stored in the cookie for that Website so that, when the visitor came back, those preferences would be loaded automatically. Some cookies set automatically while others build information based upon what you do.
You might have noticed that some Website, especially some blogs, have a "Remember me" checkbox: if you check it, a cookie will be set in your computer. This cookie holds the basic form information about your name, your e-mail address, your homepage, etc. The cookie will ensure that this information will be filled in automatically every time that form is displayed after the cookie is initially set.
The automatic form fill-in is a very common application of cookie functionality. It saves people having to fill in the same information every last time they have the same form come up.
This could be a worrisome situation. You might be thinking, "But I put credit card information into those forms. Is that information sitting in a cookie file that anyone could read?" Yes and no: yes, the information might be there; but no, the information isn't readable because it's encrypted, so only the originating Website would have the "key" to decrypt and read the code properly.
The complexity of a given cookie mostly has to do with how much information it stores, the kinds of information it collects, and the manner in which the information is retained for later use. Cookies, in and of themselves, are nothing but text files. They can't do anything but hold information for later retrieval. By themselves, they can't run around on your computer and look for all kinds of other information; but that doesn't mean they can't have that information put into them. Other programs can work with cookies to build an impressive laundry list of interesting and exciting facts about a computer user. In particular, Java and ActiveX scripts can do all kinds of snooping, then either report the results directly to a server or put those results into a cookie or other file for later retrieval or broadcast.
Cookies also, by their very existence on a computer, tell a story. Each cookie has a name, usually something like Joe@hotdog.txt. The "Joe" is the name of the user as the computer sees him. (His name might not be Joe, but at some time in the past, probably during the installation of the operating system, he told his computer to call him "Joe." If Joe never gave himself a name for his computer to use, it would probably call him "default," which is why some people see all their cookies start with that word.) The part after the "@" is the domain name of the Website that set the cookie. In this case, we know from just looking at the cookie's namenot even opening the cookie to see what information it containsthat the computer user named "Joe" went to www.hotdog.com.
Suppose we saw Joe@hotdog[1].txt and Joe@hotdog[2].txt in the cookies directory. That would mean the Website www.hotdog.com set not one but two cookies.
Perhaps you see the privacy issue. The cookie directory is a free listing of every cookie-deploying site Joe has visited. Oh my gawd! Look at some of those cookie names: Joe@lolibimbo.txt, Joe@boweltroublenow.txt, Joe@whosyerdaddy.txt, Joe@manhoodextendersolutions.txt, and other unfortunate entries.
Gracious. Our friend Joe does get around, if only in his imagination in cyberspace. The cookie directory is by its very listings a profiling resource. (In Joe's case, the profile is clear: L-O-S-E-R!)
Let's crack open a cookie to see what's inside. It's a text file, so nothing fancier than plain old Microsoft Notepad is appropriate for viewing the contents, which we find to be a combination of numbers, words, and strange bursts of unintelligible characters. Never mind the unintelligible part: that's usually nothing but computer language the Web browser and server understand. The numbers are likely to be the output from counters of one kind or another: how many times the user has visited, how long the last visit went on, etc. Long strings of numbers often show the manner in which the particular cookie generator records information about preferences set by the users, the environment on the computer the server detected on the last visit, and sometimes encrypted data. There should also be at least one date somewhere in the code, but this might not be easy to recognize in the mass of numbers, percent signs, and strange-looking garbage. One date is important: the expiration date of the cookie, the time when the cookie is no longer valid. This is set by the javascript that's in the code for the Web page that set the cookie. Web browsers keep an eye on expiration dates to know when to get rid of cookies. Here at The Dark Wraith Forums, for example, the expiration date is in the year 2040, which means your host doesn't want that cookie getting wiped out until the year 2040. Your host here figures you'll either be dead by then or you'll have moved on to something more interesting than coming here.
Some cookies will have your name and other information. HaloScan, the commenting system preferred by many bloggers, writes a cookie to the user's hard drive that has the information you enter to put in comments, as well as identification information, counter output, and other stuff.
Some cookies record entry page, some record exit page. It all depends upon the sophistication of the script that writes the cookie.
Can a cookie set by one server be read by the servers of other Websites you visit? The answer is in the affirmative, but remember that cookies are written by scripts, so a reader from a non-originating site would have to understand how information was being laid out in a particular cookie to translate the contents into meaningful data. It's not as easy as just having a server look in the "Cookies" directory to rummage around and get all kinds of great information. Scripts to make cookies can be pretty generic, so it's not that difficult in some circumstances for one server to detect and understand a foreign cookie's content. However, if a cookie has encrypted information, that's a whole different issue since a snooping server would have to be able to crack the encryption to get to the interesting information in a foreign cookie. More importantly, it's not as easy as it might seem to get at a cookie that doesn't have the same domain name as the site being visited. It's not impossible; but it's definitely not just like clicking on a directory on your local computer.
Returning to the matter of the NSA setting cookies, a little bit of knowledge goes a long way. The brouhaha that started this week has to do with the fact that the NSA was setting cookies that didn't get deleted when a visitor closed his or her Web browser. In other words, the NSA cookies were "persistent" instead of "session" cookies, which means they didn't have immediate expiration. So-called "session cookies" are no more or less "safe" than persistent cookies, the ones that stay on the computer and don't get deleted at the end of a Web browsing session. A session cookie won't be able to keep track of, say, how many times you've visited the NSA Website, nor will it be able to keep track of other surfing habits you have.
But the point is this: the type of cookie the NSA was setting is rather irrelevant. Once a cookie reports an IP address to its "mother," that information goes into a database. When the visitor unknowingly enters more information to an old (persistent) cookie or unwittingly causes the creation of a new (session) cookie, that information gets sent to the "mother," which then adds it to the database, which keys to IP addresses. In other words, the snooping goes on whether it's one cookie staying there persistently or a string of cookies, each associated with a single session. This means just about anyone could have a profile being built up in that (purely hypothetical, of course) database at the NSA or wherever else profiling of people is an on-going practice.
And on another point, going to a government Website and being shocked that the agency sponsoring the Website engages in snooping is a bit silly. It's sort of like walking into a cage with rabid lions and being quite offended when they eat your hind leg. This is the era of the neo-cons: they run this government, and they're not nice people. They have no use for personal privacy; and they're quite literally out to rule the world and to do so through mendacity, violence, and lies. They don't play by rules ordinarily anticipated by members of a civil society that greatly values and jealously protects personal privacy and individual liberty.
They just don't.
In any interaction with their kind and their government, expect that you will be treated to the full power, ferocity, and ill will of technologically-enhanced Medievalism.
More to the point, though, cookies are a terribly inefficient means of snooping. Even when they're used, to be clear and compelling threats, they usually need to work in conjunction with ActiveX or Java routines. (And don't confuse Java with javascript; they're not the same.) Cookies are the poor-man's Peeping Tom devices. They can, to a certain extent, be used for tracking and other backroom work, but there are far more effective ways to use the Internet to spy on people. Many are the suckers who buy anti-spyware software packages that tout thousands and thousands of "spyware" implementations they remove, but such claims are misleading. All those anti-spyware packages are doing is collecting lists of known cookies, then including them in the "spyware" that's going to be removed. That's not entirely a bad thing, however, since cookies that are deployed in marketing networks ultimately build marketing profiles of Internet surfers, and this might not be desirable for some people who have quaint ideas about personal privacy. The Anti-Spyware Software Review Website describes in some detail how this game works, but to consider that type of profiling as tantamount to government spying through your computer is just not reasonable.
The National Security Agency is a cream-of-the-crop spy operation; it has some of the best spooks that money and calls to patriotism (or coërcion) can buy; and it has a black-box budget. Anti-spyware and cookie deletion utilities bought at Elmer's Discount House o' Software aren't going to stop spies who want to know what you're doing; and manually going into the cookies folder on your computer, finding a cookie with the name "Joe@nsa.txt," and deleting it does not in any way, shape, or form give you bragging rights for outsmarting the National Security Agency.
If spies want you to know they've been in your computer, they'll make it so you can see that they've been there. If those same spies don't want you to know they've been there, they'll make sure you don't.
This is related to the matter of why it is that the U.S. releases people from detention where they've been tortured, knowing full well those people, once they're freed, are going to run around screaming, "I've been tortured! I've been tortured!" If our good national security folks don't want it known that someone was tortured, it won't be known. In the same way, if our good national security folks don't want it known that they've been watching you, then you won't know.
In most instances, when we "discover" something the spies have been doing, it's either because they don't care or more likely because they want to advertise, and all the howling upon discovery of the obvious gives them a megaphone at the same time the howling throws in the value-added red herring for their purposes.
To believe otherwise is to assign to our spooks the same level of stupidity possessed by our President and his cabal of crooked, incompetent cronies. Rest assured that, unlike George W. Bush, the operational-level folks at the NSA, the CIA, the FBI, and all the other agencies of ill intent are not stupid, nor are they incompetent.
They are dangerous, mean, frightening, untrustworthy, vicious, and nasty; but they're not stupid.
These high-end law enforcement and spying community men and women are not in some grand sense worthy of idol-worship. They are people who will hurt you if you get in their gunsites. The nearly god-like status to which some people assign a spy like Valerie Plame is misplaced: she, like all excellent spies, did work that in some instances would make your blood curdle. As necessary as spycraft is to the survival of the state, as art and science it is a scythe that does not discriminate between you and anyone else considered an enemy of the state. Should it ever become the case that what you do constitutes work contrary to national security, you will know that you've been followed, profiled, tagged, tracked, and fully quantified. The only problem is that you will know it once it's too late.
The NSA cookies, persistent or session as they may be, are not the focal point of any domestic spying agenda, nor are they even the tip of the iceberg. They just aren't. To think otherwise is to stare at penguins bobbing in the water and argue about the significance of the danger they pose to the hull of the Good Ship Personal Freedom while that good ship, itself, is sinking because of the massive underwater charges that were detonated beneath it.
Regardless of how deeply flawed that last metaphor was, the point is this: if you criticize this Administration, assume that you are being profiled. Assume that the profiling goes on in your Internet travels and pleasure as well as in your real-world life. As a corollary, assume that, if you really do come to be regarded as a threat to national security, you will pay. And if you believe that the "rule of law" will ultimately win the day and that your free-speech right of protest against the government will be upheld, you might be gruesomely surprised to learn that historynot the kind in movies and fantasy novels, but in real lifehas no special fondness for the good guys.
On the other hand, character-building through suffering is woefully underrated these days.
And living forever is terribly overrated.
The Dark Wraith encourages you to have a great Internet experience tonight and always.



<< 35 Comments Total
I suppose I should thank you for using Joe in your cookie examples instead of the usual Mr. Goat visited Catholic Girls Wear Thongs.
Computer security is one of those things that you either need to keep on top of it ALL the time, or rely on mainstream press (so to speak) to inform you of the latest dangers. Case in point: I used to consider myself reasonably up to date (I have at the moment, six different spyware related pieces of software on my computer - see my comment/question to you on the Message Board), but just only heard of Web Bugs yesterday with the Whitewash House tracking issue follwing in the foot steps of the NSA story.
Quite frankly I am disgusted with myself for being in the dark, 'cause now I'm certain there are other things worse than bugs out there.
BTW, if we don't cross paths in the next day or so, Happy New Year.
Good evening, Mr. Goat.
'Catholic Girls Wear Thongs'?!
O-KAY, then...
Anyway, it's funny you should mention Web bugs. Those things have been on my mind a lot, lately. I get ad graphics all the time that have those little snot-shooters in them. I strip them out with a religious passion. They are getting so common, now, that it's driving me crazy. And it's not the companies, themselves, that are pulling this nasty little stunt; it's the marketing affiliators doing it. I know for a fact that, at least in three cases, my corporate advertisers have no clue that Web bugs are being used. Worse is that the companies don't even know what the Web bugs are, how malicious they can be, or what the consequences of them are on the companies' reputations and their very ability to get their ads out there to the potential consumers.
I explained to one corporate marketer what was going on, and she seemed totally clueless and not very interested in the whole matter until I explained to her that some of the good spyware programs (and even browsers) might actually block her company's ads on Websites when the Web bugs were detected.
She got all kinds of interested at that point. (Yes, I was being a little overly dramatic about my point, but at least I got the lady's attention.)
I haven't finished my campaign on this issue with my advertisers. In fact, I'm just getting started, and I'm looking forward to the day one of the affiliators gets in my face to ask where the tracking bugs are. That's when I'll encourage the affiliator not to look at my hit counters at the bottom of this blog, but instead to look at the advertisement "impressions" number on the main marketing syndicator's stats site for this Website complex.
GAWD! but those Web bugs bug me.
Anyway, the Web bugs are only the latest round in a war against privacy that's ratching upward at an alarming rate. Some of this crap that's going to start showing up in waves and droves over the next year is enough to make a sane person go back to smoke signals and petroglyphs for interpersonal communications and entertainment.
Smoke signals aren't a particularly secure communications method, but the entertainment value is pretty high when the blanket catches on fire before the message is complete.
Talk about a bad connection.
The Dark Wraith reaches for the fire hydrant.
Good evening Dark Wraith.
Your post, both enjoyable and informative, is also quite scary.
However, really, it's rather obvious the cookies you use in your example are-shall we say-familiar to you. I suppose it is easy to just open up the folder on your computer.
Of course, you are free to protest all you want, but it will just reinforce my belief. So, it's damned if you do, damned if you don't. Gee, kind of like the message of your post.
Good evening, Guy Andrew Hall.
I, sir, will have you know that my Internet surfing is restricted exclusively to Presbyterian, Methodist, and certain Baptist Websites of an upright and wholly wholesome variety.
Why, just the other day, I was at Blogging Rectitude Online, reading an article entitled, "The Lord is My Co-Blogger." You should read it. The author was talking about a new software package called The Online Collection Plate that comes with a free trial copy of Faith Healing through Broadband.
But the best part was the testimonial from a former IPod user who was installing Windows XP on his son's computer when he saw for just a brief moment in VGA mode the image of the Lord Jesus just like it looks on the Shroud of Turin.
The whole article was inspiring to say the least, and I'm proud to have that cookie in my cookies directory.
The very idea that I'd go to some Website with a domain like www.extendyourmanhoodsolutions.com is just... just... preposterous.
The Dark Wraith doesn't waste money on what the Lord God has gifted him already.
Good morning, Dark Wraith.
Thank you for the information about cookies. Very indepth. I remember when they first came out and so many of the sites said if you wouldn't accept their cookies, you couldn't see their site. At the time, many were worried about cookies being added to the space of the hard drive. Sure, they take up next to nothing, but when the computer is full... Of course, nowadays, it's something taken for granted, clean out the cookie folder when finished. Never really understood what exactly they held, knew there was a txt file involved, usually. If I wanted to clean every last one off my computer, where else could they be placed?
The Dark Wraith doesn't waste money on what the Lord God has gifted him already.
I think Guy was referring to boweltroublenow.com due to eating that Spam for breakfast, lunch, and dinner. For what is it worth, add a little fiber to the diet and you won't need to visit that web site nearly as often. Cookies with oatmeal are a good start.
Good morning, Old White Lady.
The cookies should all be in the Cookies sub-directory; however, that's not necessarily where you'll find all instances of the text files. Going through and manually wiping out cookies is not a terrible idea, but you should note the names of some of the cookies, then do a search from the Start bar or from right-clicking on the "Documents and Settings" folder when you have the "My Computer" folder open. (The Search routine is automatically narrowed down to the "Documents and Settings" super-folder if you do the right-click method; otherwise, you'll have to use the Advanced options to narrow the search to the desired directory if you do the search from the Start menu.)
I know a number of people who manually go in and clear out cookies, and I've found the same text files in other directories on their computers. In one case, a student of mine—a very sweet, very openly Christian girl—asked me to help her father, whose computer had become overwhelmed by smutware. She swore all he had done was go to a Christian dating site, and then, all of a sudden, his desktop was constantly being filled with little pop-ups of pornography. Obviously, the man had been prowling all over the sleaziest sites he could find, and he was lying through his teeth to his gullible daughter. I wasn't going to get involved in the mess, but then I relented because the girl used the computer, too; and I really didn't think she needed the nightly shows running in little windows all over her dad's computer.
The upshot of cleaning up the mess was that he had literally hundreds and hundreds of cookies, and many of them were showing up in several directories. It was like chasing down a herd of mice. Worse was the fact that several smutware and malware installations had put stuff in his computer's registry, and some of the registry entries had references to the directories where those cookies were showing up.
I did some of it manually, then I did the rest of it with spyware sweepers. (I probably should have started right away with the spyware killers, but no! I had to go in there and start shooting like a blind fool and causing more trouble than I had to start with.) The second sweeper caught a few things the first didn't. As it turned out finally, his computer was more or less a loss, though, when it was all over. Re-installing Windows XP from scratch has very recently turned out to be the only complete solution, although I have this bad feeling...
That issue is still on-going. I thought I had dealt with it some time back, and now that the re-installation has been done, I've been asked to "make things the way they used to be" on the machine. I take that to mean I'm expected to retrieve lost files or something.
Lord.
Anyway, do that search as I recommended. Just write down the names of some of the cookies you see in the folder where they're supposed to be, then use those names in a broader search.
But always remember what I've said before about taking advice from me:
It's Bill Gates's universe;
I'm just a hacker in it.
The Dark Wraith isn't going to anyone's place to fix problems with computers anymore.
Good evening, Dark Wraith.
Thank you for that info. As soon as I get my DVD player working, I'm going to see what I can find on my computer. I downloaded a weather program that keeps giving me popups. The ads say its from the program I recently downloaded. That's the only one I remember. Except for the Xsoftspy and I wouldn't think they would have popup ads.
Happy New Year's Eve. I hope you (and everyone, of course) have a good evening and good start on the new year.
Happy New Year DW and ALL
I'll have some chocolate chip please !!
...forgot to mention how I learned a long time ago all about "if they want to know who you are they will"..
Quite true..they did too.
And a great and happy new year to all of you.
It's going to be an exciting year: either things will get better, or they won't.
Either way, it will be exciting.
Uh-oh... it's almost 2006.
Quick, everyone! Head for the bunker! There's plenty of food in the cold storage locker; there's a 52-inch wide screen plasma TV, with 1,346 of the greatest movies of all time on DVD in the cabinet; and there's a karaoke machine on Lower Level 4.
The Dark Wraith plans well for an exciting new year.
DW,
That was a very informative post, and I mean that sincerely.
Let us hope that there be Peace this 2006.
Happy New Year DW,
I just learned more than I ever wanted to learn about cookies, but it was quite informative nevertheless. I don't understand what all that pop up stuff is that people were talking about. I don't have that. What am I doing wrong? Seriously, I have no clue what spyware is or pop ups. Of course I only visit southern baptist websites and this one.
I'm not worried about the government spying on me. I don't do anything wrong. I shop at Amazon and eBay and read daily affirmations from the bible and war blogs. I also read the WH website regularly because I enjoy reading the words from our great leader in their entirety. The liberal media usually only shows snippets and I like the whole shebang.
Like most Republicans, I am very optimistic about the future of our country. We will blast all the bad guys right off the planet. Our economy will grow in leaps and bounds once the tax burden is taken away from the wealthy. We will eventually all begin to swagger and speak in faux cowboy despite being educated in the northeast.
When anyone says, "Muhommed", people will say, "Who?". We will wipe terrorists and religious fanatics right off the face of the earth so that everyone will worship the one true god of the old testament. Sure he will smite us with lots of disasters, but what is a god to do when his puppets cut their strings and try to live life in accordance with satan? A good flood or earthquake usually gets people back to praying regularly.
Other than a few disasters which will only bother infidels and liberals, '06 will be peachy.
With love, beauty, brains and boobs
The Blonde One
I tried to install a comment box yesterday and when I moved it from inline to table style all of a sudden I had to BlogScreams, no comment box.
I removed it immediately because I was actually adjusting the preferences from a remote website. I don't particularly like being tracked by a website that can adjust other functions of my page.
I have a Mac so I haven't found a program for web bug removal yet, but NoScript, Adblock and that I very rarely go to an objectionable site (I'm really boring) have helped with some stuff, but I like some cookies, just not all cookies.
Thanks for all your help. You write computer stuff without the I'm smarter than you attitude, even though you are. :)
Happy New Year Dark Wraith,
Your commentary written so all may understand should serve to keep some honest who might otherwise slip into the noose of the henchmen who currently oversee our every move. This is a matter of extreme diligence and there will be no room for fatalism regarding the henchmen in charge. If we write what we believe and are not malicious in our intent all should be well. Freedom of speech rights are not easily given up and we have a responsibility to our forefathers to uphold them.
Good evening, Charlie Potato.
A person I know asked me today if I thought the Blogosphere was become a "neural net." The suggestion stopped me cold for a moment because it hadn't occurred to me that it might very well have achieved that status: malevolent forces might very well be able to shut down one or even many pieces of this "thinking machine of many parts," but that wouldn't kill the engine's ability to continue thinking.
Free speech has become something new for us: it can't be killed unless the entire organism is killed.
And that's going to pose a bit of a challenge to our neo-con friends.
The Dark Wraith thinks that's very cool.
Good evening, Debra.
You are exactly correct to get all kinds of concerned about any installation on a Website that has any capabilities outside of its frame. I have run into great looking features I could put on this blog or other Websites I master, but these services showed very worrisome characteristics that just flipped me out when I saw what they could do to other parts of my site. What really amazes me is how some of the major Websites, including several big news services, are routinely letting advertisers put up stuff that is quite unfriendly to visitors and affects the overall functionality of the site, itself.
One news service in particular is so enamoured with making bucks off advertising that it allows its advertisers to virtually wreck the site with some of the ads that go in during the news cycles. Another service is rather well known among Webmasters for having let an advertiser do a promotional trick that was so bad that the site lost more than three-quarters of its average pageloads over the week that the ad was running. (The Webmasters of the site, itself, seemed totally clueless that this advertiser's junk was causing the steep drop-off as the week went on.)
It's difficult for bloggers because everyone really wants to offer functionality, services, and even maybe some advertising to enhance the blog's drawing power, but knowing what to put in and what to stay away from is a challenge. Your solution is probably the best for many bloggers: if it does something you think looks suspicious or otherwise troublesome, drop it like a hot potato.
Of course, the alternative for me is to create things from scratch, which leads to all kinds of frustrations getting stuff to actually work the way I want it to. The good thing is that those kinds of projects certainly do make me more of a religious man... at least to the extent that I invoke the Lord's name quite a bit during the beta testing.
Then again, as I recall, when I don't get any response from Heaven (and I never do), I start invoking the folks on the other side of the Chasm of Afterlife... but they don't answer, either.
I guess that's why all those supernatural types are immortals: they know enough to stay away from doing the kind of Webmastering that turns a young person into an old, babbling guy.
The Dark Wraith should probably pay attention to the lesson therein.
Good evening, well, morning actually. Apropo of the discussion, having become intimate with my cookie files recently in attempting to figure out why I could not get here using Opera, I wanted to announce that having given up trying to fix the problem, it miraculously does not appear to exist now that it is 2006, since I have just read the forum with no crashes.
Yes, a happy New Year to all also. I began the New Year as I hope to continue, with London Broil and Monkfish(the poor man's lobster)with asperagus and twice baked potatoes, sauteed and broiled onions and portabella mushrooms. And of course champagne and friends. Midnight dinner on NY's eve, Clover-style. Sorry DW, no Spam last night.
This post has been removed by the author.
It's funny, I have always assumed that when I visit sites like cia.gov of fbi.gov or even nasa.gov that I am going to be tracked. I just make it a habit of not puting anything on the computer I would prefer the government not know. I didn't really think much of the NSA site dropping persistent cookies. I would be far more concerned if they were dropping file read programs - which they might, in fact probably do. I would rather tend to think that to a certain degree when we access information through municipal or government agencies we leave a lot of our information behind when we access that. Why would it be a surprise that they would drop simple cookies?
good morning dw---first let me echo debra's compliment on your non-condescending style.
i have been relying rather heavily on my mac's resistance to infection. best i get up to speed here. web bugs? oh dear, never even heard of them.
nice rant you had in comments about rectitude online. that and my pet goat's catholic girls comment will have us all reported to the religious division of the thought police. i'm probably on that sh*t list already.
i always assume that they will spy on me if they want, so i'm more concerned with malware, or stuff that messes with the computer.
Informative article and discussion....recently, I've had problems accessing Haloscan comments on some sites (Shakespeare's Sister, FireDogLake, and others) but not on other sites that have Haloscan. I thought maybe it might be a cookie problem, but I can't figure it out. I can't even read comments, nevermind commenting myself. I read on Crooks and Liars one day that they were having problems with Haloscan banning some people for no reason, so maybe it is a "Haloscan spam filter" mishap. And that reminds me of all the "Downing St Memos" emails that were tagged as spam by (if memory serves me) Comcast months ago
Hey DW...Crooks and Liars has a link to this article...COOL !!!!!!
Good evening, elf.
Crooks and Liars?! What would I do without you people?
The Dark Wraith really needs to get out more often.
Good evening, zencomix.
HaloScan has been truly weirding me out lately. There are some sites where, if I use certain words in my comments, the system just swallows the comments as soon as I click "Publish." I thought I was just being paranoid, but I ran a test comment twice just to see, and the comment vanished both times. Now, this doesn't happen on some blogs that use HaloScan, but it definitely does on other blogs.
Let's talk about what's happening with your experience with HaloScan. It could be that you've ended up in what's called a ".htaccess" bad-boy listing. I don't know for sure. The one thing you'll probably need to do is to make sure it's not something that's just slipped in on your end (which can happen for a number of reasons, one of which is when a malevolent script tries to load but fails, causing all kinds of havoc in its wreckage. First clear out your Internet cache, and be sure to use the START→ACCESSORIES→SYSTEM TOOLS→DISK CLEANUP to do some tidying around the place. (That's a standard piece of advice that probably won't do much good in your case, but it's a good habit to get into, anyway.)
The next thing is to assume that something is going wrong in the HaloScan javascript that executes when you click the "Comments" button. Are you using the native javascript on your machine, or have you changed it? Even if HaloScan is actually doing some kind of random banning, you might want to try doing something that alters the environment of your browser as it interacts with Websites that have scripts.
If you recognize the Sun Java site, you've probably already been there and taken care of your runtime environment, so that wouldn't be an issue.
The bad thing is that, if you're being tagged by your IP address, you'll have to thwart that by going to another machine to see if you can get in, or you can try on your regular machine to go through a proxy server to see if you can get the comments to come up. If you can get comments to work and you can post your own comments by going through a proxy, then you'll know for sure that you've been banned by a tag in the .htaccess on your IP address.
Another trick you could try is to use the "Comments" facility from a browser different from your regular one. This would change the environment in which you're interacting with HaloScan. If you typically use Internet Explorer, try Firefox; and if you use Firefox, try Internet Explorer. I hate to say it, but in some ways Opera is a pretty robust browser when it comes to finnicky scripts of various kinds. (Opera has some serious issues, but I've been amazed at how precision-oriented the developers are about some things that no one else has gotten around to fixing yet in other browsers. These are minor issues, but it's still kind of impressive.)
Whatever happens, I'd like to know how this problem of yours proceeds: does it simply go away on its own (as some problems do); does it persist; or do you try something and it gets you around the problem? Just keep me posted if you have the time.
The Dark Wraith is thoroughly convinced that everything on the Internet is haunted, these days.
Good evening, Dread Pirate Roberts.
I need to say something about Web bugs, which are getting woefully popular. I just got a solicitation from a pretty reputable company that would like me to run their ads, but the graphic they offered had a Web bug sitting right there in the code for the ad!
I almost want to ask them if they're Internet people are on crack or something. Everyone's talking about Web bugs, now, and here all these advertisers are, throwing more and more of them out there. Don't they understand that the good spyware fence programs might not even let their ad load with the stupid Web bugs in it? Internet users don't have to know what a Web bug is to know that, if their spyware program is screaming "BAD THING!" those people are going to run like Hell from the site that set off the spyware alarms. What do those advertisers think people are going to say: "Hmm. My spyware program and my firewall are saying that this Website is going to turn my computer into Satan's Own, and I'll become a zombie slave of the undead. Well, gee, let me shut off those silly spyware and firewall programs and finish loading this site anyway."
Lord!
The Dark Wraith is sometimes amazed by how dumb marketers think people are.
Although, elf, I think I could have done without the claw that was swept across my muzzle over there at Crooks and Liars in the comments.
I usually don't expend the energy to return fire, but GAWD! when someone disses my kung fu...
The Dark Wraith must find peace, again.
I read over your blog, and i found it inquisitive, you may find My Blog interesting. My blog is just about my day to day life, as a park ranger. So please Click Here To Read My Blog
Just browse with cookies blocked by default and only allow those sites to set cookies you choose. Christ, this isn't really that difficult, and anyone who receives a cookie from a site against his or her wishes really only has him or herself to blame. You have the technology right in front of you to prevent this from happening.
Thanks for the advice,DW, and I'll try some things to see how it works out....
Thanks, Dark Wraith - for the info (which is largely over my head anyway) but mostly for the snort-inducing material.
i just have a hard time believing the bad guys could even give two farts about a crazy old mountain girl, no matter how pissed she gets about the current state of the world, you know?
sorry i've been out of the loop recently, too. have missed y'all. happy new year!
DW,
I happened upon your comment over at C&L and feel you left a wonderful recipe for her to attempt to bake. LOL
I had no clue what you were talking about but enjoyed it nonetheless.
well, I clicked on a link to comments that was in a post at Shakes Sis, and I was able to access comments from there, and then magically, I was able to access the comments from the comment button after that. I'm also able to access comments from a computer at the library.when I get the pop-up window for haloscan at the library, it has my name,email, and homepage filled in in the spaces at the bottom. The haloscan cookie is connected to accessing the Shakes Sis website from my blog, and not a specific computer?
Good afternoon, zencomix.
You've had one of those "WTF Events" so famous among long-time users of computers.
My best estimate of what happened, if I am understanding the chain of circumstances properly, is that you had some kind of a block to comments that had occurred at some time in the past. Those kinds of things are nasty because, once they happen, it's like they persist and the browser/computer can't get over it. This same thing happened to OddJob here awhile back: a link here to Shakespeare's Sister failed, and then, for the longest time afterwards, no link here to Shakespeare's Sister would work for him. They'd work other places, but not here. It's weird, but it's not that uncommon.
What you did was to enter from a different gateway that got your machine over the hurdle. The cookie then got set properly, and you're on your way.
Now, again if I understand you properly, you say that, when you go to the library, there's a computer there that, when you click on a HaloScan link, the form in the HaloScan screen is already filled in with your information. If that's the case, that's a problem: the HaloScan cookie is persistent, but you don't want that cookie (which is what's filling in that HaloScan form with your information) staying on a foreign computer: anyone could use that computer and post under your information. You need to delete that cookie when your session on that computer is over.
Until recently, at least some public computers had a "deep freeze" routine that ran every night: all information that was not from the "administrator" level was wiped out. The reason was that, otherwise, those public computers would get filled up with files people had saved, cookies, and other junk. Those deep freeze routines aren't popular now because it takes away the ability (actually, it just makes it a little harder) of the feds to go into those public computers to see what users were doing.
Now, to your last question. I've never taken the time to really look at the HaloScan routine to see what it's up to, but it wouldn't surprise me if the cookie has entry gate information in it. I don't know how sophisticated HaloScan is (it looks very simple, but that might be deceptive), but it might be running some kind of MySQL that tags access to IP, to entry gate, and to other features. If you click on the HaloScan link on a blog, look in the bottom left-hand corner of your browser. In the white area, you'll see that you're actually initiating a javascript routine. The character string you see in that left-hand corner will have an ID tag for the script, which is associated with both the blog and with particular post on the blog. That number in there could also be carrying more information, but I just don't know. I'd have to look at the script to see what particular arguments are being set in and called from the cookie.
I suppose at some point, in one of my Coding Hack's Corner posts, I should show people how to bake cookies. Once you get the hang of it, they're fun, and they can be used for all kinds of things, some quite useful and some pretty annoying. Eventually, I'm going to have to bite the ol' bullet and build a cookie that will set users' preferences for how this blog looks. In other words, I'll give users the option of selecting an alternate look for everything, and if a given user chooses the alternative, a cookie is set that will call that theme instead of the default one whenever that user comes here. The cookie isn't hard at all; it's building the entirety of an alternate theme that's the real chew.
I need to stop babbling now, zencomix. My fingers are tiring, and I'm pretty sure I've already put you beyond the "I care" point.
The Dark Wraith retires to the den with his cookie recipes book.
Valarie plame was not a spy.