The professor who teaches operating systems at my university runs people's code through an automated cheating detector. The first operating systems project ends up being around 8 lines of code to complete a stub he provided. In a class of 30 people, there will inevitably be a couple of people who produced similar enough code that they get a zero on the assignment even if they may not even have talked to the person who had similar code. After the first project everyone gets scared and writes the most obscure code they can to avoid being accused of cheating.
On another note, I was a teaching assistant for a lab last semester, and caught a few students cheating. Most often I could hold the two assignments up to the light and see that each line lined up exactly. I had a couple of students who would hand in the same assignment in different fonts, but I nailed them for having the exact same typos.
There were some other people I suspect might have been cheating, but they changed variable names and switched around lines if the order didn't matter to the point where I wasn't confident that the similarities weren't just because they were solving the same problems.
It's not just the storage cost that concerns me. For every piece of retained data that could help the police solve a crime, there are a thousand pieces of data that could help hackers steal identities. If they're not secured properly (and there will always be someone who doesn't secure them properly) ISP data stores would be a great target for hackers. If these laws go through, I expect a net increase in crime as identity theft increases sharply and police investigations get moderately easier.
The main issue is that NASA has been known undercut the private sector at expense to the taxpayer. I've read about a few of companies that came up with mechanisms for launching satellites for a lot less than it costs NASA, but NASA offered a lower price to make themselves seem useful.
Even though NASA's methods may not be as efficient, they can offer a lower price and subsidize the costs with taxpayer dollars. Private enterprise can't compete with that.
Regardless of what other advice you follow to limit the chances of a lawsuit, you should start a Limited Liability Company to reduce your personal exposure to such a lawsuit. In most states this should cost around $100. If the LLC releases the game, it is the LLC that assumes liability. If the creator of the original game does sue, they can only be awarded the assets of your LLC (which, if you manage it correctly, should be limited to the game itself).
This will take a little bit of research, but I think it will be worth the time and money. As others have pointed out, even if you're legally clear, the original game's owner could get you into a lawsuit that is prohibitively expensive to defend. In that case you may want to cut your losses and offer them the rights to the game. If you have an LLC, they're sure to accept because the rights to the game is all they could acquire by suing (and suing would cost them money). If you don't have an LLC, they could pursue more of your personal assets as damages.
From a "ratio" standpoint, if you consider the actual damage from illegally downloading a song to be 99 cents...
Just a nitpick, but people are usually sued for uploading, not downloading. If I upload something to you, then you upload that to a third person, I'm partly responsible for that third person getting the content. Even so, I think it's hard to argue that any individual is responsible for more than a few dozen people getting the content (unless they leaked content that wasn't for sale yet).
Taking that into consideration, perhaps your numbers should be knocked down an order of magnitude or more, but it still leaves a valid point (and perhaps it's a viable legal argument).
I always thought the reason it was cheaper to build a system from parts than buy a pre-built box was just a matter of scale. It's not hard to find a handful of parts that are on sale because they're beginning to be antiquated and retailers are trying to get rid of them, but I always assumed the price I paid for the parts was still above the normal wholesale price.
I can imagine that in bulk and with the right connections, you might be able to get these parts a bit below the normal wholesale price. The thing I have trouble with, is the idea that you can get enough of a discount to offset the cost of supporting random hardware configurations and software for several different CPU architectures.
I'm not sure I completely agree with your proposal, but I definitely agree with the sentiment. A party with deep pockets shouldn't be able to force an innocent party into a settlement by making it cost prohibitive to defend yourself - that's extortion by my book.
I think a better alternative would be some kind of motion where a defendant can request that the judge order the plaintiff to pay legal fees. The defendant would need to be able to convince the judge that defending the suit is cost prohibitive and that an innocent but fiscally responsible party would be inclined to settle rather than defend against the suit. The judge could require the plaintiff to pay the defendant's legal fees, and if the judge finds in favor of the plaintiff the legal fees may be awarded back as well. Someone who knows they're at fault would still be inclined to settle out of court, but someone who believes he is innocent would have a viable means of defending himself.
I'm not sure I agree that what you suggest is the best approach (because it allows a corporation at least one frivolous suit before they have to start paying the other side's legal fees), but I definitely agree with the sentiment. Corporations with deep pockets shouldn't be able to force innocent people into settlements simply because it's too expensive to defend yourself - that's extortion.
I think a better option than what you suggest would be if the defendant could file a motion for coverage of legal fees. The defendant would have to convince the judge that the plaintiff's deep pockets make prohibitively expensive to defend the case, and that without the other side footing the legal fees the fiscally responsible action of an innocent party would be to settle. If the judge rules in favor of the plaintiff, he may decide to award the defendant's legal fees back to the plaintiff. If you know you're liable, you'd still be inclined to settle rather than rack up legal fees you know you'll have to pay off, but if you're innocent you'd have a viable means to defend yourself.
Well, it should also be mandatory that source code be made available when a binary falls into the public domain...
I disagree, because I think that would be a huge imposition on some people. When I was in high school I wrote a Half-Life server-side mod that I gave out for free. Being a teenager who was learning to code, I didn't have any kind of version control, I just kept editing the same source directory. Two years after my first release the project had moved on considerably and I most certainly did not have the original source. Two years after the last release I doubt I had the source for any version of the code.
I suspect this sort of thing is fairly common. I imagine there are lots of pieces of freeware or other cheap software where the company that made it either isn't around after two years or just isn't organized enough to produce the source for a two year old version of their software.
I hardly ever use my iPod with headphones. Usually it's plugged into speakers or my car stereo. In those cases the signal quality seems to correlate to the volume set on the player, but the volume itself is set by the amplifier. Admittedly, kicking the volume up to the player's 100% tends to distort the signal, but setting the player to a level that would be "safe" in headphones is short of the best signal.
And before anyone asks- no, I'm not remotely concerned about inaccurate results from trusting mythcommflag to catch commercials.
You're not? I used MythTV for years, and while mythcommflag was probably 90% accurate, that extra 10% could make a substantial difference in the viewing experience. It's not a big deal when you accidentally end up with a commercial in the middle of your show, but it can make a huge difference if it cuts out 30 seconds of your TV show.
I'm with you on this one. I did the 30 day trial of Photoshop many years ago, and while I may not have been using its full potential, the stuff I did with it was pretty intuitive. I've used GIMP for my (minimal) image manipulation needs for several years, and only now that I have quite a bit of experience do I find it as easy to use as I found Photoshop the first time I opened it. For the more complex functions, GIMP may be as intuitive as Photoshop, but for the basic stuff GIMP has a steep learning curve.
Similar things have happened with other products like Audacity. My mother-in-law runs a dance studio and was banging ahead against the software she was using to mix tracks for a recital. I suggested Audacity, but she was convinced that because it was free it couldn't possibly be better than what she had. The next year I saw she was using Audacity and commented that I saw she had taken my advice. She told me that this wasn't a free program, that it had come with some piece of hardware she'd purchased. I shook my head and moved on, but I found it interesting that audacity was gaining a user base through inclusion with hardware.
I pay $8.99 a month for a subscription to Netflix, which gets me 1 DVD at a time and unlimited access to Netflix watch instantly. When I started using Hulu, I looked to see if there was some way I could pay a monthly fee to get rid of ads and was stunned that there wasn't (though it sounds like there may be soon). I'm happy to pay a small monthly fee for the shows I want to watch rather than paying $40 a month for the same shows plus several dozen channels I'm never going to watch.
Full disk encryption isn't a panacea for security. If someone nabs your laptop while it's off in the back seat of your car, you don't have much to worry about. If you get malware of some kind or if someone swipes your laptop while it's running, full disk encryption isn't going to help.
Don't take this the wrong way, I encrypt my laptop and would encourage almost everyone to do the same, but you still have to be security conscious.
Seconded. I use clipperz for all of my passwords. Clipperz has some great features.
First, it's a zero-knowledge web application. The web server doesn't know your username or password for its own site, let alone any of the passwords it stores. Everything is encrypted and decrypted on the client using javascript. It's open source and I've actually spent some time looking through the code, so I trust it.
The offline copy is another great feature. You can download an HTML file that operates just like the normal web site, except that you can't add passwords to it. I use the offline copy for every day use because it's a bit snappier and takes the load away from Clipperz servers. In the event that clipperz ever disappears, I still have my offline copy so my passwords aren't lost.
It lets you generate passwords randomly, so I generate a new password for every site I visit. The passwords are long strings with random characters from all over the keyboard, so they're stronger than something a person could think up or remember. I have a different password for every site, so if one gets compromised by a poorly designed website, I don't have to worry about changing my password on a dozen other sites.
It has a sidebar version that works in several browsers. It provides a list of links you can click to automatically log in to any website you have an account on.
I've recommended clipperz to several friends and family members, and I know of at least one who actually uses it frequently (the rest just have a short list of fairly weak, memorable passwords they use on a much longer list of sites).
You'd lose a lot of functionality that way. The only way Gmail could encrypt e-mails in such a way they couldn't produce them later would be to use asymmetric encryption, and only the recipient has the decryption key. That means you'd have to make sure you never lost your key, and you'd have to put it on every computer you wanted to check e-mail from. You'd lose the major benefits of having a web-mail client. You wouldn't be able to search the e-mail, unless Gmail indexed it before encrypting it, in which case they'd just use the indexes as evidence instead of the plaintext e-mails.
If you need to make sure you have legal control over your data, your best bet is to keep your data out of the cloud.
That was my thought. The iPhone might have more apps by virtue of the fact that it's been around longer, and some of them might be more mature than their Android counterparts, but 3 years down the road that won't be the case. In the long term, I'd put my money on Android if for no other reason than it can multitask.
I'm really hoping the rumors about 2.0 having multitouch support will pan out. Android does pretty well with only one contact point, but it could still benefit from multitouch support.
Other than that, both the myTouch and the G1 have an accelerometer which is used by a number of apps and built-in features of the phone. They have GPS, network, and wifi based positioning, which is pretty accurate even with my GPS receiver turned off. They have a built in compass, and there are apps that make use of it. It comes with an Amazon mp3 client, and you can put music on it with a file browser or just about any non-itunes music player.
I don't know what the OP was talking about, as only two of his points have any merit at all.
Reddit does escape all of those symbols, and they use Markdown for adding links. Still, they managed to get owned by an obscure vulnerability that was discovered only because their code is open source.
And that's the point TheLink was trying to make. It would be far simpler to tell the browser not to accept javascript in a certain block of code than it is to explore all the possible exploits that could be leveraged against your alternative markup language. There are hundreds if not thousands of places you can make mistakes, and it could be remedied by a single mechanism that prevented javascript from existing in certain blocks of code.
I am curious how much difference there would have been on a database system that would actually be running in a server environment. Ubuntu definitely got owned by that metric, but SQLite is hardly exemplary of a production database.
For clarity, you retain all of your ownership rights in your User Submissions. However, by submitting User Submissions to YouTube, you hereby grant YouTube a worldwide, non-exclusive, royalty-free, sublicenseable and transferable license...
The above licenses granted by you in User Videos terminate within a commercially reasonable time after you remove or delete your User Videos from the YouTube Website.
So not only do you continue to own your content, you even retain the right to revoke their license to it.
Me too. I'm assuming we'll be able to get back to the orange and brown, it just won't be the default. I'm personally quite fond of the brown and orange (but what do I know? I'm colorblind...).
I plan to upgrade directly from the Ubuntu servers, but I'm only going to hit their servers once for the three machines I'm upgrading. I use apt-cacher, which stores packages on the local network once they've been downloaded by something on the network, then sends out the cached version when it's requested again. It doesn't help much for the odd day-to-day package installation, but it makes significant upgrades much faster after the first system. You have to configure all of the systems to use the proxy, but it's easy to setup. If you run more than one or two systems, I'd definitely look into it.
Slashdot Mirror
The professor who teaches operating systems at my university runs people's code through an automated cheating detector. The first operating systems project ends up being around 8 lines of code to complete a stub he provided. In a class of 30 people, there will inevitably be a couple of people who produced similar enough code that they get a zero on the assignment even if they may not even have talked to the person who had similar code. After the first project everyone gets scared and writes the most obscure code they can to avoid being accused of cheating.
On another note, I was a teaching assistant for a lab last semester, and caught a few students cheating. Most often I could hold the two assignments up to the light and see that each line lined up exactly. I had a couple of students who would hand in the same assignment in different fonts, but I nailed them for having the exact same typos.
There were some other people I suspect might have been cheating, but they changed variable names and switched around lines if the order didn't matter to the point where I wasn't confident that the similarities weren't just because they were solving the same problems.
If you bought a 3 year warranty shortly before Leopard came out you still have 6-8 months left on your warranty.
It's not just the storage cost that concerns me. For every piece of retained data that could help the police solve a crime, there are a thousand pieces of data that could help hackers steal identities. If they're not secured properly (and there will always be someone who doesn't secure them properly) ISP data stores would be a great target for hackers. If these laws go through, I expect a net increase in crime as identity theft increases sharply and police investigations get moderately easier.
The main issue is that NASA has been known undercut the private sector at expense to the taxpayer. I've read about a few of companies that came up with mechanisms for launching satellites for a lot less than it costs NASA, but NASA offered a lower price to make themselves seem useful.
Even though NASA's methods may not be as efficient, they can offer a lower price and subsidize the costs with taxpayer dollars. Private enterprise can't compete with that.
Standard, disclaimer: IANAL.
Regardless of what other advice you follow to limit the chances of a lawsuit, you should start a Limited Liability Company to reduce your personal exposure to such a lawsuit. In most states this should cost around $100. If the LLC releases the game, it is the LLC that assumes liability. If the creator of the original game does sue, they can only be awarded the assets of your LLC (which, if you manage it correctly, should be limited to the game itself).
This will take a little bit of research, but I think it will be worth the time and money. As others have pointed out, even if you're legally clear, the original game's owner could get you into a lawsuit that is prohibitively expensive to defend. In that case you may want to cut your losses and offer them the rights to the game. If you have an LLC, they're sure to accept because the rights to the game is all they could acquire by suing (and suing would cost them money). If you don't have an LLC, they could pursue more of your personal assets as damages.
Just a nitpick, but people are usually sued for uploading, not downloading. If I upload something to you, then you upload that to a third person, I'm partly responsible for that third person getting the content. Even so, I think it's hard to argue that any individual is responsible for more than a few dozen people getting the content (unless they leaked content that wasn't for sale yet).
Taking that into consideration, perhaps your numbers should be knocked down an order of magnitude or more, but it still leaves a valid point (and perhaps it's a viable legal argument).
I always thought the reason it was cheaper to build a system from parts than buy a pre-built box was just a matter of scale. It's not hard to find a handful of parts that are on sale because they're beginning to be antiquated and retailers are trying to get rid of them, but I always assumed the price I paid for the parts was still above the normal wholesale price.
I can imagine that in bulk and with the right connections, you might be able to get these parts a bit below the normal wholesale price. The thing I have trouble with, is the idea that you can get enough of a discount to offset the cost of supporting random hardware configurations and software for several different CPU architectures.
Is this really cost effective?
In some less dense areas the +4 will be specific to a house. I can't imagine netflix would have released that and claimed their data was anonymous.
I'm not sure I completely agree with your proposal, but I definitely agree with the sentiment. A party with deep pockets shouldn't be able to force an innocent party into a settlement by making it cost prohibitive to defend yourself - that's extortion by my book.
I think a better alternative would be some kind of motion where a defendant can request that the judge order the plaintiff to pay legal fees. The defendant would need to be able to convince the judge that defending the suit is cost prohibitive and that an innocent but fiscally responsible party would be inclined to settle rather than defend against the suit. The judge could require the plaintiff to pay the defendant's legal fees, and if the judge finds in favor of the plaintiff the legal fees may be awarded back as well. Someone who knows they're at fault would still be inclined to settle out of court, but someone who believes he is innocent would have a viable means of defending himself.
I'm not sure I agree that what you suggest is the best approach (because it allows a corporation at least one frivolous suit before they have to start paying the other side's legal fees), but I definitely agree with the sentiment. Corporations with deep pockets shouldn't be able to force innocent people into settlements simply because it's too expensive to defend yourself - that's extortion.
I think a better option than what you suggest would be if the defendant could file a motion for coverage of legal fees. The defendant would have to convince the judge that the plaintiff's deep pockets make prohibitively expensive to defend the case, and that without the other side footing the legal fees the fiscally responsible action of an innocent party would be to settle. If the judge rules in favor of the plaintiff, he may decide to award the defendant's legal fees back to the plaintiff. If you know you're liable, you'd still be inclined to settle rather than rack up legal fees you know you'll have to pay off, but if you're innocent you'd have a viable means to defend yourself.
I disagree, because I think that would be a huge imposition on some people. When I was in high school I wrote a Half-Life server-side mod that I gave out for free. Being a teenager who was learning to code, I didn't have any kind of version control, I just kept editing the same source directory. Two years after my first release the project had moved on considerably and I most certainly did not have the original source. Two years after the last release I doubt I had the source for any version of the code.
I suspect this sort of thing is fairly common. I imagine there are lots of pieces of freeware or other cheap software where the company that made it either isn't around after two years or just isn't organized enough to produce the source for a two year old version of their software.
I hardly ever use my iPod with headphones. Usually it's plugged into speakers or my car stereo. In those cases the signal quality seems to correlate to the volume set on the player, but the volume itself is set by the amplifier. Admittedly, kicking the volume up to the player's 100% tends to distort the signal, but setting the player to a level that would be "safe" in headphones is short of the best signal.
You're not? I used MythTV for years, and while mythcommflag was probably 90% accurate, that extra 10% could make a substantial difference in the viewing experience. It's not a big deal when you accidentally end up with a commercial in the middle of your show, but it can make a huge difference if it cuts out 30 seconds of your TV show.
I'm with you on this one. I did the 30 day trial of Photoshop many years ago, and while I may not have been using its full potential, the stuff I did with it was pretty intuitive. I've used GIMP for my (minimal) image manipulation needs for several years, and only now that I have quite a bit of experience do I find it as easy to use as I found Photoshop the first time I opened it. For the more complex functions, GIMP may be as intuitive as Photoshop, but for the basic stuff GIMP has a steep learning curve.
Similar things have happened with other products like Audacity. My mother-in-law runs a dance studio and was banging ahead against the software she was using to mix tracks for a recital. I suggested Audacity, but she was convinced that because it was free it couldn't possibly be better than what she had. The next year I saw she was using Audacity and commented that I saw she had taken my advice. She told me that this wasn't a free program, that it had come with some piece of hardware she'd purchased. I shook my head and moved on, but I found it interesting that audacity was gaining a user base through inclusion with hardware.
I pay $8.99 a month for a subscription to Netflix, which gets me 1 DVD at a time and unlimited access to Netflix watch instantly. When I started using Hulu, I looked to see if there was some way I could pay a monthly fee to get rid of ads and was stunned that there wasn't (though it sounds like there may be soon). I'm happy to pay a small monthly fee for the shows I want to watch rather than paying $40 a month for the same shows plus several dozen channels I'm never going to watch.
Don't take this the wrong way, I encrypt my laptop and would encourage almost everyone to do the same, but you still have to be security conscious.
First, it's a zero-knowledge web application. The web server doesn't know your username or password for its own site, let alone any of the passwords it stores. Everything is encrypted and decrypted on the client using javascript. It's open source and I've actually spent some time looking through the code, so I trust it.
The offline copy is another great feature. You can download an HTML file that operates just like the normal web site, except that you can't add passwords to it. I use the offline copy for every day use because it's a bit snappier and takes the load away from Clipperz servers. In the event that clipperz ever disappears, I still have my offline copy so my passwords aren't lost.
It lets you generate passwords randomly, so I generate a new password for every site I visit. The passwords are long strings with random characters from all over the keyboard, so they're stronger than something a person could think up or remember. I have a different password for every site, so if one gets compromised by a poorly designed website, I don't have to worry about changing my password on a dozen other sites.
It has a sidebar version that works in several browsers. It provides a list of links you can click to automatically log in to any website you have an account on.
I've recommended clipperz to several friends and family members, and I know of at least one who actually uses it frequently (the rest just have a short list of fairly weak, memorable passwords they use on a much longer list of sites).
If you need to make sure you have legal control over your data, your best bet is to keep your data out of the cloud.
I'm really hoping the rumors about 2.0 having multitouch support will pan out. Android does pretty well with only one contact point, but it could still benefit from multitouch support.
Other than that, both the myTouch and the G1 have an accelerometer which is used by a number of apps and built-in features of the phone. They have GPS, network, and wifi based positioning, which is pretty accurate even with my GPS receiver turned off. They have a built in compass, and there are apps that make use of it. It comes with an Amazon mp3 client, and you can put music on it with a file browser or just about any non-itunes music player.
I don't know what the OP was talking about, as only two of his points have any merit at all.
And that's the point TheLink was trying to make. It would be far simpler to tell the browser not to accept javascript in a certain block of code than it is to explore all the possible exploits that could be leveraged against your alternative markup language. There are hundreds if not thousands of places you can make mistakes, and it could be remedied by a single mechanism that prevented javascript from existing in certain blocks of code.
I am curious how much difference there would have been on a database system that would actually be running in a server environment. Ubuntu definitely got owned by that metric, but SQLite is hardly exemplary of a production database.
So not only do you continue to own your content, you even retain the right to revoke their license to it.
Me too. I'm assuming we'll be able to get back to the orange and brown, it just won't be the default. I'm personally quite fond of the brown and orange (but what do I know? I'm colorblind...).
I plan to upgrade directly from the Ubuntu servers, but I'm only going to hit their servers once for the three machines I'm upgrading. I use apt-cacher, which stores packages on the local network once they've been downloaded by something on the network, then sends out the cached version when it's requested again. It doesn't help much for the odd day-to-day package installation, but it makes significant upgrades much faster after the first system. You have to configure all of the systems to use the proxy, but it's easy to setup. If you run more than one or two systems, I'd definitely look into it.