this post was submitted on 28 Aug 2024
2275 points (99.3% liked)
Technology
59288 readers
4784 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Forgive me if this is an overly simplistic view but if the ads with cookies are all served on Google's platform say then would all those ads have access to the Google cookie jar?
If they don't now then you can bet they are working on just that.
The way I'm reading it, they allow the third party cookies to be used within the actual site you're on for analytics, but prevent them from being accessed by that third party on other sites.
But I just looked at the linked article's explanation, and not a technical deep dive.
So that's what third party cookies are. What this does is make it so that when you go to example.com and you get a Google cookie, that cookie is only associated with example.com, and your random.org Google cookie will be specific to that site.
A site will be able to use Google to track how you use their site, which is a fine and valid thing, but they or Google don't get to see how you use a different site. (Google doesn't actually share specifics, but they can see stuff like "behavior on one site led to sale on the other")
We'll have to see what happens but what you are talking about is what Mozilla calls Third-Party Cookies and... they are aware of it.
https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection#:~:text=Third%2Dparty%20cookies%20are%20cookies,considered%20a%20third%2Dparty%20cookie.
I can't entirely tell if that means they will be put in the facebook cookie jar or if it will be put in the TentaclePorn Dot Org (don't go there, it is probably a real site and probably horrifying) cookie jar. If the former? Then only facebook themselves have that which... is still a lot better I guess? If the latter then that is basically exactly what we all want but a lot of sites are gonna break (par for the course with Firefox but...).
It's registered through namecheap and points to cloudflare, but there's nothing behind cloudflare. It just times out. That was disappointing.
The cookie would go to the Facebook or tentacleporn cookie jar depending on which site the user has actually visited. Whatever the domain in the address bar says.
InB4 the guy who replies to defend tenticle porn.....
They are usually separate things. Cookies are produced/saved locally, to be read in the next visit (by the same website or maany websites basically forever unless you use firefox containers or at least clear them once in a while). There's also local storage which is different but can also be used to identify you across the web. Ads, trackers, all of these categories are often made of many small components: you read a single article on a "modern" newspaper website, hundreds of connection are being made, different tiny scripts or icons or images are being downloaded (usually from different subdomains for different purposes but there's no hard rule). It's possible to block one thing and not another. For example I can block Google Analytics (googletagmanager) which is a tracker, but accept all of Google's cookies.