Personally, I'd rather not have the built in scripting language for my cryptocurrency be turing complete. Enjoy blindly executing...whatever comes across your blockchain.
You mean click 10 times to see the top 10 gadgets?
To be fair, there are 11 pages counting the intro "slide."
So we have about 19 missing clicks to account for.
Ok, well everytime you click to the next page you have to scroll down again to see the navigation, at least I do at 1280x1024. So that's 3 down mouse wheel "clicks" per page, so 11x3+11=44 clicks, shit too many!
Ok I guess I can just hit Page Down instead of mouse wheeling, for the sake of argument we'll count that as a click as it is replacing a click function. That yields us 11+11=22 clicks...still short!
Fine I relent, there aren't 30 logical clicks in there, taco was lying. Unless taco is one of those people who has to select their browser text to read it, as if it might come flying off if it weren't held down by your highlight color. In that case you could easily fill up 30 clicks!
After reviewing the OpenID RFC I was a little dissapointed to see that messages are signed with SHA1, or SHA256 (if supported.)
To me, this suggests that the majority of OpenID supported sites/providers use SHA1, of which rainbow tables have been available for some time. I think with this in mind, man in the middle becomes a legitamate attack vector, so if I can man in the middle you to determine your MAC, then I can impersonate you on any OpenID supported site?
Yea where can I sign up for _this_, and should I use my SSN as my MAC key?
Buddy of mine was headed home after Christmas this year, and I guess he brought some antique drinking glasses with him. The X-Rays were apparently inconclusive, and after repeatedly tripping the metal detector (I guess walking through the metal detector with the non X-Ray(able) item is the general TSA fallback procedure?) they finally had to call a TSA super to properly inspect the nefarious drinkware.
So as he's back at the metal detector just trying to get through the nightmare of holiday travel, he decides to give them a friendly piece of information:
I guess shouting "It's just leaded crystal!" sounds a lot like "It's just a loaded pistol!", what with all the background holiday commotion.
Sufficed to say my friend had a few automatic weapons pointed at him momentarily, but after the confusion was sorted out they let him through.
Encryption implies that you can reconstruct the original string from the encoded. Methods like md5, sha1, etc are one way algorithms that cannot be reversed* in a realistic amount of time.
Jive Lady: Oh stewardess! I speak jive. Randy: Oh, good. Jive Lady: He said that he's in great pain and he wants to know if you can help him. Randy: All right. Would you tell him to just relax and I'll be back as soon as I can with some medicine? Jive Lady: Jus' hang loose, blood. She gonna catch ya up on da' rebound on da' med side. Second Jive Dude: What it is, big mama? My mama no raise no dummies. I dug her rap! Jive Lady: Cut me some slack, Jack! Chump don' want no help, chump don't GET da' help! First Jive Dude: Say 'e can't hang, say seven up! Jive Lady: Jive ass dude don't got no brains anyhow! Hmmph!
A few months ago I developed a checkout system that used a number of payment options, I found google checkout to be the most complicated and the slowest when compared to paypals array of payment processing options (payflow pro, etc) or other merchant account setups.
Google checkout was the only processor (that I used) that had a distributed processing engine. Unlike say paypal where you execute a POST request and the response code comes back in the same transaction, google is more "fire and wait for a callback", you setup a callback URL to process the google checkout responses, then you start submitting your XML shopping carts and...just...wait...for...8...XML...transactions.. .to...finish.
I'm not blaming XML here mind you, but after the user hits "submit" with their credit card information it takes 8 requests to fully process, and in the case of AMEX that timeframe is usually 30 minutes to an hour(ouch!) Compare at paypal which I've never seen take longer than 2 minutes, or a merchant account setup which takes 1-5 seconds.
This may be OK if you sell an actual product as the consumer is accustom to waiting a few days for their package to ship/arrive, however it is quite unacceptable when say, selling a service where most users are used to seeing (almost) immediate responses.
Also (at the time of my development) you cannot remove the shipping protocols out of the transaction, google requires you to acknowledge that yes in fact your order has shipped, even if there is no shipping of a product (very confusing for users when they receive a "your order has shipped!" email.)
As for the project I was working on, the clients decided google was too slow, they ended up dropping them as a payment option even though they had better rates than paypal.
Slashdot Mirror
I don't think you understand how bitcoin works.
They also offer gigabit, conference rooms, free coffee and beer, etc.
Like that pesky cap on mining, inflation forever!
Personally, I'd rather not have the built in scripting language for my cryptocurrency be turing complete. Enjoy blindly executing...whatever comes across your blockchain.
That's good
The Frogurt is also cursed.
The cpu "cooler." The misspellings on the box. This was fraud.
Are you sure?
if i had a mod point, you would get it
shocking that P & GP posted as AC
Let's see you stuff a Macintosh 512k into your shirt pocket.
sounds like a bet to me...
To be fair, there are 11 pages counting the intro "slide."
So we have about 19 missing clicks to account for.
Ok, well everytime you click to the next page you have to scroll down again to see the navigation, at least I do at 1280x1024. So that's 3 down mouse wheel "clicks" per page, so 11x3+11=44 clicks, shit too many!
Ok I guess I can just hit Page Down instead of mouse wheeling, for the sake of argument we'll count that as a click as it is replacing a click function. That yields us 11+11=22 clicks...still short!
Fine I relent, there aren't 30 logical clicks in there, taco was lying. Unless taco is one of those people who has to select their browser text to read it, as if it might come flying off if it weren't held down by your highlight color. In that case you could easily fill up 30 clicks!
After reviewing the OpenID RFC I was a little dissapointed to see that messages are signed with SHA1, or SHA256 (if supported.)
To me, this suggests that the majority of OpenID supported sites/providers use SHA1, of which rainbow tables have been available for some time. I think with this in mind, man in the middle becomes a legitamate attack vector, so if I can man in the middle you to determine your MAC, then I can impersonate you on any OpenID supported site?
Yea where can I sign up for _this_, and should I use my SSN as my MAC key?
I thought we were better than this...one router goes down and suddenly "OMG IRAN HAS NO INTARWEBS!"
Ok, so if Iran has _no_ intarwebs, I shouldn't be able to hit a server in Tehran right?
http://www.iust.ac.ir/
Screw that.
Buddy of mine was headed home after Christmas this year, and I guess he brought some antique drinking glasses with him. The X-Rays were apparently inconclusive, and after repeatedly tripping the metal detector (I guess walking through the metal detector with the non X-Ray(able) item is the general TSA fallback procedure?) they finally had to call a TSA super to properly inspect the nefarious drinkware.
So as he's back at the metal detector just trying to get through the nightmare of holiday travel, he decides to give them a friendly piece of information:
I guess shouting "It's just leaded crystal!" sounds a lot like "It's just a loaded pistol!", what with all the background holiday commotion.
Sufficed to say my friend had a few automatic weapons pointed at him momentarily, but after the confusion was sorted out they let him through.
Shocking you would post this AC, or should I say, ES?
Bah humbug!
HAH
Someone mod parent up!
Encryption implies that you can reconstruct the original string from the encoded. Methods like md5, sha1, etc are one way algorithms that cannot be reversed* in a realistic amount of time.
* - Rainbow tables
Jive Lady: Oh stewardess! I speak jive.
Randy: Oh, good.
Jive Lady: He said that he's in great pain and he wants to know if you can help him.
Randy: All right. Would you tell him to just relax and I'll be back as soon as I can with some medicine?
Jive Lady: Jus' hang loose, blood. She gonna catch ya up on da' rebound on da' med side.
Second Jive Dude: What it is, big mama? My mama no raise no dummies. I dug her rap!
Jive Lady: Cut me some slack, Jack! Chump don' want no help, chump don't GET da' help!
First Jive Dude: Say 'e can't hang, say seven up!
Jive Lady: Jive ass dude don't got no brains anyhow! Hmmph!
Yah but who really wants to implement things like:
void randomly_BSOD_within(int seconds)
or
void set_ignore_show_clippy_preference()
I wouldn't worry, it shouldn't be too many pixels :D
A few months ago I developed a checkout system that used a number of payment options, I found google checkout to be the most complicated and the slowest when compared to paypals array of payment processing options (payflow pro, etc) or other merchant account setups.
. .to...finish.
Google checkout was the only processor (that I used) that had a distributed processing engine. Unlike say paypal where you execute a POST request and the response code comes back in the same transaction, google is more "fire and wait for a callback", you setup a callback URL to process the google checkout responses, then you start submitting your XML shopping carts and...just...wait...for...8...XML...transactions.
I'm not blaming XML here mind you, but after the user hits "submit" with their credit card information it takes 8 requests to fully process, and in the case of AMEX that timeframe is usually 30 minutes to an hour(ouch!) Compare at paypal which I've never seen take longer than 2 minutes, or a merchant account setup which takes 1-5 seconds.
This may be OK if you sell an actual product as the consumer is accustom to waiting a few days for their package to ship/arrive, however it is quite unacceptable when say, selling a service where most users are used to seeing (almost) immediate responses.
Also (at the time of my development) you cannot remove the shipping protocols out of the transaction, google requires you to acknowledge that yes in fact your order has shipped, even if there is no shipping of a product (very confusing for users when they receive a "your order has shipped!" email.)
As for the project I was working on, the clients decided google was too slow, they ended up dropping them as a payment option even though they had better rates than paypal.
1) Playback/Recording video resolution required (Standard broadcast resolution, High Definition (720i, 1040i, ....)
Ah yes, 1040i...wait...
I for one welcome our blue screen of death-ing overlords.
(Ba-dum, chink!)