This is for all the crypto-newbies out there like myself:
If we are to believe that Poe was lazy about the writing of the cipher, then we might also believe that Poe was lazy about the encryption schema aswell. In such case we may find that an successful cryptanalysis must also involve an examination of the process used to actually WRITE the cipher on a piece of paper... How would Poe have had to write this cipher down? How would he have done the type-setting?
This involves more careful thought and use of the more arcane tools of cryptanalysis. I was a big fan of Brute force until I used it to try and crack a 500 year old cipher (the Vigenere). The Kasiski test yeilded a key word of 6... the key space was 2 to the 26th... the execution time was 3 days... the result was garbage. (reason: I was using the Mutual Index of Coincidence of English to tell me if I cracked the cipher)
Perhaps my code was just buggy.
The point is: How do you Brute Force something you know nothing about... and How do you know if your answer is "Correct"?
in example Here is a cipher:
KWAKOGCMADSGJRCEANAFAESEAPVWPW
what's the decryption? Not a lot to go on is it? Perhaps Poe's cipher isn't insoluable, we just don't have enough to go on.
Last Year my Advanced Computer Graphics project was on the ImmersaDesk, here at University of Alaska it's sort of a half-a-CAVE. The ImmersaDesk uses the same set of CAVE-libs that the cave does, it's just 1/6th the price.
The biggest problem I had developing on the CAVE was the UI. It uses a wand and head tracker to get your position in space. But I found that my gestures were very limited and that using 'head woggle' for judging a user's perspective in 3d was a bit clumsy.
I also found that after more than 3 hours in the CAVE I'd have massive headaches due to the LCD shuttering action and low light.
Yes, the CAVE has a way to go.
-// Zarf//
Re:A catastrophe in slow motion...
on
Apocalypse Not
·
· Score: 1
That's really an enlightened view.
What you are saying is that the 2 views of the y2k bug are like the difference between a blow-out and a slow flat... they are both problems that need to be fixed, one causes a car wreck, the other causes me to be late to work.
The y2k bug is therefore the slow leak, I still need to fix it... but I'm not going to get blown off the road by it.
Similarly, if I have a mudslide that slides at 1 tonne a day... we still need a bull dozer to protect my house! Over time the slide will bury my home (if I'm below the slide) it's not necessary to evacuate the house per se, but, we will still need to do some work to save the house before the mud piles up over the roof.
So what happened with the y2k bug fizzle is the media was expecting the tire to blow out or the mud slide to streak down the hill, instead, we've been seeing and will see a bunch of small slides or little leaks. All of which need to be fixed... but aren't life and death situations.
I'll try to keep this in mind when the power company bills me twice or I get a check that bounces because somewhere some system says I didn't redeem it with in 120 days.
So the "measly two bytes" they saved paid for a decent dinner out.
This is a very good point. Currently I am re-writing some PERL code to use a C routine inorder to save a measly 36MB (I could elaborate on the way the program consumes memory but I don't feel like it). On some systems that I've written for 36MB is close to meaningless (Immersadesk & O2)... but on this project I've got to execute inside 17MB. The cost for more RAM outweights the need for portability in the PERL code. The difference in cost in hardware pays for a nicer workstation for another programmer, or better hardware on another project.
So it's not that I'm a short-sighted programmer, I designed initially for maximum portability and adaptability... the problem with that is it costs too much to execute that design on large data sets. The solution is to write a version of the code that does intensive memory management but is less portable and may break more easily.
I saw the congress woman from NewYork address Bill Gates on the virtues of Silicone Valley and mentioned NY's Silicone Alley on C-Span a while ago. She sounded like she could use some silicone removal herself. Perhaps she was thinking of implanted chips or chip implants.
All-in-all I wouldn't be too upset that D.C.-ites don't get the internet... it's probably better that way. The internet culture will be better off if the law-makers just have to react to it rather than having control over it's growth.
It would be most likely that the Meta-Language would only be able to handle a small subset of the meanings available in any of it's natural language counter-parts. The subset of "Meta-meanings" would be the set of all common meanings between all the languages.
Ideas like run, walk, buy, sell, ect. would easily translate... however things like "glark", "glob", "grep" may not translate accurately. That is the 6 russian verb forms you mentioned may all be mapped directly to only 3 verbal meanings.
ie: grep to look, glob to list, and glark to understand... and so on.
The resulting word elements could then be arranged by a simple pattern-matching AI into an acceptable form. The result is a valid natural-language sentance which has some shadow of the original meaning. In practice this could allow for useful bussiness communication but prevent discussions of abstract ideas.
Yet another fine example of how problem-domain-"scoping" affects over-all software functionality.
I just read this to my wife who is a Social Worker and gives various Human Resources Seminars, she said: "They could use a Social Worker!"... She's formulating a communication-skills workshop for Rocket Scientists.
I just find it amazing that someone who used to program is actually that ignorant of his computer that he had to check what kind of mouse he has.
I am also upset that he is using Caldera 1.3 and not 2.3 if he's checking out the Linux scene using Caldera 1.3... that's like saying... I wanna check out that internet thing so I'm getting MSIE 2.0!
Afterward I can hear them complain... ugh! the internet stinks... it keeps crashing!
Slashdot Mirror
This is for all the crypto-newbies out there like myself:
// Zarf //
If we are to believe that Poe was lazy about the writing of the cipher, then we might also believe that Poe was lazy about the encryption schema aswell. In such case we may find that an successful cryptanalysis must also involve an examination of the process used to actually WRITE the cipher on a piece of paper... How would Poe have had to write this cipher down? How would he have done the type-setting?
This involves more careful thought and use of the more arcane tools of cryptanalysis. I was a big fan of Brute force until I used it to try and crack a 500 year old cipher (the Vigenere). The Kasiski test yeilded a key word of 6... the key space was 2 to the 26th... the execution time was 3 days... the result was garbage. (reason: I was using the Mutual Index of Coincidence of English to tell me if I cracked the cipher)
Perhaps my code was just buggy.
The point is: How do you Brute Force something you know nothing about... and How do you know if your answer is "Correct"?
in example Here is a cipher:
KWAKOGCMADSGJRCEANAFAESEAPVWPW
what's the decryption? Not a lot to go on is it? Perhaps Poe's cipher isn't insoluable, we just don't have enough to go on.
-
Last Year my Advanced Computer Graphics project was on the ImmersaDesk, here at University of Alaska it's sort of a half-a-CAVE. The ImmersaDesk uses the same set of CAVE-libs that the cave does, it's just 1/6th the price.
// Zarf //
The biggest problem I had developing on the CAVE was the UI. It uses a wand and head tracker to get your position in space. But I found that my gestures were very limited and that using 'head woggle' for judging a user's perspective in 3d was a bit clumsy.
I also found that after more than 3 hours in the CAVE I'd have massive headaches due to the LCD shuttering action and low light.
Yes, the CAVE has a way to go.
-
That's really an enlightened view.
// Zarf //
What you are saying is that the 2 views of the y2k bug are like the difference between a blow-out and a slow flat... they are both problems that need to be fixed, one causes a car wreck, the other causes me to be late to work.
The y2k bug is therefore the slow leak, I still need to fix it... but I'm not going to get blown off the road by it.
Similarly, if I have a mudslide that slides at 1 tonne a day... we still need a bull dozer to protect my house! Over time the slide will bury my home (if I'm below the slide) it's not necessary to evacuate the house per se, but, we will still need to do some work to save the house before the mud piles up over the roof.
So what happened with the y2k bug fizzle is the media was expecting the tire to blow out or the mud slide to streak down the hill, instead, we've been seeing and will see a bunch of small slides or little leaks. All of which need to be fixed... but aren't life and death situations.
I'll try to keep this in mind when the power company bills me twice or I get a check that bounces because somewhere some system says I didn't redeem it with in 120 days.
-
So the "measly two bytes" they saved paid for a decent dinner out.
This is a very good point. Currently I am re-writing some PERL code to use a C routine inorder to save a measly 36MB (I could elaborate on the way the program consumes memory but I don't feel like it). On some systems that I've written for 36MB is close to meaningless (Immersadesk & O2)... but on this project I've got to execute inside 17MB. The cost for more RAM outweights the need for portability in the PERL code. The difference in cost in hardware pays for a nicer workstation for another programmer, or better hardware on another project.
So it's not that I'm a short-sighted programmer, I designed initially for maximum portability and adaptability... the problem with that is it costs too much to execute that design on large data sets. The solution is to write a version of the code that does intensive memory management but is less portable and may break more easily.
-
Considering that they are all iMac's, they're all most likely praying ... God PLEEZE don't let me crash while anyone is looking!!!
// Zarf //
-
I saw the congress woman from NewYork address Bill Gates on the virtues of Silicone Valley and mentioned NY's Silicone Alley on C-Span a while ago. She sounded like she could use some silicone removal herself. Perhaps she was thinking of implanted chips or chip implants.
// Zarf //
All-in-all I wouldn't be too upset that D.C.-ites don't get the internet... it's probably better that way. The internet culture will be better off if the law-makers just have to react to it rather than having control over it's growth.
-
I've posted this before and I'll post it again!
// Zarf //
Caffine is: The Mind Enhancing Drug !!!
-
It would be most likely that the Meta-Language would only be able to handle a small subset of the meanings available in any of it's natural language counter-parts. The subset of "Meta-meanings" would be the set of all common meanings between all the languages.
// Zarf //
Ideas like run, walk, buy, sell, ect. would easily translate... however things like "glark", "glob", "grep" may not translate accurately. That is the 6 russian verb forms you mentioned may all be mapped directly to only 3 verbal meanings.
ie: grep to look, glob to list, and glark to understand... and so on.
The resulting word elements could then be arranged by a simple pattern-matching AI into an acceptable form. The result is a valid natural-language sentance which has some shadow of the original meaning. In practice this could allow for useful bussiness communication but prevent discussions of abstract ideas.
Yet another fine example of how problem-domain-"scoping" affects over-all software functionality.
-
I just read this to my wife who is a Social Worker and gives various Human Resources Seminars, she said: "They could use a Social Worker!" ... She's formulating a communication-skills workshop for Rocket Scientists.
// Zarf //
-
I just find it amazing that someone who used to program is actually that ignorant of his computer that he had to check what kind of mouse he has.
... that's like saying... I wanna check out that internet thing so I'm getting MSIE 2.0!
I am also upset that he is using Caldera 1.3 and not 2.3 if he's checking out the Linux scene using Caldera 1.3
Afterward I can hear them complain... ugh! the internet stinks... it keeps crashing!