• Scam Alert. Members are reminded to NOT send money to buy anything. Don't buy things remote and have it shipped - go get it yourself, pay in person, and take your equipment with you. Scammers have burned people on this forum. Urgency, secrecy, excuses, selling for friend, newish members, FUD, are RED FLAGS. A video conference call is not adequate assurance. Face to face interactions are required. Please report suspicions to the forum admins. Stay Safe - anyone can get scammed.
  • Several Regions have held meetups already, but others are being planned or are evaluating the interest. The Ontario GTA West area meetup is planned for Saturday April 26th at Greasemonkeys shop in Aylmer Ontario. If you are interested and haven’t signed up yet, click here! Arbutus has also explored interest in a Fraser Valley meetup but it seems members either missed his thread or had other plans. Let him know if you are interested in a meetup later in the year by posting here! Slowpoke is trying to pull together an Ottawa area meetup later this summer. No date has been selected yet, so let him know if you are interested here! We are not aware of any other meetups being planned this year. If you are interested in doing something in your area, let everyone know and make it happen! Meetups are a great way to make new machining friends and get hands on help in your area. Don’t be shy, sign up and come, or plan your own meetup!

My bank uses cookies, clearly spies on me like everyone else, so why the hell.....

little ol' e said:
Do you know the # of cases that are currently before the courts on these terms of use, for the services they provide?
How about the backlog of cases in the courts currently, 3-5 years out?
Click to expand...
Facebook settled a case for providing data to Cambridge Analytica. That was all about use of user data in ways that were not laid out in the Terms of Use.

Google lawsuits against Facebook or Google and you'll see how often they are plantiffs in litigation.

Professionally I have been involved in two instances. One where a company did not live up to the performance standards made in its Terms of Use and another where a company contacted me about multi-user access.
 
Cookies are not inherently bad things. The web is stateless - meaning that from one request for a resource to another request the web server does not know what state the client (mostly browser) is. Thus for logging into websites such as a bank you need to have a way to link set of requests together so server knows its a logged in user. Cookies serve this purpose nicely, through there are other ways around the problem such as sending login id in URL each time.

The problem is abuse of cookies. When using website X such website has embedded code for "Ads mega server" site in it - this "Ads mega server", if not already created, creates the tracking cookie - which has "login info". Now as you visit sites Y Z etc. they also have Ads mega server site embedded - it reads its own cookie and checks where you have been - they see site X and display ads for site X.

Cookies can store a lot more data than just session ID or some identifier - but today AFAIK they mostly do that since Database access is fast.

Frequently parent companies do not fully know what is exactly going on - i.e. developers use a lot of 3rd party stuff for websites and these 3rd party providers can be dishonest - well, I guess same way the client can pretend to be anything it feels like. A lot of cookie creation now is done automatically - i.e. developer assumes some layer somewhere actually creates a cookie. I did not create a cookie by hand in about a decade...

I find it unlikely a bank would use a tracking cookie from 3rd party site to display ads later on - I feel this is mostly for login purposes - but technically they are tracking your login... so it is a tracking cookie. You can set cookies only for duration of a session, fixed time span or never expires.

Bottom line is, cookies were "good" until people started abusing them and made them "bad".
 
Tom Kitta said:
I find it unlikely a bank would use a tracking cookie from 3rd party site
Click to expand...
BoM uses google tag manager, or at least it did when I last checked.

Nowadays all cookies have to be suspect, even the 'good' ones. 3rd parties have made it a priority to read other vendors cookies, which is why all cookies should be session cookies, deleted as soon as you close the web page. Trouble is, people leave tabs open too long, allowing tracking to a much higher degree.
 
You must log in or register to reply here.
Back
Top