moakakala

3 ms·

1.
by moakakala 13y ago
I think the site/service is pretty slick and well-made. It worked well for me -- I'd be curious to see what kinds of boxes these people failing were drawing (or whether it's just a browser issue for them or something). These
2.
by moakakala 13y ago
You've advised "get a client" and "people will ask to hire you," but that only works if people are already aware of you. What if you are unknown? Where do you find these people people who will ask to hire you?
3.
by moakakala 13y ago
I don't think he's planning to start a foundation, he's donating to existing ones, like the against malaria foundation.
4.
by moakakala 13y ago
> If you want to save the world, save the world first. > Stop. Fucking. Waiting. I don't understand what you're suggesting. Is Trigg (the programmer who joined Wall Street) "waiting"? What does "not waiting" look like?
5.
by moakakala 13y ago
He probably also doesn't know how to use a sliderule or churn butter.
6.
by moakakala 13y ago
Is the risk any greater with APIs (like described in the article) compared to typical username/password login systems?
7.
by moakakala 13y ago
>Also, out of curiosity, in his timing attack example, the difference in time caused by the string being equal seems like it'd get absolutely swallowed up by the random nature of the universe - do those things actually work in the real
8.
by moakakala 13y ago
> This means that as long as you have one example of a signed message, you can forge signatures for that message plus any arbitrary request parameters you like and they will authenticate under the above described scheme. If all requests