I know someone will tell me it's not, because it has a real cost associated with it. It uses computer resources and bandwidth.
But guess what? There is a real cost associated with the KKK marching in DC, or giving some speeches in your hometown. There was also a very real cost when thousands of protesters showed up at the WTO meeting in Seattle.
But the real source was research doen by Joseph Campbell and documented (in a few books, but especially by) Hero of a Thosand Faces.
He basically disected the world's mythology and found certain story paradigms that existed in just about every culture known to man. You would have different characters and adventures, but the basic dramatic structure would be the same. The interesting thing is that the stories came about independantly. There's just something in the back of human's brains that makes certain stories universal.
The original Star Wars was based on the "Hero's Journey" paradigm. Lucas has acknowledged this.
Campbell is interesting reading if you get the chance, and have the inclination.
Or maybe provoke discussion, but hasn't it occurred to anyone that Dune is not a Science Fiction Book? It takes more than just being "set in the year 10,899" to be Science Fiction. The technology is incidental to the story. It's about mysticism and feudalism.
Oh yeah, and Star Wars isn't Science Fiction either.
Even a cursory examination should show that these numbers don't have enough uniqueness to be globally unique IDs. Microsoft's GUID had 128 bits; a good hash function might have 160 bits; those serial numbers, culled from widely scattered machines, aren't unique enough.
There are 48 (presumably) hex digits there. Each hex digit represents 4 bits. So the number is a 192 bit value.
is that it's designed with a very specific purpose in mind. To provide a framework to do 'proper' polygonal rendering.
Direct3D on the other hand, is a thin layer over 3D hardware. Microsoft, as usual, is very pragmatic. If some video-card company comes out with a crazy feature like an 8 Dimentional Voxel based chip(or more realisitically a ParticleEngine(tm) chip), it'll get incorporated into D3D, and Microsoft will write a software version for cards that don't. It doesn't matter that the technology will be dead in six months.
OpenGL, on the other hand, has been criticized because they're slow to add extentions. But the OpenGL additude is that it does basically everything it's supposed to anyway. Some crazy 8D Voxels or particle engines have nothing to do with Polygon rendering. True or not, it prevents you from using all the cool new tricks on those $400 dollar videocards.
Basically what they do is encrypt the password with blowfish. Then they take the resulting cypher and encrypt it in blowfish. Then they take that result and encrypt it in blowfish. And repeat the cycle something like 36 times. This effectively creates a one-way hash.
I think the logic is not so much that it's a provable perfect hash (only one password will create the same hash), but that it's way to computationally expensive to do a dictionary attack.
AES can actaully be decrypted, so so can your passwords.
md5 is a one way hash. That means there's no way to decrypt the password once it's encoded. This makes sense for this purpose because you don't care what a password is as long as it's the right one. There's no reason to decypher a password, if someone forgets it you just reset it.
And it should work especially well with the American Bar Association
Send them this a nice little e-mail telling them that you are blind and their public site is violating the Americans With Disabilities Act, as it won't work with an audio browser.
Per the spec, you can request a compression method to be used, without the user noticing anything. The trick is making sure the XML-RPC client and server both have the same stuff.
This agreement seems fair. Clearly, a company needs to own all of the source code behind their product. They can't worry about a disgruntled ex-employee suddenly demanding that they pay royalties for 'his code' or any other things that might pop up.
Just sit down and write the code from scratch. Even if you're doing basically exactly the same thing you've done before. If you get a job at another company doing the exact same thing, rewrite it from scratch again.
It not only protects the company, it protects you from any ex-employers.
the article suggests you buy a CD from linuxcentral. Get the official CD from openbsd.org instead so that the people who actually work on it get some money.
1) There's changelogs at openbsd.org. The ABBREVIATED LIST shows something like 700 changes between 2.8 and 2.9.
2) It's open source and the 'original' programs are open source. There's a program called diff that will allow you to see what is different.
3) OpenBSD doesn't release Binary upgrades between major releases. They release patches and expect you to be able to re-compile the system. One of the big reasons to do this is so that anyone who feels like it can look at the patches and see what is really being changed.
I don't know what your situation is, so I don't want to flame you personally, but I think they provide more than enough information for anyone who has the skills to look at changes and see what effects they have. For people who don't have the skills to be able to do this, no amount of documentation/versioning is going to accomplish anything.
Slashdot Mirror
Trolls throughout history:
But guess what? There is a real cost associated with the KKK marching in DC, or giving some speeches in your hometown. There was also a very real cost when thousands of protesters showed up at the WTO meeting in Seattle.
And the new movie where Chris Tucker plays the first black president is certainly Speculative Fiction, but I doubt it'll win any Nebula Awards.
He basically disected the world's mythology and found certain story paradigms that existed in just about every culture known to man. You would have different characters and adventures, but the basic dramatic structure would be the same. The interesting thing is that the stories came about independantly. There's just something in the back of human's brains that makes certain stories universal.
The original Star Wars was based on the "Hero's Journey" paradigm. Lucas has acknowledged this.
Campbell is interesting reading if you get the chance, and have the inclination.
Oh yeah, and Star Wars isn't Science Fiction either.
Even a cursory examination should show that these numbers don't have enough uniqueness to be globally unique IDs. Microsoft's GUID had 128 bits; a good hash function might have 160 bits; those serial numbers, culled from widely scattered machines, aren't unique enough.
There are 48 (presumably) hex digits there. Each hex digit represents 4 bits. So the number is a 192 bit value.
And here's a link Look at the GUI/Windowing system package.
Glad to see someone in the Linux world realized that Anti-aliasing isn't next-gen technology.
Somebody please tell Linus what this "transmeta" company is up to so he can stop it!!!!!!!
War is peace
igonrance is strength
free software is slavery
To forge ASCII-based files.
I've got some ICQ logs that prove that the moon-landing was fake and the world is flat.
The Python software Foundation was announced on Tuesday, but I guess that isn't important enough for a story.
Go ahead, click it
is that it's designed with a very specific purpose in mind. To provide a framework to do 'proper' polygonal rendering.
Direct3D on the other hand, is a thin layer over 3D hardware. Microsoft, as usual, is very pragmatic. If some video-card company comes out with a crazy feature like an 8 Dimentional Voxel based chip(or more realisitically a ParticleEngine(tm) chip), it'll get incorporated into D3D, and Microsoft will write a software version for cards that don't. It doesn't matter that the technology will be dead in six months.
OpenGL, on the other hand, has been criticized because they're slow to add extentions. But the OpenGL additude is that it does basically everything it's supposed to anyway. Some crazy 8D Voxels or particle engines have nothing to do with Polygon rendering. True or not, it prevents you from using all the cool new tricks on those $400 dollar videocards.
Since 1Ghz frequencies are touching the microwave area of the EMR spectrum.
Pro:
Save $100 on a chip.
Con:
Spend $300 on cooling gear.
Basically what they do is encrypt the password with blowfish. Then they take the resulting cypher and encrypt it in blowfish. Then they take that result and encrypt it in blowfish. And repeat the cycle something like 36 times. This effectively creates a one-way hash.
I think the logic is not so much that it's a provable perfect hash (only one password will create the same hash), but that it's way to computationally expensive to do a dictionary attack.
AES can actaully be decrypted, so so can your passwords.
md5 is a one way hash. That means there's no way to decrypt the password once it's encoded. This makes sense for this purpose because you don't care what a password is as long as it's the right one. There's no reason to decypher a password, if someone forgets it you just reset it.
And it should work especially well with the American Bar Association
Send them this a nice little e-mail telling them that you are blind and their public site is violating the Americans With Disabilities Act, as it won't work with an audio browser.
Why are they 120 characters instead of 128?
at least in theory.
Per the spec, you can request a compression method to be used, without the user noticing anything. The trick is making sure the XML-RPC client and server both have the same stuff.
If you really want to use XML and Distributed Components in an even less practical way, check this out.
This agreement seems fair. Clearly, a company needs to own all of the source code behind their product. They can't worry about a disgruntled ex-employee suddenly demanding that they pay royalties for 'his code' or any other things that might pop up.
Just sit down and write the code from scratch. Even if you're doing basically exactly the same thing you've done before. If you get a job at another company doing the exact same thing, rewrite it from scratch again.
It not only protects the company, it protects you from any ex-employers.
the article suggests you buy a CD from linuxcentral. Get the official CD from openbsd.org instead so that the people who actually work on it get some money.
That C++ programmers should be using cout and the string class instead of char[]
1) There's changelogs at openbsd.org. The ABBREVIATED LIST shows something like 700 changes between 2.8 and 2.9.
2) It's open source and the 'original' programs are open source. There's a program called diff that will allow you to see what is different.
3) OpenBSD doesn't release Binary upgrades between major releases. They release patches and expect you to be able to re-compile the system. One of the big reasons to do this is so that anyone who feels like it can look at the patches and see what is really being changed.
I don't know what your situation is, so I don't want to flame you personally, but I think they provide more than enough information for anyone who has the skills to look at changes and see what effects they have. For people who don't have the skills to be able to do this, no amount of documentation/versioning is going to accomplish anything.