\nContinuing from yesterday’s post<\/a>, I’m talking more about cookies and possible effects of them during Internet browsing.<\/p>\n \nA cookie is a string of characters a website can load onto your computer as it delivers the content you request. Cookie loading happens invisibly. By itself, it’s harmless, since, by design, only the entity who put the cookie there can retrieve it. However, the cookie may effectively be able to transmit its presence to another site when the user lands there. Practically, the cookie is then saying, “This surfer has also been to whatever site.<\/em>“<\/p>\n How this actually works starts with a fact you may not expect: when you go to a site, many other sites may pay that one to load their cookies as well. Therefore, hypothetically speaking, at siteA.com, you may also receive cookies from siteB.com, if siteA.com has allowed siteB.com that access. In such a case, the cookies from siteB.com are called third-party cookies<\/em>, since they are from a site you didn’t actually visit.<\/p>\n Third-party cookie loading can be accomplished in a number of ways. The important concept is that, once it’s done, and then you do actually visit siteB.com, it already knows things about you. This can seem like “tracking”, although it really isn’t that siteB.com has followed you around.<\/p>\n Some sites have a wide network of other ones from which they load their own cookies as third-party ones.<\/p>\n Source:<\/p>\n us.norton.com<\/a><\/p>\nJack of Oracle Tutoring by Jack and Diane,<\/a> Campbell River, BC.\n \n","protected":false},"excerpt":{"rendered":" Self-tutoring about browsing and cookies: the tutor continues, mentioning third-party cookies. Continuing from yesterday’s post, I’m talking more about cookies and possible effects of them during Internet browsing. A cookie is a string of characters a website can load onto …<\/p>\n