some of their stories? they bring in scully's whole family pretty much...
plus, that would have been a bit messed like luke and leia in star wars ("you're my sister" "i know. somehow i've always known [even when i kissed you back in episode 4]" or whatever).
The profs have long had a similar cheat detection tool, although I've heard it's somewhat more sophisticated in that it even checks code for being the same with different variable names and that sort of trick. Supposedly it catches code blocks that are arranged in a different order too.
Then again, I'm not on the inside, so a lot of that could just be the professors trying to scare us students into not cheating....;)
As a side note, though, in the courses there, a lot of the time, sharing code with each other was allowed as long as it was cited.
I don't know about the rest of you, but when I use open source software, I don't personally verify that the software is written to my own personal specs.
I actually use the software under the mentality that the source is publicly available, so some other people (who are both more qualified and care more than I) have had the opportunity to review the code and have possibly improved it.
Thus the responsibility for the correct operation of the open source code is partially that of the original writer, the whole open source community, and the user. Since this is such a vague group, it's difficult to hold anyone financially liable for problems. ("Are you a member of the open source community?" "If you're here to sue me, no, I'm not.")
However, it seems like common sense that open source software is provided with a "use at your own risk" type agreement and any trust you have in the software is the same as trusting this vague open source community entity. I'm not familiar with the nuances of the different licenses, but if the "use at your own risk is not explicitly stated in the public license, maybe it should be. If it already is, then that's a settled matter.
In the case of closed source software, there is a very clear boundary of who wrote the software and thus who may be held responsible for any errors or damage the software causes.
Next, most closed source software is probably sold for a profit. Thus it is the responsibility of the user also to demand some sort guarantee or warranty or whatnot from the software provider before handing over money for a product that may or may not be suitable for the user's needs. If security is a key need, the user is supposed buy the software that is guaranteed to be secure.
If the software provider sells a product as "secure" for instance, the user has a right to expect the product to be "secure" as advertised. If it is not, however, the software provider should be held responsible for the same liability as any company that provides defective goods. (i.e. the consumer can sue them for damages caused by defects etc.)
That's why I believe closed source software providers should be held liable for damages caused by defects in their products, whereas the open source community cannot be.
heh, it would just be fun to see how far people could twist the dmca until we finally got it repealed.;)
i wonder if we could attack the fingerprint database too since it would fall under the same category of reverse engineering your prints into another format and circumventing the current storage mechanism.
heh, then imagine if this lawsuit were a class action lawsuit. to claim shares of the payout, criminals would have to come and get them. (much like the classic tales of criminals being suckered out of hiding by letting them know they've won some sort of prize.);)
saw some article on tv stating that the u.s. actually only gets 10% of its oil from the middle east anyways (like 50% domestic, 10% mexico, 10% canada, 10% venezuela, 10% other, 10% middle east or something like that.). the television article pointed out that our buddies europe and japan get much more of their oil from the middle east, so that's sort of why we end up sticking our noses into the middle east conflicts.
as for that comment about our taxes being higher than before the american revolution, our current taxes are still lower than the current taxes in britain (as time has progressed, both governments have begun to provide more services). =)
the full win2k source? errr, my memory is rusty, wasn't that some 40 million lines of code or something?
of course the kernel part wouldn't be nearly that big, but i still shudder to think how big it might be.
as for uc berkeley, we just used trusty old nachos too. one prof in the past has made folks work on bsd (fittingly), but running nachos on top of solaris seems to be much much easier.
It would be nice if things worked out so that gravity would be pushing too, but it's gonna be pretty hard to show this. It's like the search for magnetic monopoles just so that Maxwell's equations look nicer.
Actually, I thought this was a fairly common physics demonstration. I even seem to recall some silly kid's game show I saw once in which they were levitating ping pong balls with hair dryers to accomplish something or other. It works.
Slashdot Mirror
or he could have just gone to a warez site and grabbed a pirated copy of the american version.
some of their stories? they bring in scully's whole family pretty much...
plus, that would have been a bit messed like luke and leia in star wars ("you're my sister" "i know. somehow i've always known [even when i kissed you back in episode 4]" or whatever).
The profs have long had a similar cheat detection tool, although I've heard it's somewhat more sophisticated in that it even checks code for being the same with different variable names and that sort of trick. Supposedly it catches code blocks that are arranged in a different order too.
;)
Then again, I'm not on the inside, so a lot of that could just be the professors trying to scare us students into not cheating....
As a side note, though, in the courses there, a lot of the time, sharing code with each other was allowed as long as it was cited.
I don't know about the rest of you, but when I use open source software, I don't personally verify that the software is written to my own personal specs.
I actually use the software under the mentality that the source is publicly available, so some other people (who are both more qualified and care more than I) have had the opportunity to review the code and have possibly improved it.
Thus the responsibility for the correct operation of the open source code is partially that of the original writer, the whole open source community, and the user. Since this is such a vague group, it's difficult to hold anyone financially liable for problems. ("Are you a member of the open source community?" "If you're here to sue me, no, I'm not.")
However, it seems like common sense that open source software is provided with a "use at your own risk" type agreement and any trust you have in the software is the same as trusting this vague open source community entity. I'm not familiar with the nuances of the different licenses, but if the "use at your own risk is not explicitly stated in the public license, maybe it should be. If it already is, then that's a settled matter.
In the case of closed source software, there is a very clear boundary of who wrote the software and thus who may be held responsible for any errors or damage the software causes.
Next, most closed source software is probably sold for a profit. Thus it is the responsibility of the user also to demand some sort guarantee or warranty or whatnot from the software provider before handing over money for a product that may or may not be suitable for the user's needs. If security is a key need, the user is supposed buy the software that is guaranteed to be secure.
If the software provider sells a product as "secure" for instance, the user has a right to expect the product to be "secure" as advertised. If it is not, however, the software provider should be held responsible for the same liability as any company that provides defective goods. (i.e. the consumer can sue them for damages caused by defects etc.)
That's why I believe closed source software providers should be held liable for damages caused by defects in their products, whereas the open source community cannot be.
a compiler that will handle misspellings and if-than's?
;) the result just might not be what you expect. heh
i thought pl/1 was supposed to compile anything you gave it.
in case you're wondering, there is already a free standard for animated images that support lossy (jpg) and lossless (png) component images. =)
png info is at: http://www.libpng.org/pub/png/
mng info is at: http://www.libpng.org/pub/mng/
heh, it would just be fun to see how far people could twist the dmca until we finally got it repealed. ;)
;)
i wonder if we could attack the fingerprint database too since it would fall under the same category of reverse engineering your prints into another format and circumventing the current storage mechanism.
heh, then imagine if this lawsuit were a class action lawsuit. to claim shares of the payout, criminals would have to come and get them. (much like the classic tales of criminals being suckered out of hiding by letting them know they've won some sort of prize.)
so 1 and 2 really are absurd. ;)
however, i'm voting for hoax at the moment. hehehe. when they release a beta that i can try, i'll believe it.
i don't understand how people expect to detect encrypted messages that are then steganographically hidden in images anyways.
in theory if you encrypt your message via any good standard method, it should result in something that even statistically looks like random garbage.
if management makes you play a stupid social game, then isn't making management the enemy giving people something to bond about.
wow hope no one takes that quote out of context. ;)
I'd like to see the legal definition of a "message board" before being too impressed by a ruling like this.
saw some article on tv stating that the u.s. actually only gets 10% of its oil from the middle east anyways (like 50% domestic, 10% mexico, 10% canada, 10% venezuela, 10% other, 10% middle east or something like that.). the television article pointed out that our buddies europe and japan get much more of their oil from the middle east, so that's sort of why we end up sticking our noses into the middle east conflicts.
as for that comment about our taxes being higher than before the american revolution, our current taxes are still lower than the current taxes in britain (as time has progressed, both governments have begun to provide more services). =)
the full win2k source? errr, my memory is rusty, wasn't that some 40 million lines of code or something? of course the kernel part wouldn't be nearly that big, but i still shudder to think how big it might be. as for uc berkeley, we just used trusty old nachos too. one prof in the past has made folks work on bsd (fittingly), but running nachos on top of solaris seems to be much much easier.
It would be nice if things worked out so that gravity would be pushing too, but it's gonna be pretty hard to show this. It's like the search for magnetic monopoles just so that Maxwell's equations look nicer.
Actually, I thought this was a fairly common physics demonstration. I even seem to recall some silly kid's game show I saw once in which they were levitating ping pong balls with hair dryers to accomplish something or other. It works.