technoguyrob
technoguyrob on Hacker News
Could be an easy Putnam problem.
Bookmarked this HN page for later so I can make the obvious joke about this article.
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.
..............
........................
I thought David was kidding. Jesus.
Indeed. The title should have appended: "...dramatically."
What if your business partner dies? I thought everyone needs to confirm you are dead? What if they are dead?
Sing this out loud in a low voice...awesome.
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.
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...
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!
Hahahaha, I like the profile update.
Sweet, I can now say I've been told "fuck you[r downvotes]" by a professor from Cornell.
XSS detection is not just as simple as that. For example, in IE, entering the following produces a pop-up:
<table style="background-image:url(javascript:alert(1))"><tr><td>Hi</td></tr></table>
However, read debt's comment below. XSS is irrelevant here since "XSS" means cross-site scripting, i.e., ,managing to embed Javascript into pages someone ELSE sees. Only the client sees this, it doesn't get reproduced for anyone else.
I think mediocrity is sort of the complement to laziness, in that respect. For example, settling for a cubicle job that drains you because you don't think you can do anything better or don't want to--that's still "laziness" in the way you're describing.
Some people read that presentation in NOT full screen?
Maybe someone should write a "How People Really Use Slideshare" post...
I am a mathematics student and sometimes need to look up papers. A lot of these papers are in journals not available online and have references to more of such papers. This can sometimes make even understanding a relatively simple proof that could be explain in a book in a few pages a gruesome all-day ordeal where 3/4th of the time is spent looking up references.
It would be really freaking cool if Google (Scholar?) could scan these articles into PDFs, then attempt to OCR the references and see if Google has indexed those, then embed hyperlinks to the references. This is technically feasible, and I imagine it would really make a lot of researchers very happy.
Posted by
technoguyrob on Friday October 31, 2008 @06:08AM
from the self-post dept.
I am working on an application that might touch some legal gray areas in occasional circumstances.I usually skip any Terms & Conditions for 99% of the stuff I sign up for on the web. There are three reasons for this:1. They are hard to read, as they are usually a list of clauses and subclauses in legal terms.2. I don't have the time, usually it's something small like a forum account or...
Oh wow, learn something new each day, huh...
Posted by
technoguyrob on Thursday October 30, 2008 @03:52PM
from the akropolix.net dept.
"Account balances as of 31 October 2008:"
But it's the 30th today....
And with the recent discovery that graphene nanoribbons may be able to replace silicon as the semiconductor in processors at least one researcher predicts that clock speeds in the terahertz range may be possible.[1]
Has anyone ever heard of this or have enough technical background to expound? I am really curious.
Either way, I suppose it is far off, certainly not any time soon.
[1] http://en.wikipedia.org/wiki/Clock_speed
With the history of unusual ways things have been discovered in science, I'm not sure if that is sarcasm.