Obviously there is a lot of subjectivity to whether you like a game, but here's my take after playing for about a year.
WoW has kept me interested and playing since last November mainly because as you progress through the game you keep seeing new things. There are many moments when I've said "wow, that's really cool" as I enter a new zone. I think Blizzard has done a great job at creating a world that is interesting to explore.
Compared to single-player RPGs, the addition of other players in the world and the ability to do cooperative quests IMO adds a dimension to the online games that really helps replayability.
Bottom line, WoW held my interest a lot longer than Morrowind. For me this qualifies it as a great game.
This is a specious argument. The house has a lot more incentive to keep the game honest so that more players come to them. Look at how much money the house makes in an honest game - they don't need to cheat.
Individual players don't care about the site's reputation, so they would be much more likely to want to cheat.
C'mon now, they announced ahead of time they were going to do this. In the auction procedures they clearly stated they might price the IPO below the auction price. Several news sources reported before the IPO that it was likely they would do this.
Why does everything have to be a conspiracy?
Re:Does this finally solve the *other* major probl
on
IEEE Approves 802.11i
·
· Score: 3, Informative
Yes, it does solve this problem. Since every wireless client (insider as you call it) is using a different key, one client can't decrypt another's traffic.
The key is negotiated at authentication time and is valid only for the given client and sesion. Without the client's authentication credential (certificate or otherwise), you can't get a hold of the key.
Today I had the opportunity to look at the [incriminating?] code snippets.
Through a mistake of the representing Law firm, my colleague and I did not have to sign an NDA, unlike the other 7 representatives that also were viewing the code today. This is in stark contrast to the Microsoft representatives who apparently even had to maintain silence with their own supervisors, and were only allowed to report back to their internal [Legal?] department.
Now to the code itself:
46 pages each containing one half Linux code (largely printed posts out of the linux-kernel lists) and one half listings from SCO were presented under legal supervision. It is therefore not possible to tell whether this actually comes from SysV-Sources, as they are taken out of context. Also interisting is that all dates are taken out of both parts, even out of the comments.
The comments are in fact identical in places. Even some of the jokes are the same on both sides. What is apparent, though, is that in the most similar places the preceding source code is quite different. The basic structure of the affected functions are similar, but the concrete implementation is quite different. Variables and function names are different, loops are structured differently, conditions run on chained conditionals or bitmaps. All in all only one thing is sure: the functions presented in the code-snippets were often the same, which was to be expected, though.
In the concrete implementation there are so many differences, however, that a proof of the same origin will be hard to construct, albeit not impossible.
However one function of the scheduler presents a [breaking point?], as except for minor differences it is identical. In this case there are also a whole row of matching comments.
Only one routine of the Memory Management offers comparable similarity. In this case, however, only the linux version has comments.
Only a lawyer could safely judge whether these two similarities alone provide proof enough for a verdict. The vague similarties in other parts are, in my opinion, insufficient, since a certain similarity is to be expected as both pieces are based on the same standards. On the other hand, I have no clue where the identical comments in different code could come from. In any case, this should be researched more closely, especially with the dates restored. Only with these would a copyright infringement be provable.
As to the discussion of the piece of Linux sold by SCO/Caldera itself under the GPL, one has to take into account that no Court has commented on the enforcability of the GPL yet...
[Sorry ran out of time. I will try to get to the rest later. Perhaps someone else can translate the rest.]
But there could be garbage byte streams which match both hashes, right? In fact there probably are many of these. How many hashes would you need to get a unique answer? How much data would that entail? Look up the pigeon hole principle (the real one, not zeosync's weird obfuscated one) to see how to prove that you can't possibly come up with an algorithm that compresses all byte streams of a given length into a smaller size. This doesn't prove that your approach can't work, but might make it more intuitively apparent why it is likely that such compression is not feasible.
I see your point, and if Dmitry was in fact ignorant that his employer was going to sell his software in the United States, I will concede that he deserves to go free.
However, it seems to me that "I just was following orders" should not be an acceptable excuse for this matter. Just being an employee doesn't absolve him of the responsibility of how his code was used.
I certainly don't approve of the DMCA, and I am an EFF member, but I think that there is a good chance that Dmitry may in fact bear some responsibility in this whole matter. As others have reported here, Elcomsoft seems to be a company that has targetted the less legitimate areas of the internet (spam, breaking protections). Was Dmitry really unaware of the kind of company he was working for?
Actually, the rotaries in the RX-7 are all 2-rotor models. Having said that, if an apex seal blows, those engines are still toast. All those little metal bits don't do the engine any good, and it has a tendency to seize up (been there, done that). On the prototype race cars that Mazda built, they use a 3-rotor engine.
The real hack, though, is the emissions control junk Mazda put on RX-7's in the late 70's and early 80's in order to sell the cars in California. You've never seen so many vacuum tubes before...
I may not be completely up on Swiss laws, but you are allowed to carry your service weapon to the range to practice. However, if you're not on your way to or from the range, the laws that you mention probably apply.
Note that there is (rare) gun violence in Switzerland, but this almost never involves service weapons because of social taboos. Nor is the service weapon considered for home defense. It is there only in case of a mobilization against an external threat. This is not something that the gun lobby here ever mentions.
The simple fact is that there are a lot of cultural constraints in a place like Switzerland that are difficult to understand unless you are exposed to them. Certain things are just not done there.
I'm an American citizen, but I work for a Silicon Valley company where a significant portion of the workforce is on H1-B's. I've been in the position of having to hire in this company, and I can tell you that it is very difficult to find resumes from Americans here. At least 80% of the resumes that you get from going to a hiring fair like Westech are from recent immigrants. I can tell you that there is no discrimination or salary-gouging in the process when hiring at this company.
On the other hand, I also have friends who have come over to this country through contracting houses who basically seem to indenture the people they bring over. These companies seem to try to keep their employees in the dark about immigration laws to make them afraid of switching jobs all the while skimming a significant portion of their employees wages. The companies I know about are run by "entrepreneurs" (con artists?) from the countries from which they draw their workforce.
The fact is that given the shortage of skilled workers here, many American companies are willing to go through the H1-B visa transfer hassle and hire immigrants directly. If more of the people working for the "slave traders" knew this, I suspect they would find that they could relatively quickly (2-3 months) spring themselves free from their exploitative employment.
Slashdot Mirror
Obviously there is a lot of subjectivity to whether you like a game, but here's my take after playing for about a year.
WoW has kept me interested and playing since last November mainly because as you progress through the game you keep seeing new things. There are many moments when I've said "wow, that's really cool" as I enter a new zone. I think Blizzard has done a great job at creating a world that is interesting to explore.
Compared to single-player RPGs, the addition of other players in the world and the ability to do cooperative quests IMO adds a dimension to the online games that really helps replayability.
Bottom line, WoW held my interest a lot longer than Morrowind. For me this qualifies it as a great game.
This is a specious argument. The house has a lot more incentive to keep the game honest so that more players come to them. Look at how much money the house makes in an honest game - they don't need to cheat.
Individual players don't care about the site's reputation, so they would be much more likely to want to cheat.
I think the SHA-1 speculation originated because of the SHA-0 collision, not the MD5 collision.
SHA-0 obviously is related to SHA-1. So although no one has yet extended the SHA-0 collision to SHA-1, it is conceivable it might be possible.
C'mon now, they announced ahead of time they were going to do this. In the auction procedures they clearly stated they might price the IPO below the auction price. Several news sources reported before the IPO that it was likely they would do this.
Why does everything have to be a conspiracy?
Yes, it does solve this problem. Since every wireless client (insider as you call it) is using a different key, one client can't decrypt another's traffic.
The key is negotiated at authentication time and is valid only for the given client and sesion. Without the client's authentication credential (certificate or otherwise), you can't get a hold of the key.
Today I had the opportunity to look at the [incriminating?] code snippets.
Through a mistake of the representing Law firm, my colleague and I did not have to sign an NDA, unlike the other 7 representatives that also were viewing the code today. This is in stark contrast to the Microsoft representatives who apparently even had to maintain silence with their own supervisors, and were only allowed to report back to their internal [Legal?] department.
Now to the code itself:
46 pages each containing one half Linux code (largely printed posts out of the linux-kernel lists) and one half listings from SCO were presented under legal supervision. It is therefore not possible to tell whether this actually comes from SysV-Sources, as they are taken out of context. Also interisting is that all dates are taken out of both parts, even out of the comments.
The comments are in fact identical in places. Even some of the jokes are the same on both sides. What is apparent, though, is that in the most similar places the preceding source code is quite different. The basic structure of the affected functions are similar, but the concrete implementation is quite different. Variables and function names are different, loops are structured differently, conditions run on chained conditionals or bitmaps. All in all only one thing is sure: the functions presented in the code-snippets were often the same, which was to be expected, though.
In the concrete implementation there are so many differences, however, that a proof of the same origin will be hard to construct, albeit not impossible.
However one function of the scheduler presents a [breaking point?], as except for minor differences it is identical. In this case there are also a whole row of matching comments.
Only one routine of the Memory Management offers comparable similarity. In this case, however, only the linux version has comments.
Only a lawyer could safely judge whether these two similarities alone provide proof enough for a verdict. The vague similarties in other parts are, in my opinion, insufficient, since a certain similarity is to be expected as both pieces are based on the same standards. On the other hand, I have no clue where the identical comments in different code could come from. In any case, this should be researched more closely, especially with the dates restored. Only with these would a copyright infringement be provable.
As to the discussion of the piece of Linux sold by SCO/Caldera itself under the GPL, one has to take into account that no Court has commented on the enforcability of the GPL yet...
[Sorry ran out of time. I will try to get to the rest later. Perhaps someone else can translate the rest.]
But there could be garbage byte streams which match both hashes, right? In fact there probably are many of these. How many hashes would you need to get a unique answer? How much data would that entail? Look up the pigeon hole principle (the real one, not zeosync's weird obfuscated one) to see how to prove that you can't possibly come up with an algorithm that compresses all byte streams of a given length into a smaller size. This doesn't prove that your approach can't work, but might make it more intuitively apparent why it is likely that such compression is not feasible.
I see your point, and if Dmitry was in fact ignorant that his employer was going to sell his software in the United States, I will concede that he deserves to go free.
However, it seems to me that "I just was following orders" should not be an acceptable excuse for this matter. Just being an employee doesn't absolve him of the responsibility of how his code was used.
I certainly don't approve of the DMCA, and I am an EFF member, but I think that there is a good chance that Dmitry may in fact bear some responsibility in this whole matter. As others have reported here, Elcomsoft seems to be a company that has targetted the less legitimate areas of the internet (spam, breaking protections). Was Dmitry really unaware of the kind of company he was working for?
Actually, the rotaries in the RX-7 are all 2-rotor models. Having said that, if an apex seal blows, those engines are still toast. All those little metal bits don't do the engine any good, and it has a tendency to seize up (been there, done that). On the prototype race cars that Mazda built, they use a 3-rotor engine.
The real hack, though, is the emissions control junk Mazda put on RX-7's in the late 70's and early 80's in order to sell the cars in California. You've never seen so many vacuum tubes before...
I may not be completely up on Swiss laws, but you are allowed to carry your service weapon to the range to practice. However, if you're not on your way to or from the range, the laws that you mention probably apply.
Note that there is (rare) gun violence in Switzerland, but this almost never involves service weapons because of social taboos. Nor is the service weapon considered for home defense. It is there only in case of a mobilization against an external threat. This is not something that the gun lobby here ever mentions.
The simple fact is that there are a lot of cultural constraints in a place like Switzerland that are difficult to understand unless you are exposed to them. Certain things are just not done there.
I'm an American citizen, but I work for a Silicon Valley company where a significant portion of the workforce is on H1-B's. I've been in the position of having to hire in this company, and I can tell you that it is very difficult to find resumes from Americans here. At least 80% of the resumes that you get from going to a hiring fair like Westech are from recent immigrants. I can tell you that there is no discrimination or salary-gouging in the process when hiring at this company.
On the other hand, I also have friends who have come over to this country through contracting houses who basically seem to indenture the people they bring over. These companies seem to try to keep their employees in the dark about immigration laws to make them afraid of switching jobs all the while skimming a significant portion of their employees wages. The companies I know about are run by "entrepreneurs" (con artists?) from the countries from which they draw their workforce.
The fact is that given the shortage of skilled workers here, many American companies are willing to go through the H1-B visa transfer hassle and hire immigrants directly. If more of the people working for the "slave traders" knew this, I suspect they would find that they could relatively quickly (2-3 months) spring themselves free from their exploitative employment.