If I write a program, by default (per US copyright law), you have *no* right to use it, *no* right to the source code, *no* right to the binary. You have no right to to modify that source code, you have no right to use that source code in whole or in part in your own program.
That is copyright law.
I can choose to not release it at all, release it under one or more licenses, or to release it under public domain.
If I release it under GPL, you have the right to use the binary, you have the right to use the source. You simply don't have the right to modify that source and distribute a binary-only version of your modifications. Now, pay attention to this part: You have not lost the right to distribute a binary-only version of my modified source, because you never had that right in the first place.
Now, I might choose to release it to YOU under the GPL, to my customers as BSD, and to my grandmother under a Microsoft-type license (no right to the source, no right to redistribute, etc). That means I've granted my customers more rights then I've granted you. But you have still not lost any rights, or had any right restricted, because until I gave you some rights (under the GPL) you had none to begin with.
As far as "right" being permission vs correct, this entire post uses it in the "permission" context.
Lastly, you seem to be somewhat confused by the "freeware" license -- Freeware and Public Domain mean very different things. If I write a program and release it as freeware it typically means free to you to use and free to distribute, but it does not grant you any right to make changes, nor do you have the rights to the source.
If I release the binary as public domain, you can make changes, distribute, decompile, whatever, but you don't automatically get the source from me.
If I release the source as public domain, then I have basically given you the right to do anything you want.
In other words, the GPL gives you certain rights you did not have, but it places conditions on which you can use those rights.
If you don't like it, you have a simple alternative: you don't use my code, you right it yourself from scratch.
So? I can't make voice phone calls with my broadband without additional hardware or software, and paying someone to terminate the call to the PSTN network.
Without being rude, why is it unreasonable to expect a deaf person to buy a TTY terminal (phone) or a modem?
The concept is simple: If you CHOOSE to quit, then you need to accept the consequences. If you lose your job, especially through no fault of your own, then society will help you out.
I'm not saying I agree with it, but I know too many people (outside the computer industry) that work just long enough to get EI, manage to get themselves downsized (usually they're just a giant pain to be around, but they don't do anything fireable) and live off my dollar for the next few months.
It's hit and miss, they have a few very good techs, mostly at tier 2/3, but they don't normally take frontline calls.
They also have a whole lot of techs which were trained to take 611 calls, given about a day's worth of training and set loose on the internet side as well.
I was one of those folks on the Cadvision side of the migration. I fought long and hard to maintain some of what made Cadvision great (true static IPs,/29 or larger subnets available upon request/justification, 7Mb/1.5Mb over dry copper, 7KM+ DSL serving distances with MVL, all of which TELUS trashed)
Sure... But while the processor's performance is directly RELATED to it's clock speed, there are other factors involved.
If you've ever compared a 386DX/33 against a 486/25, you'll notice the 486 is faster even though it has a slower clock speed.
Why? In laymans terms, the clock speed is how often you can tell the CPU *what* to do. The other factor is how many cycles it takes the CPU to carry out the instruction before the CPU is ready to do something else.
DX/50s, in particularly, were *extremely* fast in their day because of the 50Mhz system bus - for nearly all high-end purposes they were faster than DX2/66s)
Okay, I was gonna let your post go until I saw that little gem... 50MHz system bus? -- The fastest the 486 line's bus got was 33MHz, and they went back to 25MHz system bus for the DX2 (50MHz CPU clock) and DX4 lines
Wait states are a function of the memory controller, not the CPU.
Sure. But what exactly is waiting on the memory? Your joystick?
The problem with TELUS is that none of their support scripts end with "Problem is on TELUS' side, send for resolution" or even "Transfer to someone who knows what a 'DHCP' is without looking it up"
They all end in "Annoy the customer until they hang up" or "Reintall Windows" or something equally useless.
Many of them still insist you reboot your PC when the DSL light on the modem is out, simply because their script starts off with a reboot before it even addresses the concern.
There are a couple legal differences. One problem is that you cannot legally copy a copy.
I can lend you my original Metallica CD, you can copy it to CD, convert it to MP3, do whatever you want, return the CD, and keep your copies.
However, if I lend you my COPIED Metallica CD, you cannot do any of the above. In addition, I MAY have broken the law by lending the CD, although I don't think the CIRA would get far in court with that one.
Unless you are serving uncompressed data from the original media format, you're liking copying a copy in some way, shape or form. Now, if you were to read from CD, encode into MP3 in real time and share it, you MIGHT survive a legal challange by arguing that the MP3 compression was a form of encoding for transport. But whether you'd be able to pull it off saying your hard drive is a cache or something similar, I don't know.
In any event, if you were only sharing media that you own, my personal feeling is that the CRIA would just drop it rather then continuing to persue you, especially if you looked like you were going to put up a fight.
I have an unencrypted cordless phone kicking around, and I don't think twice about using it.
Why?
Frankly, my conversations are too boring for anyone to care, and if they really wanted to listen in, they'd go into my backyard with a little battery powered radio transmitter and install it onto the telephone patch panel outside.
That being said, most of my conversations are on my desk phone, but that's more out of convinience then security concern.
Do I give out my credit card over the phone? I can't remember the last time I did, I buy stuff on the net. However, if I did give it out, I wouldn't worry about it. If you want credit card numbers, you'll have better luck getting a minimum wage retail job for two weeks and copying the receipts then to listen aimlessly to cordless phone calls until somebody gives out a credit card number.
Would I read out my SIN (SSN, for the American readers)? No. That one is need to know, and anybody that needs to know will meet me in person.
When they ask "what's your (home) phone number?" do you give your cell phone, or start off with some "I don't have a phone, but umm... well... uhhh... I have a cell phone if you want it" crap?
I go back and forth about having a landline, but I only ever give out my cell. When I have a landline, the number forwards to my landline when the cell is off. When I don't, I leave the cell on all the time.
In my experience, if you just give your cell phone number like you would give your home number on application forms, and when people ask, you won't run into any problems. If you tell people you don't have a landline, they get weirded out.
Why buy from Verisign? If we're talking a telco deployed system (Vonage, etc) have them sign it.
Now, if you're talking a "every man runs his own VoIP" environment, or one which doesn't have a small number of key players, then certificates are more important, but even then, a web of trust model could help.
Slashdot Mirror
I'll type this slowly so I don't confuse you.
If I write a program, by default (per US copyright law), you have *no* right to use it, *no* right to the source code, *no* right to the binary. You have no right to to modify that source code, you have no right to use that source code in whole or in part in your own program.
That is copyright law.
I can choose to not release it at all, release it under one or more licenses, or to release it under public domain.
If I release it under GPL, you have the right to use the binary, you have the right to use the source. You simply don't have the right to modify that source and distribute a binary-only version of your modifications. Now, pay attention to this part: You have not lost the right to distribute a binary-only version of my modified source, because you never had that right in the first place.
Now, I might choose to release it to YOU under the GPL, to my customers as BSD, and to my grandmother under a Microsoft-type license (no right to the source, no right to redistribute, etc). That means I've granted my customers more rights then I've granted you. But you have still not lost any rights, or had any right restricted, because until I gave you some rights (under the GPL) you had none to begin with.
As far as "right" being permission vs correct, this entire post uses it in the "permission" context.
Lastly, you seem to be somewhat confused by the "freeware" license -- Freeware and Public Domain mean very different things. If I write a program and release it as freeware it typically means free to you to use and free to distribute, but it does not grant you any right to make changes, nor do you have the rights to the source.
If I release the binary as public domain, you can make changes, distribute, decompile, whatever, but you don't automatically get the source from me.
If I release the source as public domain, then I have basically given you the right to do anything you want.
In other words, the GPL gives you certain rights you did not have, but it places conditions on which you can use those rights.
If you don't like it, you have a simple alternative: you don't use my code, you right it yourself from scratch.
True enough. However, TTY-over-IP might not be the right route to go, maybe SMS or something similar which authenticates the sender to some extent.
How do deaf people without a computer send or receive IP packets?
They probably already own TTY hardware, so the point is moot.
Fax? TTY is basically realtime, fax is not.
Not only that, but try faxing Walmart and asking for their hours, see how fast you get a reply.
So? I can't make voice phone calls with my broadband without additional hardware or software, and paying someone to terminate the call to the PSTN network.
Without being rude, why is it unreasonable to expect a deaf person to buy a TTY terminal (phone) or a modem?
Unless I'm mistaken, GPL does not restrict any rights. Under copyright law you have *no* rights to begin with, beyond fair use.
The only rights you're given are those which the GPL explicitly grants you (Or rather, the copyright holder grants you, as listed in the GPL)
The concept is simple: If you CHOOSE to quit, then you need to accept the consequences. If you lose your job, especially through no fault of your own, then society will help you out.
I'm not saying I agree with it, but I know too many people (outside the computer industry) that work just long enough to get EI, manage to get themselves downsized (usually they're just a giant pain to be around, but they don't do anything fireable) and live off my dollar for the next few months.
Sure. Microsoft has proved themselves to be evil (And I happen to prefer W2K as a server platform)
Google hasn't (yet?)
What about them? Are backups required for this type of application if you have a sufficiently redundant file system (Which google does!)
Okay, maybe you should give them the discman? That's punishment enough
Nope, but the robberies are part of the campaign, plus it keeps production costs down.
Just hit them with the damn discman
Well sure, but think about how many different breakfast cereals are available!
It's hit and miss, they have a few very good techs, mostly at tier 2/3, but they don't normally take frontline calls.
/29 or larger subnets available upon request/justification, 7Mb/1.5Mb over dry copper, 7KM+ DSL serving distances with MVL, all of which TELUS trashed)
They also have a whole lot of techs which were trained to take 611 calls, given about a day's worth of training and set loose on the internet side as well.
I was one of those folks on the Cadvision side of the migration. I fought long and hard to maintain some of what made Cadvision great (true static IPs,
Sure... But while the processor's performance is directly RELATED to it's clock speed, there are other factors involved.
If you've ever compared a 386DX/33 against a 486/25, you'll notice the 486 is faster even though it has a slower clock speed.
Why? In laymans terms, the clock speed is how often you can tell the CPU *what* to do. The other factor is how many cycles it takes the CPU to carry out the instruction before the CPU is ready to do something else.
DX/50s, in particularly, were *extremely* fast in their day because of the 50Mhz system bus - for nearly all high-end purposes they were faster than DX2/66s)
Okay, I was gonna let your post go until I saw that little gem... 50MHz system bus? -- The fastest the 486 line's bus got was 33MHz, and they went back to 25MHz system bus for the DX2 (50MHz CPU clock) and DX4 lines
Wait states are a function of the memory controller, not the CPU.
Sure. But what exactly is waiting on the memory? Your joystick?
Preferences will let you assign whatever modpoints to AC postings you want. Set AC to -2 and you'll probably not see much more AC crap.
The problem with TELUS is that none of their support scripts end with "Problem is on TELUS' side, send for resolution" or even "Transfer to someone who knows what a 'DHCP' is without looking it up"
They all end in "Annoy the customer until they hang up" or "Reintall Windows" or something equally useless.
Many of them still insist you reboot your PC when the DSL light on the modem is out, simply because their script starts off with a reboot before it even addresses the concern.
There are a couple legal differences. One problem is that you cannot legally copy a copy.
I can lend you my original Metallica CD, you can copy it to CD, convert it to MP3, do whatever you want, return the CD, and keep your copies.
However, if I lend you my COPIED Metallica CD, you cannot do any of the above. In addition, I MAY have broken the law by lending the CD, although I don't think the CIRA would get far in court with that one.
Unless you are serving uncompressed data from the original media format, you're liking copying a copy in some way, shape or form. Now, if you were to read from CD, encode into MP3 in real time and share it, you MIGHT survive a legal challange by arguing that the MP3 compression was a form of encoding for transport. But whether you'd be able to pull it off saying your hard drive is a cache or something similar, I don't know.
In any event, if you were only sharing media that you own, my personal feeling is that the CRIA would just drop it rather then continuing to persue you, especially if you looked like you were going to put up a fight.
I have an unencrypted cordless phone kicking around, and I don't think twice about using it.
Why?
Frankly, my conversations are too boring for anyone to care, and if they really wanted to listen in, they'd go into my backyard with a little battery powered radio transmitter and install it onto the telephone patch panel outside.
That being said, most of my conversations are on my desk phone, but that's more out of convinience then security concern.
Do I give out my credit card over the phone? I can't remember the last time I did, I buy stuff on the net. However, if I did give it out, I wouldn't worry about it. If you want credit card numbers, you'll have better luck getting a minimum wage retail job for two weeks and copying the receipts then to listen aimlessly to cordless phone calls until somebody gives out a credit card number.
Would I read out my SIN (SSN, for the American readers)? No. That one is need to know, and anybody that needs to know will meet me in person.
When they ask "what's your (home) phone number?" do you give your cell phone, or start off with some "I don't have a phone, but umm... well... uhhh... I have a cell phone if you want it" crap?
I go back and forth about having a landline, but I only ever give out my cell. When I have a landline, the number forwards to my landline when the cell is off. When I don't, I leave the cell on all the time.
In my experience, if you just give your cell phone number like you would give your home number on application forms, and when people ask, you won't run into any problems. If you tell people you don't have a landline, they get weirded out.
Sure, with a central server it's easy.
It's not so each if you want to establish a direct VoIP call with both people behind a NAT router that they don't control.
Why buy from Verisign? If we're talking a telco deployed system (Vonage, etc) have them sign it.
Now, if you're talking a "every man runs his own VoIP" environment, or one which doesn't have a small number of key players, then certificates are more important, but even then, a web of trust model could help.
While that's true, I'm not sure you'd be able to sue until/unless you had actual damages.
I might be wrong though, not only does IANAL apply, but I'm not even American.
Figures. I thought they used to have a (800) number back when I was a personal account.
Either way, I'm business now, which explains why I don't know about their current personal support numbers.