...Finally, the sides must not be clearly defined at the beginning of the game. Your allies shouldn't be a gameplay decision based on what side of a coin you flip. Alliances need to be built out of a common desire to survive. You cannot possibly have a real hatred for an enemy just because your predisposed to them. But more importantly, you are forced to ally with those you may not want to because you are on the same side.
Asheron's Call II had that sort of a system. Every guild belonged to one of three factions so when you joined a guild, you became part of that faction. There was no artificial separation along racial boundaries.
It's not a question of your end points needing that kind of bandwidth, it's a question of the links between ISPs and such. Look at any of the large router manufacturers today and see what kind of interfaces they're putting on their high-end gear: multiple 10Gbps ports. You can safely believe that if 100Gbps were available now that people would be using it. The step to 1Tbps is a large one, but there's no such things as "too much" bandwidth.
Kenosis is really only a platform for forming peer meshes. Are you telling me you can't think of any use for that sort of a thing? How about distributed computing, for one. As more nodes join the mesh, the workload is extended to encompass the newly available resources. Serverless instant messaging also comes to mind.
I assume that what you are really asking about is tying this to BitTorrent and the peer-to-peer distribution of the.torrent tracker file. As others have already stated, the elimination of a single point of failure in a networked system is generally considered a good thing. Consider trying to download the latest Slackware release when the server hosting the tracker is suffering from a DDoS.
So, in answer to your question, even outside of "piracy" this is still very useful.
A few kilowatts?!? MegaWatts?! GIGAWATTS!?!? I've worked with metal cutting laser that was (only) 10 Watts. Even that was more than enough to take a chunk out of a guy's finger when he wasn't being careful. Note this was an infrared beam on a design prototype and that the safety interlocks were disengaged which is why he was able to get his finger in the way when the laser was on. Yes, he knew better but just got careless.
I'm sure you were joking about those power ranges, but anything above a few milliwatts requires warning labels and anything above about 100 mW (I think) requires safety mechanisms so that people don't hurt themselves. Of course, things like wavelength, whether the laser light is scattered or directed, etc. come into account.
Go
here to see how the government classifies lasers.
No. Futurama proved that drinking that much coffee in such a short time period accelerates your metabolism to such a high level that everything else seems to slow down and you move at super-speed.
While I agree that most of the people downloading music from the p2p services are simply looking for freebies, the legitimate gripe that the rest of have is that the labels making up the RIAA have done nothing to address the root of the problem for people who would otherwise buy music. Namely, CD's are too expensive for the majority of the crap that is out there, and most of the legitimate online music services are pathetic.
Then consider the case of DVD's, as you mentioned. For slightly more than that overpriced CD, I can get not only a full length movie, but usually a whole other disc filled with behind the scenes info, out-takes, alternate endings, directors commentary, etc. It's not just about wanting something without having to pay for it, it's about getting a product at a reasonable price. In any market where people feel gouged, any reasonably priced alternative will flourish, even if that involves the creation of a black or grey market. Of course, getting something free will always be an attractive offer if the perceived consequences are minor.
It's the strong-arm tactics of the RIAA, without the promotion of reasonable alternatives that earns them the label of "goon".
...I think I should point out that the RIAA does provide a service to the artist.
The RIAA actually provides a service to the record labels. The labels provide services to the artists. In and of itself, the RIAA doesn't actually do anything for the artists, directly.
Heh. For a minute there I thought you said asses, not assets, and was ready to make a comment about them either facing pound-me-in-the-ass prison or pound-me-in-the-ass IBM management.
Wow, I never thought to try that.
The big question is, does it still load up all of the GUI code? If so, then that's not worth so much. If it doesn't then that probably reduces resource consumption by a lot. It would be interesting to run benchmarks against the same system both with and without the video card installed to see what effect this has.
Not to mention they're probably breaking the "cd" standard, and still calling it a compact discs. I wonder when pioneer (or sony or philips or whomever it is that owns the right, patent, whatever to "cd") will sue the people who cook up these horrid schemes.
When copy-protected CDs first started coming out, Philips said that the official compact disc digital audio logo could not be put on the packaging, since the discs did not conform to the standard and, hence, were not really "compact discs". If you follow the link to the report, you will see mention that "The "Compact Disc Digital Audio" logo is absent from the printed jacket and the face of the disc".
Yes and it is worth the jump backwards in technology to help OS manufacturers continue to pedal sub par product and services that are the real cause of the problem. Attacking a problem at somewhere other than its source has always been such a great way to deal with challenges like this.
Or, we could realize that blocking some ports would be part of a defense-in-depth strategy. You know, that "layered" thing security experts always talk about? That way, when someone writes or uses a vulnerable app, the community at large still has a chance of minimizing potential damage.
I agree that just blocking all ports except those used for web browsing and email would be overkill. However, blocking ports 135-139 and 445 alone would probably help a lot.
According to Mr. Campell, no one has picked it up for distribution. That's why he's been going around to some of the showings - in order to generate a little more hype and get people to head down to the local, independent theater. They are relying almost exclusively on word-of-mouth advertising as well, so if you see the movie and enjoy it, tell anyone else who might be interested.
"I won't be doing this. Such a think could void warranties."
So, what you're saying is you're worried about the thought police cracking down on rogue warranty violators? May I suggest a tinfoil hat; perhaps without the thermal paste option?
You are correct, however, that conductance is not very good in resistors. Hence the name resistors.
While this may apply to the home (and possibly the business) pure software market, it's not the case across the board. I work for a company which makes specialized testing equipment controlled across a network from a PC. Believe me, there's MANY of my coworkers who would benefit from a book like this. I've lost count of the number of times that a great new feature has been made available, but the implementation has been such that it's rendered almost completely useless. This is primarily due to the fact that those who are implementing it have no real idea of how our customers interact with our products. (Depressing, but true)
In every project, there's a number of small choices in how details are implemented that can make things wonderful and easy to use, or turn them into a nightmare of a user interface. Without understanding your target audience, the chances are very good that doing something one way makes perfect, logical sense to you, but has your customers tearing out their hair in frustration.
The nice thing about general semiconductor technology is that it's applicable to more than just microprocessors. AMD makes a whole range of products, not just PC CPUs. While this will be nice for pushing computer clock speeds, it will really be helpful for a whole range of applications most people will never think about. Consider things like Digital Signal Processing. There are still things for which there is no "fast enough". Think full-body MRI scans at 30fps; think high-energy physics simulations, weather modelling, etc.; think OC-768. These examples are not just about processor speed, though, as was mentioned in other posts, people running heavily loaded servers would also be greateful for cheap, faster processors.
In any event, it's been demonstrated repeatedly that no matter how fast a general purpose computer or function specific device you build, someone, somewhere will find an application that could benefit from making it even faster.
I agree. It's almost always easier to understand code you've written than code someone else has written, which means it's a lot faster to track down bugs in your own code. Even with good documentation and plenty of comments (and how often do you really see both of those in one project?) understanding someone else's code is time consuming and you are more prone to missing something, which could create even more bugs.
I don't know if saying that the adoption of a threat model isn't just a nice way of saying that you have to accept what you cannot change.
The point of establishing your threat model is so that you know what you are defending against. It's the first step in any serious engineering work: define the problem. If you don't know what problem you are trying to solve - in this case how to prevent copying - how do you know what kind of a system to design?
Basically Mr. Felton is proposing that there are only two applicable problem sets - either everyone needs to be locked out from copying, or simply most people need to be prevented from copying. Which problem they choose to tackle will determine the type of system design.
Slashdot Mirror
...Finally, the sides must not be clearly defined at the beginning of the game. Your allies shouldn't be a gameplay decision based on what side of a coin you flip. Alliances need to be built out of a common desire to survive. You cannot possibly have a real hatred for an enemy just because your predisposed to them. But more importantly, you are forced to ally with those you may not want to because you are on the same side.
Asheron's Call II had that sort of a system. Every guild belonged to one of three factions so when you joined a guild, you became part of that faction. There was no artificial separation along racial boundaries.
It's not a question of your end points needing that kind of bandwidth, it's a question of the links between ISPs and such. Look at any of the large router manufacturers today and see what kind of interfaces they're putting on their high-end gear: multiple 10Gbps ports. You can safely believe that if 100Gbps were available now that people would be using it. The step to 1Tbps is a large one, but there's no such things as "too much" bandwidth.
Kenosis is really only a platform for forming peer meshes. Are you telling me you can't think of any use for that sort of a thing? How about distributed computing, for one. As more nodes join the mesh, the workload is extended to encompass the newly available resources. Serverless instant messaging also comes to mind.
I assume that what you are really asking about is tying this to BitTorrent and the peer-to-peer distribution of the .torrent tracker file. As others have already stated, the elimination of a single point of failure in a networked system is generally considered a good thing. Consider trying to download the latest Slackware release when the server hosting the tracker is suffering from a DDoS.
So, in answer to your question, even outside of "piracy" this is still very useful.
Oh, I always though it was Drug Awareness by Repeated Experimentation.
I'm sure you were joking about those power ranges, but anything above a few milliwatts requires warning labels and anything above about 100 mW (I think) requires safety mechanisms so that people don't hurt themselves. Of course, things like wavelength, whether the laser light is scattered or directed, etc. come into account.
Go here to see how the government classifies lasers.
No. Futurama proved that drinking that much coffee in such a short time period accelerates your metabolism to such a high level that everything else seems to slow down and you move at super-speed.
Then consider the case of DVD's, as you mentioned. For slightly more than that overpriced CD, I can get not only a full length movie, but usually a whole other disc filled with behind the scenes info, out-takes, alternate endings, directors commentary, etc. It's not just about wanting something without having to pay for it, it's about getting a product at a reasonable price. In any market where people feel gouged, any reasonably priced alternative will flourish, even if that involves the creation of a black or grey market. Of course, getting something free will always be an attractive offer if the perceived consequences are minor.
It's the strong-arm tactics of the RIAA, without the promotion of reasonable alternatives that earns them the label of "goon".
...I think I should point out that the RIAA does provide a service to the artist.
The RIAA actually provides a service to the record labels. The labels provide services to the artists. In and of itself, the RIAA doesn't actually do anything for the artists, directly.
Heh. For a minute there I thought you said asses, not assets, and was ready to make a comment about them either facing pound-me-in-the-ass prison or pound-me-in-the-ass IBM management.
Wow, I never thought to try that.
The big question is, does it still load up all of the GUI code? If so, then that's not worth so much. If it doesn't then that probably reduces resource consumption by a lot. It would be interesting to run benchmarks against the same system both with and without the video card installed to see what effect this has.
When copy-protected CDs first started coming out, Philips said that the official compact disc digital audio logo could not be put on the packaging, since the discs did not conform to the standard and, hence, were not really "compact discs". If you follow the link to the report, you will see mention that "The "Compact Disc Digital Audio" logo is absent from the printed jacket and the face of the disc".
Or, we could realize that blocking some ports would be part of a defense-in-depth strategy. You know, that "layered" thing security experts always talk about? That way, when someone writes or uses a vulnerable app, the community at large still has a chance of minimizing potential damage.
I agree that just blocking all ports except those used for web browsing and email would be overkill. However, blocking ports 135-139 and 445 alone would probably help a lot.
According to Mr. Campell, no one has picked it up for distribution. That's why he's been going around to some of the showings - in order to generate a little more hype and get people to head down to the local, independent theater. They are relying almost exclusively on word-of-mouth advertising as well, so if you see the movie and enjoy it, tell anyone else who might be interested.
Oh, great, so how long is it going to be until the first "In Soviet Rus^H^H^H Linux..." joke?
Come on, we've been expecting that ever since they patented one's and zero's.
So, what you're saying is you're worried about the thought police cracking down on rogue warranty violators? May I suggest a tinfoil hat; perhaps without the thermal paste option?
You are correct, however, that conductance is not very good in resistors. Hence the name resistors.
In every project, there's a number of small choices in how details are implemented that can make things wonderful and easy to use, or turn them into a nightmare of a user interface. Without understanding your target audience, the chances are very good that doing something one way makes perfect, logical sense to you, but has your customers tearing out their hair in frustration.
Hmmm... must be a slow day, all I can think of is laxatives.
Glad I'm not the only one who saw the title and immediately thought of a system that alerted you to the fact that you just had an accident.
Sound of brakes immediately followed by *CRASH*, and then, *BEEP* and a little accident warning light comes on.
The nice thing about general semiconductor technology is that it's applicable to more than just microprocessors. AMD makes a whole range of products, not just PC CPUs. While this will be nice for pushing computer clock speeds, it will really be helpful for a whole range of applications most people will never think about. Consider things like Digital Signal Processing. There are still things for which there is no "fast enough". Think full-body MRI scans at 30fps; think high-energy physics simulations, weather modelling, etc.; think OC-768. These examples are not just about processor speed, though, as was mentioned in other posts, people running heavily loaded servers would also be greateful for cheap, faster processors.
In any event, it's been demonstrated repeatedly that no matter how fast a general purpose computer or function specific device you build, someone, somewhere will find an application that could benefit from making it even faster.
I agree. It's almost always easier to understand code you've written than code someone else has written, which means it's a lot faster to track down bugs in your own code. Even with good documentation and plenty of comments (and how often do you really see both of those in one project?) understanding someone else's code is time consuming and you are more prone to missing something, which could create even more bugs.
The point of establishing your threat model is so that you know what you are defending against. It's the first step in any serious engineering work: define the problem. If you don't know what problem you are trying to solve - in this case how to prevent copying - how do you know what kind of a system to design?
Basically Mr. Felton is proposing that there are only two applicable problem sets - either everyone needs to be locked out from copying, or simply most people need to be prevented from copying. Which problem they choose to tackle will determine the type of system design.