some folks with control of their own name servers just added their own replacement entries, say pointing verisign.com to some random IP? While it might not have as broad an effect, sufficient implementation could still cause some aggravation. Any thoughts on the legalities of this? Their being at the top does not exclude other players from the game of IP hijack.
It may depend on the event. Consider this recent article. Just because they didn't intend to offer WiFi does not mean that it will not become more common. OTOH, I don't think public WiFi would be popular for pro users of this camera. I doubt any pro covering an event would want to broadcast his images for someone else to capture and distrubute. It would be more likely to be connected to their laptop with an encryption key to provide at least some protection.
Teleconference recording available
on
Today's SCO News
·
· Score: 3, Informative
A recording of the teleconference is available: (888) 203-1112 code: 164628
In some cases, watching TV can have the same activity level as listening to music, or lack thereof. How about combining iTunes, TiVo and XServe for a home media server? Record the MP3, TV shows, or music videos you want and listen/watch them from any computer in the house. Download the music to your iPod or download the shows to your iBook for watching on the train during the morning commute.
What makes us think an ID system will be well designed? Look at many of the software and hardware systems we work with. Most are thrown together as people happen to think of things that are needed. Too rarely are systems well thought out in advance. Often, there is a rush to solve a problem and, at that moment, those in control view time (and thus money) as the more valuable commodity. To save that, the system is thrown together in a hurry.
I think a similar situation exists here. Some people are in a hurry to implement a system, and as a result, do not take the time to inspect the details, specifically, how some early design decisions have further reaching consequences. It may be short-sighted, but it is easier and quicker up front. The real payment comes later with trying to live with and improve that now legacy system.
It is very easy for people to take this viewpoint. As they may not have been directly affected, people easily forget the lessons history has to teach, even if those lessons have been repeated many times before.
That should probably be 'apply SETI@Home principles to design challenges." If the communites are underserved, they have enough problems already without designing more.
Actually, this is starting to happen in the US. I was recently involved in bid for a US government agency. Other than Red Hat, Apache, PHP and PostgreSQL, one specific requirement was that the result be made open source. Even if it is not the law, I like that direction.
If I understand this correctly, here are a couple of rough analogies:
1) You buy a vehicle, sign the papers, start the loan and then get told you have pay more before taking delivery.
2) You go through a store checkout, pay for your items, get your receipt and then have to pay more to leave the store.
IANAL, yada, yada, but...
It is one thing to have a typo and not sell based on the quoted price. It is quite another to sell based on a price and then, after the completing the sale (i.e., collecting the purchase price money), claim the price was not correct and that more is required. While the former may be a legitimate mistake, the later appears to be fraud.
Personally, I don't plan on the software I write having defects. That is not to say that it doesn't, just that having defects is something I strive to avoid. Given the premise that having defects is a bad thing, building in obsolescense because you might encounter a defect at some point in the future seems to be a defeatist attitude. "I know it will have defects, so it should just stop working." That's just crap.
Good enough software? If the possiblity of a defect is such a bad thing, it would be better to build in methods that allow for that possiblity. Several of those have already been mentioned here. Software that can check for available upgrades or just having a method of notification of available upgrades are just two possibilities.
I can just imagine it. As evening approaches, first just one starts to click. A bit later, another responds and clicks back. Then another joins in. Pretty soon, you have a whole chorus going.
The article you are quoting is related to the original slashdot story of August 2nd and not the follow up story on March 19th, which is what I linked to.
To respond to your quote, though, aren't most business decisions financial ones? While the decision may have been influenced by the slow PC market, I am also of the opinion that was not the only factor involved. Of course, without being privy to inside correspondence/discussions, this can only be speculation on my part.
The slashdot article I linked said dropping plans to offer the open-source Linux operating system on some machines it sells. It did not say all machines, only some machines. To quote you, maybe you should try checking the facts first.
I just did another quick check. I went to Dell Search and searched for 'Linux' in all categories. 7 of the first 10 links are no longer valid. Link 2 was when the 11/19/01 press release came out and allows you to get to the medium to large business sytems you found. Link 7 was for video drivers as recent as 7.0. Link 9 was as recent as 6.1. When I narrowed the search to the Home category, I found only one link. It was for the Lexmark Z53 Color Printer.
According to the article, The new terms would affect contracts written after Dec. 16 for the top 20 PC makers. and Fama concluded that the new uniform pricing mechanism benefits those companies selling the highest volumes, such as Dell Computer. and "Dell may not want to be a witness, but Dell is affected in similar ways to Gateway because of uniform licensing."
Maybe Dell has already spoken. Reference this recent slashdot article:
It is fraudulent to claim that I am about to lose my domain name. That claim was a lie. The domain name had been renewed with another registrar a couple of months earlier.
I wonder if some of the services like SpamCop could handle something like this. For each spam that is reported, allow sending the "$25 will be owed for each subsequent spam" along with the spam report. On collecting a sufficient quantity of subsequent spam from the same company, sue on behalf of the many receipients and split the cash to cover their expenses. Even if they could not sue directly on behalf of the inviduals, it would be nice to consolidate the contact information for the companies and individuals that could be sued for the spam received.
The larger a company becomes, the less practical it is to move en mass. It is one thing to move a headquarters. It is quite another to try to move and/or replace the entire staff and risk loss of intellectual assets.
Do you already have specific changes in mind you would like to implement and, if so, what are they and what process do you intend to use to ensure success?
I know some people that homeschool and have not heard any problems related to a lack of interaction with others. More often, I hear that their son did this or that with the Boy Scout troup. Not being in school does not (necessarily) mean a lack of interaction with others their age.
Referring to the paragraph starting with: "In addition, adolescent flamers -- almost invariably young males -- continue to disrupt and distort efforts to create online communities."
This has been one of the reasons I have stopped reading some newsgroups and mailing lists. While filtering in a mail reader could help some, the use of filtering software on the server may help even more. If there is a person that is being disruptive, one that I would prefer not receive my posts or I theirs, I could add that person's email address to my exclusion list. Any new message I send to the list server would be forwarded to everyone on the list except those in my exclusion list. Similar to a client-side filter, any message an exluded person may send to the list would not be forwarded to me by the server. An additional piece of software could periodically check the exclusion lists of all subscribers. If a certain percentage level is reached for any one person, that individual could be automatically unsubscribed or at least sent a warning message to the effect of "You have been excluded by X percent of subscribers."
Guaranteed to work? Of course not. But, if it makes it more inconvenient for those considered undesirable, it may help a little. I would guess that most flamers do so for the attention. Perhaps removing that attention can remove the incentive or just encourage them to move them to another venue.
To recap, the article has 6 pages on modifying the Iwill Slocket IIs (albiet with graphics).
I like the item mentioned in the conclusion better: "a new revision of the Slocket II is currently in the works that will support FCPGA SMP out of the box, making the configuration of a dual CPU system a matter of plugging the CPUs in the slockets, no soldering required."
Slashdot Mirror
This MacGIMP Launcher script started it fine for me. Of course, I found this after I created the /opt/local/bin/gimp link in the X11 applications menu.
Since the original link did not appear to work, here are a couple more that might:
MacGimp
WinGimp
some folks with control of their own name servers just added their own replacement entries, say pointing verisign.com to some random IP? While it might not have as broad an effect, sufficient implementation could still cause some aggravation. Any thoughts on the legalities of this? Their being at the top does not exclude other players from the game of IP hijack.
It may depend on the event. Consider this recent article. Just because they didn't intend to offer WiFi does not mean that it will not become more common. OTOH, I don't think public WiFi would be popular for pro users of this camera. I doubt any pro covering an event would want to broadcast his images for someone else to capture and distrubute. It would be more likely to be connected to their laptop with an encryption key to provide at least some protection.
A recording of the teleconference is available:
(888) 203-1112 code: 164628
In some cases, watching TV can have the same activity level as listening to music, or lack thereof. How about combining iTunes, TiVo and XServe for a home media server? Record the MP3, TV shows, or music videos you want and listen/watch them from any computer in the house. Download the music to your iPod or download the shows to your iBook for watching on the train during the morning commute.
What makes us think an ID system will be well designed? Look at many of the software and hardware systems we work with. Most are thrown together as people happen to think of things that are needed. Too rarely are systems well thought out in advance. Often, there is a rush to solve a problem and, at that moment, those in control view time (and thus money) as the more valuable commodity. To save that, the system is thrown together in a hurry.
I think a similar situation exists here. Some people are in a hurry to implement a system, and as a result, do not take the time to inspect the details, specifically, how some early design decisions have further reaching consequences. It may be short-sighted, but it is easier and quicker up front. The real payment comes later with trying to live with and improve that now legacy system.
It is very easy for people to take this viewpoint. As they may not have been directly affected, people easily forget the lessons history has to teach, even if those lessons have been repeated many times before.
In preparation for being slashdotted, they have already posted a mirror site link.
That should probably be 'apply SETI@Home principles to design challenges." If the communites are underserved, they have enough problems already without designing more.
Actually, this is starting to happen in the US. I was recently involved in bid for a US government agency. Other than Red Hat, Apache, PHP and PostgreSQL, one specific requirement was that the result be made open source. Even if it is not the law, I like that direction.
If I understand this correctly, here are a couple of rough analogies:
1) You buy a vehicle, sign the papers, start the loan and then get told you have pay more before taking delivery.
2) You go through a store checkout, pay for your items, get your receipt and then have to pay more to leave the store.
IANAL, yada, yada, but...
It is one thing to have a typo and not sell based on the quoted price. It is quite another to sell based on a price and then, after the completing the sale (i.e., collecting the purchase price money), claim the price was not correct and that more is required. While the former may be a legitimate mistake, the later appears to be fraud.
Personally, I don't plan on the software I write having defects. That is not to say that it doesn't, just that having defects is something I strive to avoid. Given the premise that having defects is a bad thing, building in obsolescense because you might encounter a defect at some point in the future seems to be a defeatist attitude. "I know it will have defects, so it should just stop working." That's just crap.
Good enough software? If the possiblity of a defect is such a bad thing, it would be better to build in methods that allow for that possiblity. Several of those have already been mentioned here. Software that can check for available upgrades or just having a method of notification of available upgrades are just two possibilities.
I can just imagine it. As evening approaches, first just one starts to click. A bit later, another responds and clicks back. Then another joins in. Pretty soon, you have a whole chorus going.
The poor admin will be afraid to open the door.
They're alive, I tell you.
If the click of death happens in a data center and there is no one there to hear it, does it make a sound?
The article you are quoting is related to the original slashdot story of August 2nd and not the follow up story on March 19th, which is what I linked to.
To respond to your quote, though, aren't most business decisions financial ones? While the decision may have been influenced by the slow PC market, I am also of the opinion that was not the only factor involved. Of course, without being privy to inside correspondence/discussions, this can only be speculation on my part.
The slashdot article I linked said dropping plans to offer the open-source Linux operating system on some machines it sells. It did not say all machines, only some machines. To quote you, maybe you should try checking the facts first.
I just did another quick check. I went to Dell Search and searched for 'Linux' in all categories. 7 of the first 10 links are no longer valid. Link 2 was when the 11/19/01 press release came out and allows you to get to the medium to large business sytems you found. Link 7 was for video drivers as recent as 7.0. Link 9 was as recent as 6.1. When I narrowed the search to the Home category, I found only one link. It was for the Lexmark Z53 Color Printer.
According to the article, The new terms would affect contracts written after Dec. 16 for the top 20 PC makers. and Fama concluded that the new uniform pricing mechanism benefits those companies selling the highest volumes, such as Dell Computer. and "Dell may not want to be a witness, but Dell is affected in similar ways to Gateway because of uniform licensing."
Maybe Dell has already spoken. Reference this recent slashdot article:
More on Dell Dropping Linux Support
It is fraudulent to claim that I am about to lose my domain name. That claim was a lie. The domain name had been renewed with another registrar a couple of months earlier.
I wonder if some of the services like SpamCop could handle something like this. For each spam that is reported, allow sending the "$25 will be owed for each subsequent spam" along with the spam report. On collecting a sufficient quantity of subsequent spam from the same company, sue on behalf of the many receipients and split the cash to cover their expenses. Even if they could not sue directly on behalf of the inviduals, it would be nice to consolidate the contact information for the companies and individuals that could be sued for the spam received.
The larger a company becomes, the less practical it is to move en mass. It is one thing to move a headquarters. It is quite another to try to move and/or replace the entire staff and risk loss of intellectual assets.
Do you already have specific changes in mind you would like to implement and, if so, what are they and what process do you intend to use to ensure success?
I know some people that homeschool and have not heard any problems related to a lack of interaction with others. More often, I hear that their son did this or that with the Boy Scout troup. Not being in school does not (necessarily) mean a lack of interaction with others their age.
Referring to the paragraph starting with: "In addition, adolescent flamers -- almost invariably young males -- continue to disrupt and distort efforts to create online communities."
This has been one of the reasons I have stopped reading some newsgroups and mailing lists. While filtering in a mail reader could help some, the use of filtering software on the server may help even more. If there is a person that is being disruptive, one that I would prefer not receive my posts or I theirs, I could add that person's email address to my exclusion list. Any new message I send to the list server would be forwarded to everyone on the list except those in my exclusion list. Similar to a client-side filter, any message an exluded person may send to the list would not be forwarded to me by the server. An additional piece of software could periodically check the exclusion lists of all subscribers. If a certain percentage level is reached for any one person, that individual could be automatically unsubscribed or at least sent a warning message to the effect of "You have been excluded by X percent of subscribers."
Guaranteed to work? Of course not. But, if it makes it more inconvenient for those considered undesirable, it may help a little. I would guess that most flamers do so for the attention. Perhaps removing that attention can remove the incentive or just encourage them to move them to another venue.
To recap, the article has 6 pages on modifying the Iwill Slocket IIs (albiet with graphics).
I like the item mentioned in the conclusion better: "a new revision of the Slocket II is currently in the works that will support FCPGA SMP out of the box, making the configuration of a dual CPU system a matter of plugging the CPUs in the slockets, no soldering required."