Hey Luke...I decided to take up Lessig's challenge as well. I am kicking it off by cancelling my AOL account, and I will donate the amount of money I would have spent on that account for one year to the EFF. That comes out to 19.95 x 12 = $293.40.
I'll give AOL a call, let them know why I'm cancelling the account and where the money will be going, and then post my notes on that call in my journal!
The web page for my slashdot journal is "A HREF="http://slashdot.org/~Locke!Erasmus/journal/" >here . Please do not list my email address, just the link to my slashdot journal.
the thing to remember here is that you haven't done anything wrong, and I wouldn't cave in to them just because they're being intimidating. My gut feeling, knowing as little about the situation as I do, is that the folks who are threatening you fear having to GPL their derived products as well, so they're employing bsa or riaa-style tactics on you.
if it comes down to it, set up a paypal account. I will be happy to donate to any legal fund set up to fight these guys.
I think hahnfield might have opted to leave his website and the identity of his project out to avoid the slashdot effect. It seems to be nailing his site at the moment.
I would just wish to clarify something - about making the software company publish the code under the GPL.
I don't think hahnfield actually made the software company do anything. It was a settlement. The software company chose on their own to release the code under GPL to avoid the hassle of going to court - because unlike the guy working on open source code, a court actually can make the software company do something.
Let me get this straight...are they saying that their code is contained in the original GPL product that you put together, and it must be removed or they will ($gratuitous_threat)?
Or are they saying they think their code is included in the derived product that you just settled on, that is soon to be released under the GPL?
There's a difference there. If it's your original product, how did their proprietary stuff get there? Did you hack into their networks, swipe their proprietary code, and add it to your open source project?
If it's the derived product that is being released as part of the settlement, the "how did it get there" question applies, but I'd also ask some more questions. How do they know they have code there? Did they collaborate on the add-on? Did they at any time give any code for any reason to the person who is settling with you? Under what terms?
There's also this point: You're not releasing the code under the GPL. The developer is the derived product is releasing it. Why would all these other companies want to block him from distributing his project for free, by coming after you?
($gratuitous_IANAL_message), but it seems to me like they might have GPL-protected code in the products they've derived off your project, so it seems like they are using nasty and unpleasant tactics to try to scare you into backing off or whatever.
Get a good IP lawyer, and if one isn't available I'd definitely be hooking up with the FSF to see if they can provide any assistance.
would be Avery Brooks, AKA Captain Benjamin Sisko...and he should know perfectly well that his flying cars are in front of the bluescreen or greenscreen or whatever!
There are a couple of ideas that I believe any NOC engineer should hold close if he or she wants to keep it together:
1. When trying to resolve an outage, don't believe any piece of information that anyone (vendor, peer, SA department) gives you until you can prove it to yourself. People make assumptions, which are often wrong.
2. Don't close a trouble ticket until you know the problem is fixed and it isn't coming back. If your NOC has three or four tickets on the same outage within a week or two, then you've got two problems: one with your gear, and one with your process.
3. Stay away from red bull. That crap is evil.
4. Find your own niche, a particular set of NOC duties that you excel in. Find some subject matter on which you can be an expert.
5. Just like they say you should check your problems at the door when you come to work, check your work at the door when you go home.
6. Be nice to people. There is no reason to be a jerk or ugly with people whether they are a vendor or a phone monkey in the call center. Sometimes it is harder to be nice when there's a high-profile outage going on and you aren't getting instant results, but it will pay off when that vendor or TS supe or whoever pulls your hiney out of the fire later on.
7. CSM aka head of lettuce is a pimp.:)
at the request of Microsoft or John Ashcroft?
Aw shucks, does it matter?
On the matter of holidays
on
Howl-o-ween
·
· Score: 1
I like halloween, but I like the weekend before that, Fall Back, even better!
I am all about an extra hour of sleep:)
On the matter of vendors
on
Nosy Vendors?
·
· Score: 3, Insightful
It is entirely possible that he was curious about exactly what you wanted the system to do, and trying to come up with the best deal he could make you....
of course, if he was confrontational about it, etc, that's rude, poor salesmanship, and terribly unprofessional on his part. He should have asked for clear specifications regarding your needs in the first place.
I've also learned through extensive experience dealing with vendors like telcos, circuit carriers, and colo providers that keeping control of a conversation with them, and keeping them focused on what you want or need, is an acquired skill. It takes patience, the ability to be manipulative, and the ability to put your foot down while not stepping on anyone. And most importantly, you must remain focused on your needs.
(well, ok, maybe there was this one hosebeast at this one telco that I wanted to step on...heheh...)
I'm going to make the first post that is serious on this topic...
I think it's great that they've found another moon in the outer solar system. It must be rather complicated keeping track of all the objects that are out there, and especially determining whether an object is a brand-new discovery or an old one.
Do they have some kind of database or repository of this information? Perhaps it is available on the web or something. I would be most obliged if someone would point the way.
Does this mean I will have to get my pager refitted with a nozzle to pour the water into?
I think you might be missing a distinction
on
Weblogs and Fair Use?
·
· Score: 3, Insightful
IANAL but...
There is a big difference between including a link to a news article (or any other content) in your weblog and actually taking a copy of the news article and hosting it somewhere else (for archiving purposes after the news provider removes it from your website.
In the first case, you are just posting a link. The news providers' content remains on their website. In the second case, you are actually copying content that they own and placing it somewhere on the internet that is not under the copyright owner's direct control.
See the difference?
I'm really surprised that NY Times has come out with this stance. At the same time, I'm also very pleased. It is good to see a major publication entity encouraging competition.
I don't recall seeing any pro-Linux commentary in NY Times' website before...does anyone else?
Slashdot Mirror
An email I just sent to Luke:
Hey Luke...I decided to take up Lessig's challenge as well. I am kicking it off by cancelling my AOL account, and I will donate the amount of money I would have spent on that account for one year to the EFF. That comes out to 19.95 x 12 = $293.40.
I'll give AOL a call, let them know why I'm cancelling the account and where the money will be going, and then post my notes on that call in my journal!
The web page for my slashdot journal is "A HREF="http://slashdot.org/~Locke!Erasmus/journal/" >here . Please do not list my email address, just the link to my slashdot journal.
Thanks!
I sincerely wish you luck.
the thing to remember here is that you haven't done anything wrong, and I wouldn't cave in to them just because they're being intimidating. My gut feeling, knowing as little about the situation as I do, is that the folks who are threatening you fear having to GPL their derived products as well, so they're employing bsa or riaa-style tactics on you.
if it comes down to it, set up a paypal account. I will be happy to donate to any legal fund set up to fight these guys.
I think hahnfield might have opted to leave his website and the identity of his project out to avoid the slashdot effect. It seems to be nailing his site at the moment.
You have some really good points!
I would just wish to clarify something - about making the software company publish the code under the GPL.
I don't think hahnfield actually made the software company do anything. It was a settlement. The software company chose on their own to release the code under GPL to avoid the hassle of going to court - because unlike the guy working on open source code, a court actually can make the software company do something.
Let me get this straight...are they saying that their code is contained in the original GPL product that you put together, and it must be removed or they will ($gratuitous_threat)?
Or are they saying they think their code is included in the derived product that you just settled on, that is soon to be released under the GPL?
There's a difference there. If it's your original product, how did their proprietary stuff get there? Did you hack into their networks, swipe their proprietary code, and add it to your open source project?
If it's the derived product that is being released as part of the settlement, the "how did it get there" question applies, but I'd also ask some more questions. How do they know they have code there? Did they collaborate on the add-on? Did they at any time give any code for any reason to the person who is settling with you? Under what terms?
There's also this point: You're not releasing the code under the GPL. The developer is the derived product is releasing it. Why would all these other companies want to block him from distributing his project for free, by coming after you?
($gratuitous_IANAL_message), but it seems to me like they might have GPL-protected code in the products they've derived off your project, so it seems like they are using nasty and unpleasant tactics to try to scare you into backing off or whatever.
Get a good IP lawyer, and if one isn't available I'd definitely be hooking up with the FSF to see if they can provide any assistance.
would be Avery Brooks, AKA Captain Benjamin Sisko...and he should know perfectly well that his flying cars are in front of the bluescreen or greenscreen or whatever!
There are a couple of ideas that I believe any NOC engineer should hold close if he or she wants to keep it together: 1. When trying to resolve an outage, don't believe any piece of information that anyone (vendor, peer, SA department) gives you until you can prove it to yourself. People make assumptions, which are often wrong. 2. Don't close a trouble ticket until you know the problem is fixed and it isn't coming back. If your NOC has three or four tickets on the same outage within a week or two, then you've got two problems: one with your gear, and one with your process. 3. Stay away from red bull. That crap is evil. 4. Find your own niche, a particular set of NOC duties that you excel in. Find some subject matter on which you can be an expert. 5. Just like they say you should check your problems at the door when you come to work, check your work at the door when you go home. 6. Be nice to people. There is no reason to be a jerk or ugly with people whether they are a vendor or a phone monkey in the call center. Sometimes it is harder to be nice when there's a high-profile outage going on and you aren't getting instant results, but it will pay off when that vendor or TS supe or whoever pulls your hiney out of the fire later on. 7. CSM aka head of lettuce is a pimp. :)
at the request of Microsoft or John Ashcroft? Aw shucks, does it matter?
I like halloween, but I like the weekend before that, Fall Back, even better!
I am all about an extra hour of sleep:)
It is entirely possible that he was curious about exactly what you wanted the system to do, and trying to come up with the best deal he could make you....
of course, if he was confrontational about it, etc, that's rude, poor salesmanship, and terribly unprofessional on his part. He should have asked for clear specifications regarding your needs in the first place.
I've also learned through extensive experience dealing with vendors like telcos, circuit carriers, and colo providers that keeping control of a conversation with them, and keeping them focused on what you want or need, is an acquired skill. It takes patience, the ability to be manipulative, and the ability to put your foot down while not stepping on anyone. And most importantly, you must remain focused on your needs.
(well, ok, maybe there was this one hosebeast at this one telco that I wanted to step on...heheh...)
Perhaps they will destroy some bugs and security holes soon, too!
I'm really surprised they didn't include a humane method of euthanizing the animal in the spacecraft. I think it's very sad.
Are they going to give a handout listing all the exploits and security holes Palladium will include?
And shortly after that, the backdoor howto will appear on slashdot, right?
Thanks for fixing those bugs, guys!
Is there perhaps any way you can fix my internet explorer next?
I'm going to make the first post that is serious on this topic...
I think it's great that they've found another moon in the outer solar system. It must be rather complicated keeping track of all the objects that are out there, and especially determining whether an object is a brand-new discovery or an old one.
Do they have some kind of database or repository of this information? Perhaps it is available on the web or something. I would be most obliged if someone would point the way.
Not if they used the pyramids for game shows as well as burials.
Obviously Maytag appliances with a lifetime warranty.
Does this mean I will have to get my pager refitted with a nozzle to pour the water into?
IANAL but... There is a big difference between including a link to a news article (or any other content) in your weblog and actually taking a copy of the news article and hosting it somewhere else (for archiving purposes after the news provider removes it from your website. In the first case, you are just posting a link. The news providers' content remains on their website. In the second case, you are actually copying content that they own and placing it somewhere on the internet that is not under the copyright owner's direct control. See the difference?
is to outsource your sales team.
recommend a list of people that should be on the bus?
I'm really surprised that NY Times has come out with this stance. At the same time, I'm also very pleased. It is good to see a major publication entity encouraging competition. I don't recall seeing any pro-Linux commentary in NY Times' website before...does anyone else?
scp great.firewall.of.china cybersecurity@us.gov:
After all, if he hadn't flamed Enterprise in his original story, this thread would be filled with nothing but the highest praise for the show, right?