Oh, they learned alright. What they learned is they can play the stock market like a lottery. They learned to ride the hype, and then try to dump it at as close to the peak as possible before everyone else does the same. Every time SCO releases one of these bullshit sessions, er, press releases or interviews, their stock takes a quick bump upwards. This all from a company that has proven nothing so far, has threatened Red Hat with a "day of reckoning", and then claimed they had no intention of suing RH, and has repeatedly contradicted themselves. Nothing will surprise me at this point...... Other than a full appology, and immediate termination of their lawsuits. The chances of that happening are probably pretty small.
From what I can see, it's not even a design flaw, but a configuration flaw. For site admins using the lazy admin configuration. Site admins who use the lower maintainance 'only root deligation except for.tld' have the problem. Site admins who use the 'specified tld is deligation only', which could require more work in the future, would not be affected. If you used the first method with the example given by ISC,.name would malfunction. If you used the second method, everything would continue to work (except the verisign, etc wildcard domains).
"We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V" - Chris Sontag.
The problem with WMA compression was there were flaws in the compression. At least back in WM7, WMA had problems correctly compressing and playing back percussion sounds without introducing pre-echo, or ringing. MP3 and AAC are both technologies with a great deal of research behind them to make sure that unwanted sound artifacts aren't introduced into the audio stream during compression. Both those standards take sounds out of the audio, but should never add sounds into the decompressed audio.
WMA, on the other hand, was developed by Microsoft at a time when they were desparate to get into the market to avoid being left behind. It was engineered quickly, and as a result, they made mistakes. I haven't heard much about WM9, so it's possible many of those mistakes were corrected, or maybe they were merely software 'corrected' during decompression. I would be interested in seeing an actual test of WM9's compression in terms of these sounds that are difficult to compress correctly.
Either that, or carry on the spirit of the last line he wrote ("Such a pity, comrade."), and insult him in the same way. Perhaps by taking a page from the RIAA/MPAA, and calling him a pirate and thief. Turnabout is fair play, right?
I really don't understand why the US hasn't implemented a "loser pays" rule into the court system. I think it would really reduce the number of 'lottery' lawsuits, and people would be more inclined to think about if they really want to file this lawsuit with the prospect of losing, and having to pay both sides' legal fees. This wouldn't nessesarily make lawsuits more fair for you, but it should reduce some of the legal threatening, with the consequence that the party that is threatening might lose some money if you decide not to back down.
Are you kidding? Apple is basically violating an equivalent document to the one they hold sacred on their platform. Skinned or owner-draw widgets have got to be the worst thing ever implemented on any platform. And I seriously doubt Apple uses nothing but native widgets on Quicktime for Macintosh, either. Windows Media Player 7+ isn't any better, in fact, it's worse because not only is it skinned, it's also unusable. Linux media players have got to be the worst of the bunch, since most of them insist on having their own skinning method. IMO, if you think you need to use a bitmapped or owner drawn control because there's a limitation in the guidelines, it's because there's a flaw in your GUI design, not generally the guidelines.
For harmful effects of 2.4GHz radiation, you need look no farther than your microwave oven. Exposure to that radiation will literally cook something. However, try as they might, I don't believe they've ever managed to link microwave ovens to any kind of cancer. Most wi-fi products use less than 1/10000 or 1/33333 of the power of any microwave, and I'd bet more radiation than escapes from just about any microwave oven that's been used for a while than you'd get from being near a wi-fi product..
I think for all the ranting and raving on the fringe, the government of the US actually does operate under the informed consent of its constituents.
Given the voter turnout rate, the US government operates under the sheer apathy of it's constituents. There's two ways to change the government, voting and revolution. One is only slightly less dangerous than the other. Right now, the only "people" voting tends to be corporations, and they're doing it with their money and power.
And remember, the Internet exists because DARPA was charged to create a communication network that would be *more* reliable than the existing telephone lines.
More reliable on the whole, not on an individual basis. A DDoS can knock down entire ISPs. Making sure their service is up and running is one thing, but how can they have the same standards of service as telephone companies when the critical bit of infrastructure required for those standards of service are not controlled by them? This would leave POTS carriers and cable providers as the only ones who could offer a service that obeys the standards.
Now, these VoIP providers should be providing (and help pay for) 911 service if they're advertising it as a replacement for regular telephone service. Unfortunately, power outages and internet service interruptions will both affect the availability of this kind of service, so not having a regular phone line should be discouraged.
They also have used their patents to slap down people who got a little too close to their work. I remember reading that the VirtualDub author recieved a threat about his ASF code, and removed it instead of taking the chance on a lawsuit (which no private individual can afford to follow through with). It really is amazing. Lots of people tout the benefits of patents for small inventors, but the costs for applying and successfully litigating a patent are very high.
Because regulation at this point seems more like the entrenched industry trying to kill the upstart, rather than regulation for the sake of public good. I'm sure someday, regulations will require a certain degree of ISP uptime and reliability. Until that happens, though, it would be impossible to force a VoIP company to provide those kind of assurances.
I'm all for regulating them, but only after the technology develops, and real needs for regulation are identified. Right now, can you say you know what aspects of their business needs to be regulated, and which don't? Slapping telephone regulations on VoIP would be like requiring postage stamps for e-mail.
That's still better than my Toshiba laptop's keyboard. Unnnnnless you liiiiike typppping like ttttthis. I imagine hunt-and-peck typists wouldn't have a problem with it, though, since it only repeats when one key is depressed before another is released, but not predictably.
pedant-mode: No longer strictly true (although most architectures may still require this). CC-NUMA does not, for example.
Fine, but quoting memory in SI units is messy. If I have 34MB(32MiB), for example, and double my memory, I end up with 67MB(64MiB) because of rounding. Frankly, the problem is that either the hard drive manufacturers need to change their labelling, or Microsoft Windows and RAM manufacturers need to change their labelling. The former would probably be easier, but the latter would be "correct".
How is this the fault of Windows? Every single application that Microsoft releases works with restricted logins, and that is not by accident.
Actually, that's not true. Just about every office application MS releases works as a limited user, but Microsoft has a long list of games that do not work, and several Microsoft published games are listed. Age of Mythology, Asheron's Call, and Microsoft Flight Simulator 2002 to name just a few are part of this list. There's even some non-game software in there that Microsoft creates, such as Microsoft Money 2003 and Works Suite 2001/Picture It Publishing 2001.
In my opinion, it should force you to add a restricted user account during installation. (But note that most linux distributions do not force you to do this either...)
More Linux distributions are forcing you to create one, or just tell you that you're stupid not to add one. However, in regards to WinXP, I'd go one step further, and say that the user it prompts you to create should be made a limited user by default, and to encourage the use of runas to do system maintainance. Unfortunately, then we run into another problem. People will forget the administrator password.
Client side handling also allows administrators to enforce a uniform implementation, rather than having one search engine for.com and.net, a different one for.ca, another for.us, something else for.uk, and so on.
Yet, your government pays more per capita for health care for its citizens than anywhere else, and a large number of its citizens are not covered by any health care plan, government subsidized or otherwise. Peculiar, isn't it? I know the health care industry used the Canadian system's fault to poison the public's attitude, but if you ask just about any Canadian, our health care plan is pretty good. A serious illness won't ruin you financially, here.
No, he's saying the script kiddies are the carriers for the 'viral' r00tkits, in that they're the ones that propagate the infection. It's an interesting way of looking at it, I suppose.
I should say something about RTFA, but instead I'll tell you what was in the article. Yes, NTFS and restricted logins would reduce the number of viruses, but many systems become nearly useless with restricted logons. You can run few, if any, games, many applications that weren't designed to work on NT will fail, and so on. Plus, Windows XP pretty much encourages use of the Administrator account rather than suggesting you use runas to run specific tasks as an administrator instead.
ICANN's contract with Verisign said they could only hold 5,000 domains themselves. It's a lot, but perhaps not unreasonable. This modification by Verisign effectively gave them a very large number of domains (limited only by the maximum allowable size for a DNS query). Although, honestly, I was amazed at Verisigns self restraint on not putting a "Buy this domain" link on every sitefinder page. Guess they decided they couldn't get away with that... Not yet, at least.
Re:"Deprecated"? "left out to dry"? Fuck off, trol
on
Software Fashion
·
· Score: 1
Personally, I love Debian's "anceint packages". It means my servers stay stable over many package upgrades. Sure I might not have a sexy Gnome 2.2 or KDE 3.1 desktop, but who cares? It's a server. I may not have the latest version of Apache, MySQL, or anything else, for that matter, but what does it matter so long as the server works as it's supposed to.
Either way, there are less intrusive ways of doing this. HTTP proxies are one way of doing it, as they can return anything they want when they get a DNS error. Modifications to a web browser are another option (I believe Internet Explorer already does this).
From what I've read, if you do nothing about an infringment for an extended period of time, then it proves to the court that you haven't suffered irreparable harm.
When a plaintiff establishes a prima facie case of copyright infringement, irreparable harm is presumed. ABKCO Music, Inc. v. Stellar Records, Inc., No. 95-7887 at 8091 (2d Cir. September 19, 1996). The presumption may be rebutted, if the defendant is able to demonstrate that the plaintiff delayed in bringing an action requesting preliminary injunctive relief. Bourne Co., 976 F.2d at 101; Citibank, N.A. v. Citytrust, 756 F.2d 273, 276 (2d Cir. 1985). An unreasonable delay suggests that the plaintiff may have acquiesced in the infringing activity, or that any harm suffered by the plaintiff is not so severe as to be ?irreparable.? Although delay for purposes of preliminary-injunction analysis may be similar to the equitable consideration of laches in shaping appropriate final relief, our refusal to approve the issuance of a preliminary injunction should not prevent a lower court from considering the full panoply of available remedies when it fashions permanent relief. See Tough Traveler, Ltd. v. Outbound Products, 60 F.3d 964, 968 (2d Cir. 1995) (making the same point in reference to a Lanham Act case).
I'm not a lawyer, so I could be completely wrong, however. But, to this day, SCO has yet to bring about a copyright infringement action against anyone.
Slashdot Mirror
Oh, they learned alright. What they learned is they can play the stock market like a lottery. They learned to ride the hype, and then try to dump it at as close to the peak as possible before everyone else does the same. Every time SCO releases one of these bullshit sessions, er, press releases or interviews, their stock takes a quick bump upwards. This all from a company that has proven nothing so far, has threatened Red Hat with a "day of reckoning", and then claimed they had no intention of suing RH, and has repeatedly contradicted themselves. Nothing will surprise me at this point...... Other than a full appology, and immediate termination of their lawsuits. The chances of that happening are probably pretty small.
From what I can see, it's not even a design flaw, but a configuration flaw. For site admins using the lazy admin configuration. Site admins who use the lower maintainance 'only root deligation except for .tld' have the problem. Site admins who use the 'specified tld is deligation only', which could require more work in the future, would not be affected. If you used the first method with the example given by ISC, .name would malfunction. If you used the second method, everything would continue to work (except the verisign, etc wildcard domains).
"We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V" - Chris Sontag.
WMA, on the other hand, was developed by Microsoft at a time when they were desparate to get into the market to avoid being left behind. It was engineered quickly, and as a result, they made mistakes. I haven't heard much about WM9, so it's possible many of those mistakes were corrected, or maybe they were merely software 'corrected' during decompression. I would be interested in seeing an actual test of WM9's compression in terms of these sounds that are difficult to compress correctly.
Either that, or carry on the spirit of the last line he wrote ("Such a pity, comrade."), and insult him in the same way. Perhaps by taking a page from the RIAA/MPAA, and calling him a pirate and thief. Turnabout is fair play, right?
I really don't understand why the US hasn't implemented a "loser pays" rule into the court system. I think it would really reduce the number of 'lottery' lawsuits, and people would be more inclined to think about if they really want to file this lawsuit with the prospect of losing, and having to pay both sides' legal fees. This wouldn't nessesarily make lawsuits more fair for you, but it should reduce some of the legal threatening, with the consequence that the party that is threatening might lose some money if you decide not to back down.
Are you kidding? Apple is basically violating an equivalent document to the one they hold sacred on their platform. Skinned or owner-draw widgets have got to be the worst thing ever implemented on any platform. And I seriously doubt Apple uses nothing but native widgets on Quicktime for Macintosh, either. Windows Media Player 7+ isn't any better, in fact, it's worse because not only is it skinned, it's also unusable. Linux media players have got to be the worst of the bunch, since most of them insist on having their own skinning method. IMO, if you think you need to use a bitmapped or owner drawn control because there's a limitation in the guidelines, it's because there's a flaw in your GUI design, not generally the guidelines.
For harmful effects of 2.4GHz radiation, you need look no farther than your microwave oven. Exposure to that radiation will literally cook something. However, try as they might, I don't believe they've ever managed to link microwave ovens to any kind of cancer. Most wi-fi products use less than 1/10000 or 1/33333 of the power of any microwave, and I'd bet more radiation than escapes from just about any microwave oven that's been used for a while than you'd get from being near a wi-fi product..
Given the voter turnout rate, the US government operates under the sheer apathy of it's constituents. There's two ways to change the government, voting and revolution. One is only slightly less dangerous than the other. Right now, the only "people" voting tends to be corporations, and they're doing it with their money and power.
Now, these VoIP providers should be providing (and help pay for) 911 service if they're advertising it as a replacement for regular telephone service. Unfortunately, power outages and internet service interruptions will both affect the availability of this kind of service, so not having a regular phone line should be discouraged.
They also have used their patents to slap down people who got a little too close to their work. I remember reading that the VirtualDub author recieved a threat about his ASF code, and removed it instead of taking the chance on a lawsuit (which no private individual can afford to follow through with). It really is amazing. Lots of people tout the benefits of patents for small inventors, but the costs for applying and successfully litigating a patent are very high.
I'm all for regulating them, but only after the technology develops, and real needs for regulation are identified. Right now, can you say you know what aspects of their business needs to be regulated, and which don't? Slapping telephone regulations on VoIP would be like requiring postage stamps for e-mail.
That's still better than my Toshiba laptop's keyboard. Unnnnnless you liiiiike typppping like ttttthis. I imagine hunt-and-peck typists wouldn't have a problem with it, though, since it only repeats when one key is depressed before another is released, but not predictably.
Fine, but quoting memory in SI units is messy. If I have 34MB(32MiB), for example, and double my memory, I end up with 67MB(64MiB) because of rounding. Frankly, the problem is that either the hard drive manufacturers need to change their labelling, or Microsoft Windows and RAM manufacturers need to change their labelling. The former would probably be easier, but the latter would be "correct".
Actually, that's not true. Just about every office application MS releases works as a limited user, but Microsoft has a long list of games that do not work, and several Microsoft published games are listed. Age of Mythology, Asheron's Call, and Microsoft Flight Simulator 2002 to name just a few are part of this list. There's even some non-game software in there that Microsoft creates, such as Microsoft Money 2003 and Works Suite 2001/Picture It Publishing 2001.
More Linux distributions are forcing you to create one, or just tell you that you're stupid not to add one. However, in regards to WinXP, I'd go one step further, and say that the user it prompts you to create should be made a limited user by default, and to encourage the use of runas to do system maintainance. Unfortunately, then we run into another problem. People will forget the administrator password.
Client side handling also allows administrators to enforce a uniform implementation, rather than having one search engine for .com and .net, a different one for .ca, another for .us, something else for .uk, and so on.
Yet, your government pays more per capita for health care for its citizens than anywhere else, and a large number of its citizens are not covered by any health care plan, government subsidized or otherwise. Peculiar, isn't it? I know the health care industry used the Canadian system's fault to poison the public's attitude, but if you ask just about any Canadian, our health care plan is pretty good. A serious illness won't ruin you financially, here.
No, he's saying the script kiddies are the carriers for the 'viral' r00tkits, in that they're the ones that propagate the infection. It's an interesting way of looking at it, I suppose.
I should say something about RTFA, but instead I'll tell you what was in the article. Yes, NTFS and restricted logins would reduce the number of viruses, but many systems become nearly useless with restricted logons. You can run few, if any, games, many applications that weren't designed to work on NT will fail, and so on. Plus, Windows XP pretty much encourages use of the Administrator account rather than suggesting you use runas to run specific tasks as an administrator instead.
ICANN's contract with Verisign said they could only hold 5,000 domains themselves. It's a lot, but perhaps not unreasonable. This modification by Verisign effectively gave them a very large number of domains (limited only by the maximum allowable size for a DNS query). Although, honestly, I was amazed at Verisigns self restraint on not putting a "Buy this domain" link on every sitefinder page. Guess they decided they couldn't get away with that... Not yet, at least.
Personally, I love Debian's "anceint packages". It means my servers stay stable over many package upgrades. Sure I might not have a sexy Gnome 2.2 or KDE 3.1 desktop, but who cares? It's a server. I may not have the latest version of Apache, MySQL, or anything else, for that matter, but what does it matter so long as the server works as it's supposed to.
Either way, there are less intrusive ways of doing this. HTTP proxies are one way of doing it, as they can return anything they want when they get a DNS error. Modifications to a web browser are another option (I believe Internet Explorer already does this).
Oh, quite easy. Instead of modifying DNS, you could always just modify the WEB BROWSERS, or go through a web proxy server that would do this for you.
Along with "/* You are not expected to understand this */" and "/* FIXME */"
From what I've read, if you do nothing about an infringment for an extended period of time, then it proves to the court that you haven't suffered irreparable harm.
I'm not a lawyer, so I could be completely wrong, however. But, to this day, SCO has yet to bring about a copyright infringement action against anyone.