But other people already have that data, and thus the first person to have it has a copyright, no? You were certainly not the first person to know your phone number, the phone company was. So they (since they had it in a database) own the copyright for that record.
Bought a house? First person to put that in a list owns it. IE. your realtor.
Maybe we computer saavy people would say "hold it, while I enter that into MY databse. Ok, now, you can hit return." but the average Joe would lose rights to his own darn address.
My assumption from what I've seen is that this law copyrights the effort, not individual datums, but if it does, I'm pretty sure private citizens wouldn't benefit from even the absurd case.
Huh? What? I think you're missing something here. And further, from my experience with technical classes in college, most of the folks responding to him missed something too.
Our little poster here has decided to be a technical person. That means he's gonna be a have, not a have not, money-wise (current IT job situation notwithstanding). He's gonna make more money than most Americans, and that starts NOW.
Our poster will get a job working in someone's lab keeping the machines running, or will work for campus computing, and if he's any good, he'll make a lot more than the crap jobs you're thinking of. Those are for OTHER people -- people without valuable skills.
(For the record, campus computing folk may make less than individual labs where you'll be more valued as a person. If the professor you hire on with turns out to be a bastard, find another job immediately. Avoid work study positions, if you can -- They tend to pay lower than non-work study. Try to work in a position where you're the only guy running the machines, but cultivate friends who work elsewhere on campus so you have a network of people who can help you when you can't figure it out. There's good reason for this: You'll learn more -- both about computing and about the research of the people you work for.)
Furthermore, working in a lab, (for instance a high-energy physics lab) he'll figure out that studying computers is for losers. Yes, LOSERS. He'll learn everything he needs to get a great job in IT by keeping those machines running, and working on open source projects that interest him. (Having your name on a known open source package opens doors like CRAZY, people.) He'll be bored in his CS (or worse, MIS) classes and he'll find that the Physics lab he works in, or the Psychology Lab, or the Econ department, or Hell, anywhere he works will educate him better than sitting on his ass, hearing stuff about pointers that he already knew or could figure out on his own.
If he's smart, he'll get a degree in something other than CS and he'll make more doing CS work than does someone who can't think, can't talk, and has no common vocabulary with the educated world -- that is, he'll make more with any liberal arts or sciences degree than he would with a CS or MIS degree, unless he goes on to get an MBA as well.
The stuff you don't know anything about is the reason to go to college, not the stuff you already know and already have a huge interest in.
Sit in on Tech classes, Poster, but don't waste your valuable credit hours on them. They'll point the way for you to work on your own, but they won't stretch you. You go to college to be stretched, not capped.
A class action suit against SCO would not pay for the Linux and GNU community's work. They don't have enough money.
Since individuals made these decisions, can a class action suit include name those individuals as defendants, along with SCO as a corporate entity, so that there will be enough to pay for the development effort which SCO has stolen?
SCO's only going to be able to cough up tens of millions at the most, and they'll spend every asset of the company fighting this, such that a the community might win only a notice of bankruptcy. Not so if the personal fortunes of the decision-making officers are included.
The key is not to whitelist, blacklist, etc. The key is to make mass emails impossible.
The answer should be obvious. What do you care if your email to your Aunt Millie takes 20 seconds to send?
All sendmail or other mailers should demand a pain-toll before allowing you to pass. The toll should be plug-in, so that while there's always the first (common) one to fall back on and so new ways to get approval (such as $-based, blacklists, whitelists, etc.) can be added.
But at core, the common one should be a painful calculation -- a large public/private key handshake, for example. If the spammer has to buy a Cray to send out 10000 emails, then WE WIN.
The problem with this is that it demands a sendmail replacement. Everybody needs to have the sending component to get email to those with a pain-toll-based recieve version.
But the advantage is huge. Imagine a world where you can decide to allow all emails in for either:
a. A 10 cent donation to UNICEF
b. Those with a public key in your database (known firends/whitelist)
c. Those willing to do a 10000 byte key encrypt/decrypt function (one which goes fast on YOUR end).
SPAM as we know it simply GOES AWAY.
I would hasten to add that actual $-based systems can be added but are entirely optional.
Hey, I have $200 bucks here for her countersuit. I think a lot of us have SOME money. At least she's owed attorney fees, as this was a lawsuit instigated without due dilligence.
But to me, it sounds like Libel (or would that be Slander). They've called her a thief in public without facts and have refused to apologize, saying, in effect -- "We still suspect you."
I'll certainly up my contribution to the EFF by that $200 if they'll sue on her behalf.
Slashdot Mirror
But other people already have that data, and thus the first person to have it has a copyright, no? You were certainly not the first person to know your phone number, the phone company was. So they (since they had it in a database) own the copyright for that record.
Bought a house? First person to put that in a list owns it. IE. your realtor.
Maybe we computer saavy people would say "hold it, while I enter that into MY databse. Ok, now, you can hit return." but the average Joe would lose rights to his own darn address.
My assumption from what I've seen is that this law copyrights the effort, not individual datums, but if it does, I'm pretty sure private citizens wouldn't benefit from even the absurd case.
I assume NONE.
Which means it's security through obscurity and we all know how long that works.
Huh? What? I think you're missing something here. And further, from my experience with technical classes in college, most of the folks responding to him missed something too.
Our little poster here has decided to be a technical person. That means he's gonna be a have, not a have not, money-wise (current IT job situation notwithstanding). He's gonna make more money than most Americans, and that starts NOW.
Our poster will get a job working in someone's lab keeping the machines running, or will work for campus computing, and if he's any good, he'll make a lot more than the crap jobs you're thinking of. Those are for OTHER people -- people without valuable skills.
(For the record, campus computing folk may make less than individual labs where you'll be more valued as a person. If the professor you hire on with turns out to be a bastard, find another job immediately. Avoid work study positions, if you can -- They tend to pay lower than non-work study. Try to work in a position where you're the only guy running the machines, but cultivate friends who work elsewhere on campus so you have a network of people who can help you when you can't figure it out. There's good reason for this: You'll learn more -- both about computing and about the research of the people you work for.)
Furthermore, working in a lab, (for instance a high-energy physics lab) he'll figure out that studying computers is for losers. Yes, LOSERS. He'll learn everything he needs to get a great job in IT by keeping those machines running, and working on open source projects that interest him. (Having your name on a known open source package opens doors like CRAZY, people.) He'll be bored in his CS (or worse, MIS) classes and he'll find that the Physics lab he works in, or the Psychology Lab, or the Econ department, or Hell, anywhere he works will educate him better than sitting on his ass, hearing stuff about pointers that he already knew or could figure out on his own.
If he's smart, he'll get a degree in something other than CS and he'll make more doing CS work than does someone who can't think, can't talk, and has no common vocabulary with the educated world -- that is, he'll make more with any liberal arts or sciences degree than he would with a CS or MIS degree, unless he goes on to get an MBA as well.
The stuff you don't know anything about is the reason to go to college, not the stuff you already know and already have a huge interest in.
Sit in on Tech classes, Poster, but don't waste your valuable credit hours on them. They'll point the way for you to work on your own, but they won't stretch you. You go to college to be stretched, not capped.
A class action suit against SCO would not pay for the Linux and GNU community's work. They don't have enough money.
Since individuals made these decisions, can a class action suit include name those individuals as defendants, along with SCO as a corporate entity, so that there will be enough to pay for the development effort which SCO has stolen?
SCO's only going to be able to cough up tens of millions at the most, and they'll spend every asset of the company fighting this, such that a the community might win only a notice of bankruptcy. Not so if the personal fortunes of the decision-making officers are included.
The key is not to whitelist, blacklist, etc. The key is to make mass emails impossible.
The answer should be obvious. What do you care if your email to your Aunt Millie takes 20 seconds to send?
All sendmail or other mailers should demand a pain-toll before allowing you to pass. The toll should be plug-in, so that while there's always the first (common) one to fall back on and so new ways to get approval (such as $-based, blacklists, whitelists, etc.) can be added.
But at core, the common one should be a painful calculation -- a large public/private key handshake, for example. If the spammer has to buy a Cray to send out 10000 emails, then WE WIN.
The problem with this is that it demands a sendmail replacement. Everybody needs to have the sending component to get email to those with a pain-toll-based recieve version.
But the advantage is huge. Imagine a world where you can decide to allow all emails in for either:
a. A 10 cent donation to UNICEF
b. Those with a public key in your database (known firends/whitelist)
c. Those willing to do a 10000 byte key encrypt/decrypt function (one which goes fast on YOUR end).
SPAM as we know it simply GOES AWAY.
I would hasten to add that actual $-based systems can be added but are entirely optional.
But to me, it sounds like Libel (or would that be Slander). They've called her a thief in public without facts and have refused to apologize, saying, in effect -- "We still suspect you."
I'll certainly up my contribution to the EFF by that $200 if they'll sue on her behalf.