technoguyrob

Joined 18 years ago

Karma
28
Submissions
302
Member since
Feb 24
http://therobert.org

technoguyrob @ [letter before h]mail (math\.uic\.edu)\/~(robertk) -> $2 @ $1

View on Hacker News

Recent submissions

Comment · 16 years ago
Could be an easy Putnam problem.
Comment · 18 years ago
Bookmarked this HN page for later so I can make the obvious joke about this article.
Comment · 18 years ago
I'd like to live for a time, sure, but even five hundred years might be too long. I'd either get driven insane by the constant bow-shocks of ever advancing culture, or I'd lapse into some kind of boredom-induced stupor.

It's not wrong either for the rest of us to be curious.

Comment · 18 years ago
..............

........................

I thought David was kidding. Jesus.

Comment · 18 years ago
Centralization. (OpenID)
Comment · 18 years ago
Indeed. The title should have appended: "...dramatically."
Comment · 18 years ago
What if your business partner dies? I thought everyone needs to confirm you are dead? What if they are dead?
Comment · 18 years ago
Sing this out loud in a low voice...awesome.
Comment · 18 years ago
The same key can be used for each session...when the Gmail page is being generated, I am saying this embedded in-line key can be associated TO the user's cookie, so that there is a one-to-one correspondence between this "Javascript cookie/session variable" and the user's actual cookie. There is no problem whatsoever. The only thing to be done is the exact same authentication that Google has to do to determine from which authenticated user chat requests are coming from (or any other AJAX request sent to Gmail).

EDIT: To answer your question of "are they doing some kind of lookup for each AJAX request?" Well of course, since they already have to look up a user's ID, account information, etc. based on the cookie they send.

Comment · 18 years ago
And the Gmail engineers should add an opt-out "high security" mode that checks the referer to make sure the form submission is coming from Gmail itself and not some outside website. This way people who like to use custom/blank referers can ignore this security concern if they want, and all the rest of us can prevent the risk of this problem.

EDIT: Or how about just adding an in-line Javascript variable? Say, on all Gmail pages, you could embed this in the page:

   <script>var SECURITY_KEY = "918028cd79a5ba47e83e6ba68d036ca3";</script>
And then when sending AJAX or form requests in the background, make sure to include that as a request parameter. That way, even if the user has the right authentication cookies, external websites won't be able to fool Gmail into thinking they are Gmail.

Really, this doesn't seem like a very hard problem to solve...couple lines of code...

Comment · 18 years ago
Reading that article made me expect a future in which a musician will not be known for a particular composition, but for the algorithm he devised for creating music of a particular flavor.

This only goes to show that eventually, all fields of knowledge will be nothing except mathematics!

Comment · 18 years ago
Hahahaha, I like the profile update.
Comment · 18 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton