Should The Governing Body Take A Good Look At Their Cookies And See Where People Are Going Before They Dine At The Y(JW.Org)?

by frankiespeakin 7 Replies latest watchtower beliefs

• 

  frankiespeakin

  When people visit their site they leave a cookie foot print. The Governing Body as dutiful CEOs need to examine this bit of information closely so as to see where these visitors have been before comming to their site. They need to find out what apostate sites they are visiting. I'm sure JWD cookies are being collected in big numbers as well as many other sites.

  In fighting a battle one needs to gather intelligence and cookies are important.

  True this over the hill gang of CEOs may be in denial, but sooner or latter they have got to pay the piper.
• 

  frankiespeakin

  So we send them a message by posting their site to click on and giveing them a pile of cookies when you do.

  http://www.jw.org/en/bible-teachings/questions/science-and-the-bible/
• 

  Dis-Member

  Not sure what you know about website cookies but that cookie is not an entire history of everywhere you have been on the net.

  A cookie's contents are determined by the specific website that created that cookie. Contents vary from site to site. As a general rule, cookies contain random alphanumeric text characters.

  Cookies are intended to help you access a site faster and more efficiently. For example, cookies can store information to help you enter a site without having to login. In effect, cookies tell the website that your browser has been to the site before. It does not need to know your exact identity.

  When created, cookies normally don't contain any personal information. They don't scan your computer or do any kind of investigation to find out your personal information. Any personal information they might contain is a result of your own input on a website's form. Most of the time, when a cookie does store personal information, this information is coded in such a way that it is unreadable to any third party who happens to access your cookie folder. The only computer that can read and decode the information is the server that created the cookie in the first place.

  In addition to encrypting any information stored in cookies, some websites add extra layers of security to browsers' cookie handling processes: store only anonymous but unique content on local cookies; or store personal information on the website's server and make it accessible only by matching with it the anonymous cookie stored on your computer.

  This depends on how a website has set up its cookie feature, but generally the content of a cookie is a randomly generated set of characters. For most purposes a website sending a cookie does not need to know who you are - it just needs to remember that it has seen your browser before.

  Some websites do write personal information about you into a cookie, but this is only possible if you have provided them with the information in the first place. If personal information is stored in a cookie it is usually encrypted - coded - so that any third party who has access to the cookie folder of your browser cannot read it.

  Some website servers use a combination of methods: on your browser they may create a cookie with unique but anonymous content; or on the server side they may create a file that logs that unique but anonymous content alongside any personal information that you have provided.
  
  What can't cookies do?

  Cookies are plain text files. They are not compiled so they cannot execute functions or make copies of themselves. They cannot browse through or scan your computer or otherwise snoop on you or dig for private information on your hard disk.

  Cookies have a very limited function: to help your browser deliver the full features designed into many of today's websites. These features include smooth login, preference settings, themes, shopping carts, and many other features. Cookies cannot scan or retrieve your personal information.

  Because cookies are just harmless files, or keys, they cannot look into your computer and find out information about you, your family, or read any material kept on your hard-drive. Cookies simply unlock a computer's memory and allow a website to recognise users when they return to a site by opening doors to different content or services. It is technically impossible for cookies to read personal information.
• 

  Phizzy

  Thank you DM for that info. I was a bit worried before reading it, not about the JW Thought Police finding out about me, they really don't worry me anymore, stupid twats, but I was a little concerned generally about Cookies, so you have allayed my fears.

  I am now a calmer Techno-phobe.
• 

  frankiespeakin

  Thanks for the cookie low down.

  http://en.wikipedia.org/wiki/HTTP_cookie

  Although cookies cannot carry viruses, and cannot install malware on the host computer, [2] tracking cookies and especially third-party tracking cookies are commonly used as ways to compile long-term records of individuals' browsing histories—a potential privacy concern that prompted European [3] and U.S. law makers to take action in 2011. [4] [5] Cookies can also store passwords and form content a user has previously entered, such as a credit card number or an address. When a user accesses a website with a cookie function for the first time, a cookie is sent from server to the browser and stored with the browser in the local computer. Later when that user goes back to the same website, the website will recognize the user because of the stored cookie with the user's information. [6]

  Other kinds of cookies perform essential functions in the modern web. Perhaps most importantly, authentication cookies are the most common method used by web servers to know whether the user is logged in or not, and which account they are logged in with. Without such a mechanism, the site would not know whether to send a page containing sensitive information, or require the user to authenticate themselves by logging in. The security of an authentication cookie generally depends on the security of the issuing website and the user's web browser, and on whether the cookie data is encrypted. Security vulnerabilities may allow a cookie's data to be read by a hacker, used to gain access to user data, or used to gain access (with the user's credentials) to the website to which the cookie belongs (see cross-site scripting and cross-site request forgery for examples). [7]

  First-party cookies are cookies that belong to the same domain that is shown in the browser's address bar (or that belong to the sub domain of the domain in the address bar). Third-party cookies are cookies that belong to domains different from the one shown in the address bar. Web pages can feature content from third-party domains (such as banner ads), which opens up the potential for tracking the user's browsing history. Privacy setting options in most modern browsers allow the blocking of third-party tracking cookies.

  As an example, suppose a user visits www.example1.com . This web site contains an advert from ad.foxytracking.com , which, when downloaded, sets a cookie belonging to the advert's domain ( ad.foxytracking.com ). Then, the user visits another website, www.example2.com , which also contains an advert from ad.foxytracking.com , and which also sets a cookie belonging to that domain ( ad.foxytracking.com ). Eventually, both of these cookies will be sent to the advertiser when loading their ads or visiting their website. The advertiser can then use these cookies to build up a browsing history of the user across all the websites that have ads from this advertiser.

  Tracking

  Tracking cookies may be used to track internet users' web browsing. This can also be done in part by using the IP address of the computer requesting the page or the referrer field of the HTTP request header, but cookies allow for greater precision. This can be demonstrated as follows:

  1. If the user requests a page of the site, but the request contains no cookie, the server presumes that this is the first page visited by the user; the server creates a random string and sends it as a cookie back to the browser together with the requested page;
  2. From this point on, the cookie will automatically be sent by the browser to the server every time a new page from the site is requested; the server sends the page as usual, but also stores the URL of the requested page, the date/time of the request, and the cookie in a log file.

  By analyzing the log file collected in the process, it is then possible to find out which pages the user has visited, in what sequence, and for how long.
• 

  frankiespeakin

  Any way I don't think the Watchtower Corporation will send the elders after anybody if the read their third party cookies and find out that they have been to an appostate site. The repercusions would be too great if they formed committees because appostate site tracking cookies were in their browser.
• 

  RichardHaley

  Your biggest risk would be a friend/family member looking over your sholder/checking your browsing history (ctl+h keys) and then gossiping/reporting what you are doing. Clearing browsing history and/or using incognito mode will protect you from most of this threat.
• 

  compound complex

  I stopped using the public library pc, when mine was down, after some loud and chatty lady looking over my shoulder began jabbering away about what I was reading here.

  No manners.

  CC