Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But that has nothing to do with "cookies" at all. You could in principle implement purchasing using client-side javascript without any cookies, as long as you don't care that the customer's shopping cart disappears if they close their tab, and when the customer sends their purchase information you'd still have all their personal info even if you didn't use any cookies.

Meanwhile the actual problem with (third party) cookies is that they're used to correlate users across multiple sites for tracking purposes, which goes away when browsers stop accepting third party cookies by default.

> But consider if you buy some books or sex toys or whatever from an online store. Do you want the store to sell information about your purchases to third parties?

This is really a different problem, because how are you supposed to know if they're doing this anyway? How is the government? Once they have your information there is no real way to tell what they're doing with it if they're willing to lie to you.

So the answer is to make it so they never actually have your personal information. But for this we need some kind of anonymous digital payment system for small transactions, so that the vendor doesn't have to know who you are. If all they have is a transaction ID from a bank that lets them get paid and a virtual one-time-use PO box number you had the item shipped to which forwards to your real address for a week and then is deleted forever, they can do whatever they want with that information and you don't have to worry about it.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: