Re:Firefox rolls out Total Cookie Protection by default to a...
by PaulDavisThe1st on Tuesday June 14, 2022 @01:36PM
(#31742998)
> And no one saw the privacy invading potential at the time.
Maybe not the privacy invasion potential but ... As we got started building amzn in the fall of 94, it was a no-brainer decision to not use cookies even though they were just arriving. The controversy around the idea was intense and it was far from clear that they would be a success as a technology. It is likely true that there was more attention being paid to the "what? it lets a remote server create a file on my driver?" angle than the privacy one.
Re:Firefox rolls out Total Cookie Protection by default to a...
by shubhamkrm on Tuesday June 14, 2022 @02:04PM
(#31743413)
How did you manage session information without using cookies?
Re:Firefox rolls out Total Cookie Protection by default to a...
by PaulDavisThe1st on Tuesday June 14, 2022 @03:03PM
(#31744374)
http://yourdomain.com/path/to/something?SESSION=af2828c119ae1
and yes, all URLs in every page were rewritten during page generation to include the session ID.
Re:Firefox rolls out Total Cookie Protection by default to a...
by marshray on Tuesday June 14, 2022 @03:45PM
(#31745007)
Didn't that break bookmarks?
Re:Firefox rolls out Total Cookie Protection by default to a...
by jeltz on Wednesday June 15, 2022 @12:11AM
(#31749027)
Sometimes, but usually not. What it did enable was people accidentally leaking their sessions when sharing links.
Re:Firefox rolls out Total Cookie Protection by default to a...
by leaflets2 on Wednesday June 15, 2022 @04:19PM
(#31758904)
What did the company do then? (When their users started accidentally leaking session IDs)
(Hmm but you're a different person :-))
Re:Firefox rolls out Total Cookie Protection by default to a...
by PaulDavisThe1st on Tuesday June 14, 2022 @05:31PM
(#31746336)
This was 1994. Web technology was barely even emergent.
[1] https://en.wikipedia.org/wiki/Browser_cookie#History