Just because 'piracy' was used 200 years ago does not make it a good term or right. Calling it piracy 200 years ago was wrong, and calling it piracy today is wrong. It is copyright infringement. Comparing it to murder and theft on the high seas is wrong no matter how many years you repeat it.
Oh yes, I'm aware of all of that - but (generally speaking) Cogent has the content, and Level 3 has the users. Guess who catches the most heat from the de-peering from its customers - Level 3 - as their customers will tend to see the problem first.
I predict that Cogent will do the same again as well - not lift a finger to fix the problem when they are de-peered on November 9th, and Level 3 will probably end up being forced to re-peer as customers whine that they are not getting the whole Internet and threaten to take up Cogent's free 1 year offer.
It's not a rumour that Level 3 is in financial trouble - it's clear for all to see. They have crushing debt repayments right now.
The Cogent spat isn't over yet either - Level 3 are going to de-peer Cogent again on November 9th. They are trying to force Cogent to pay for transit, but right now it looks like Cogent holds the strongest hand and Level 3 will be once again forced to back down.
You can't actually dim the typical streetlight lamps - they are usually high or low pressure sodium lights (low pressure sodium lights being the most energy efficient lamps ever made - however, most places replace the orange low pressure lights for light pink high pressure sodium lamps for a number of reasons). A dimmable type of lamp would actually be a lot less efficent - it'd have to be a tungsten filament lamp which is just about the least efficient type of lamp that we have.
A better plan is to turn off the streetlights altogether in some areas, and switch off every other streetlight in other areas where lighting is needed all night. That's what we do where I live. Also, be proactive in fixing the lights that stay stuck on continuously (I think our streetlights here are switched by both a timer and the ambient light, so if the ambient light sensor fails, the light won't stay stuck on because the timer will switch it off). Last time I was in the UK, travelling on one of the motorways, it seemed like at least 10% of the street lights were stuck permanently on.
Yes there is - you do the comparison by another method. DNA comparisons used to be done without computers at one point. You can take the sample and run it through a completely different system. It's possible to independently verify the DNA match. However, it's not possible to independently verify the number shown on the LCD of a breathalyser several days after the fact.
This is why in sane states and countries, the police don't rely on one source like the breathalyser - they also do a blood or urine test (and the courts won't accept breathalyser evidence on its own).
Slashdot is primarily a community of Unix/Linux geeks, so *of course* the same doesn't apply - generally, we'd much rather know about developments in the *nix world (which includes Mac OS X) than in the Windows mode. This is Slashdot, not Backslashdot.
Well, the thing is I think Microsoft thinks that patronising == user-friendly. Hence all those annoying speech bubbles when you log in (that get in your way), Teletubbies default theme, dumbed down control panel, that dog on the Search function, and in past years Clippy.
The nice thing about Apple is they can make things user friendly without being patronising.
I don't think you understand DNS. Many of the root DNS servers are not in the United States (probably half of them are outside of the US). I think three of them are notionally located outside the US, and out of the rest that are notionally inside the US, parts of them are in other parts of the world. This is because they have 'anycast' addresses, so a root server can be many machines in many places with the same IP address; routers on the internet will decide which physical root server you'll actually contact.
DNA tests can be independently verified after the fact. The process of how DNA matching works is available to the public.
However, the number shown on a black box whose implementation is secret at a given moment in time is totally unverifiable. I'm highly surprised that breatalyser evidence is even admissable in Florida without a second, independent test. Where I live, the breathalyser is used at the roadside to determine whether further testing is necessary (blood or urine) - so any case that goes to court, the evidence will have been verified.
The difference between this and AFR (automatic fingerprint recognition) is that any matches from an AFR system is trivially easy to verify just by looking at the fingerprints. It's not just a black box saying "Yes, these fingerprints match", leaving the jury no way to tell whether this is actually true - the judge and jury can just look at the prints. AFR is just a tool to cut out the monk work of manually going through fingerprints trying to find matches by hand. (Indeed, in the real world, at least last time I worked with an AFR system, it wittled down the possible set of matches, and the final matching was done by a fingerprint specialist).
The breathalyser, however, is a black box. There is no way to verify that at that given moment in time, the box was working within its usual parameters. That's why (where I live) the breathalyser is NEVER used as evidence, rather it is used at the road side to determine whether a blood or urine test is warranted. In an actual drink driving case, the evidence will be from a blood or urine sample.
The thing is, it's not a level playing field. Microsoft doesn't have to make drivers - the manufacturers of hardware does it for them, and often pays Microsoft for the privilege! Linux and the *BSDs have to (by and large) make their OWN drivers for the same hardware, and it might not even be documented - so they are at a huge disadvantage, having to write drivers themselves either by reverse engineering or by using (often) bad hardware documentation. It's not that drivers are innately difficult to install under Linux (I installed the FUSE driver the other day without needing to even reboot, it took about a minute to install the kernel module which loaded automatically as soon as I ran a program that used FUSE) it's that manufacturers simply don't write them for Linux at all.
It would be nice to be able to use Linux on any random piece of hardware - but the fault that it can't is down to the manufacturers, not the Linux developers who have made a sterling effort to support most common hardware with absolutely no support from hardware manufacturers. Microsoft on the other hand doesn't even lift a finger to do hardware support itself - it just lets the manufacturers pay for it (then pay Microsoft a fee to certify the driver). There are of course some exceptions - I'm sure Hewlett-Packard contributed expertise and source to make sure that Linux runs very well on their server hardware. But by and large, the usual response from hardware manufacturers is to not even release documentation let alone an actual driver.
Or any injections at all. I host a modest number of people's domains (a dozen people). One user had PHPBB. When I told him what trouble his buggy, old version of PHPBB had caused, he swore he'd deleted it - all he'd actually done is removed the links to the board, but the code was still there.
A Romanian phishing gang found it, and tried to send over 2 million phishing emails by uploading a PHP script via the exploit. Fortunately, the way I have the email relay configured (the firewall blocks port 25 egress from the web server, so the system has no choice but to relay it through my relay), it shut down after only a handful of phishing emails went out and I could contain it (and had all the evidence to find out who did it). It's prompted me to make the egress filtering tighter though - I had allowed port 80 outbound because it was convenient, now I've told all the users they have to tell me what addresses they need because the rule is now default deny.
"Could care less" implies he cares a lot (and could care a smaller amount). I think the phrase you want is "Couldn't care less"
Re:Why are we hiding from the police, daddy?
on
Vim 6.4 Released
·
· Score: 1
Vim *is* a mouse based text editor. You can put a noob in front of vim on a GUI, and they can use it almost like notepad - complete with pull down menus and a scuzzy little toolbar with icons on it.
I know (well, I hope) you're just joking - but in all seriousness, this new beachfront property will not be very nice. Evidence of prior warming periods of the Earth have shown very rapid sea level rises (several metres in one decade). Most new 'beach' will resemble a shipwreck - ruined buildings, dead trees, all the decades of grime and oily pollution washed around etc. It's not the kind of beachfront property you'd really want to have.
Argh. Stop posting Dvorak articles! The man is an idiot who doesn't check his facts. He has actually gone out and complained in a column about the System Idle Process taking up 98% of cpu on his Windows machine and making the box thrash.
His ignorant rantings are not in the least insightful.
The fact is, if the flooding you speak of occurs, it won't happen such that a bunch of lowland dwellers go to sleep Tuesday night, dry, and wake up Wednesday morning floating on their mattresses.
There is good evidence that prior warming periods of the planet have resulted in very rapid (several meters in one decade) sudden sea level rises. Imagine the economic damage of having to abandon London or New York in one decade. Imagine you live in London or New York and own your home - now unsaleable. You will essentially be unable to afford a new home because you can't sell the old one first.
This is the reason I made sure my house was at least 30 metres above sea level - at least I'm not likely to be driven out of it *when* the sea level does its sudden rise.
Slashdot Mirror
Just because 'piracy' was used 200 years ago does not make it a good term or right. Calling it piracy 200 years ago was wrong, and calling it piracy today is wrong. It is copyright infringement. Comparing it to murder and theft on the high seas is wrong no matter how many years you repeat it.
Oh yes, I'm aware of all of that - but (generally speaking) Cogent has the content, and Level 3 has the users. Guess who catches the most heat from the de-peering from its customers - Level 3 - as their customers will tend to see the problem first.
I predict that Cogent will do the same again as well - not lift a finger to fix the problem when they are de-peered on November 9th, and Level 3 will probably end up being forced to re-peer as customers whine that they are not getting the whole Internet and threaten to take up Cogent's free 1 year offer.
It's not a rumour that Level 3 is in financial trouble - it's clear for all to see. They have crushing debt repayments right now.
The Cogent spat isn't over yet either - Level 3 are going to de-peer Cogent again on November 9th. They are trying to force Cogent to pay for transit, but right now it looks like Cogent holds the strongest hand and Level 3 will be once again forced to back down.
You can't actually dim the typical streetlight lamps - they are usually high or low pressure sodium lights (low pressure sodium lights being the most energy efficient lamps ever made - however, most places replace the orange low pressure lights for light pink high pressure sodium lamps for a number of reasons). A dimmable type of lamp would actually be a lot less efficent - it'd have to be a tungsten filament lamp which is just about the least efficient type of lamp that we have.
A better plan is to turn off the streetlights altogether in some areas, and switch off every other streetlight in other areas where lighting is needed all night. That's what we do where I live. Also, be proactive in fixing the lights that stay stuck on continuously (I think our streetlights here are switched by both a timer and the ambient light, so if the ambient light sensor fails, the light won't stay stuck on because the timer will switch it off). Last time I was in the UK, travelling on one of the motorways, it seemed like at least 10% of the street lights were stuck permanently on.
Yes there is - you do the comparison by another method. DNA comparisons used to be done without computers at one point. You can take the sample and run it through a completely different system. It's possible to independently verify the DNA match. However, it's not possible to independently verify the number shown on the LCD of a breathalyser several days after the fact.
This is why in sane states and countries, the police don't rely on one source like the breathalyser - they also do a blood or urine test (and the courts won't accept breathalyser evidence on its own).
You know I'll truly laugh if Microsoft ends up doing what Apple did - making the stuff underlying the pretty Windows bits into a UNIX-style OS.
Slashdot is primarily a community of Unix/Linux geeks, so *of course* the same doesn't apply - generally, we'd much rather know about developments in the *nix world (which includes Mac OS X) than in the Windows mode. This is Slashdot, not Backslashdot.
Well, the thing is I think Microsoft thinks that patronising == user-friendly. Hence all those annoying speech bubbles when you log in (that get in your way), Teletubbies default theme, dumbed down control panel, that dog on the Search function, and in past years Clippy.
The nice thing about Apple is they can make things user friendly without being patronising.
I don't think you understand DNS. Many of the root DNS servers are not in the United States (probably half of them are outside of the US). I think three of them are notionally located outside the US, and out of the rest that are notionally inside the US, parts of them are in other parts of the world. This is because they have 'anycast' addresses, so a root server can be many machines in many places with the same IP address; routers on the internet will decide which physical root server you'll actually contact.
DNA tests can be independently verified after the fact. The process of how DNA matching works is available to the public.
However, the number shown on a black box whose implementation is secret at a given moment in time is totally unverifiable. I'm highly surprised that breatalyser evidence is even admissable in Florida without a second, independent test. Where I live, the breathalyser is used at the roadside to determine whether further testing is necessary (blood or urine) - so any case that goes to court, the evidence will have been verified.
The difference between this and AFR (automatic fingerprint recognition) is that any matches from an AFR system is trivially easy to verify just by looking at the fingerprints. It's not just a black box saying "Yes, these fingerprints match", leaving the jury no way to tell whether this is actually true - the judge and jury can just look at the prints. AFR is just a tool to cut out the monk work of manually going through fingerprints trying to find matches by hand. (Indeed, in the real world, at least last time I worked with an AFR system, it wittled down the possible set of matches, and the final matching was done by a fingerprint specialist).
The breathalyser, however, is a black box. There is no way to verify that at that given moment in time, the box was working within its usual parameters. That's why (where I live) the breathalyser is NEVER used as evidence, rather it is used at the road side to determine whether a blood or urine test is warranted. In an actual drink driving case, the evidence will be from a blood or urine sample.
Perhaps they have a corrupted MBR or the boot PROM got zapped by static.
The thing is, it's not a level playing field. Microsoft doesn't have to make drivers - the manufacturers of hardware does it for them, and often pays Microsoft for the privilege! Linux and the *BSDs have to (by and large) make their OWN drivers for the same hardware, and it might not even be documented - so they are at a huge disadvantage, having to write drivers themselves either by reverse engineering or by using (often) bad hardware documentation. It's not that drivers are innately difficult to install under Linux (I installed the FUSE driver the other day without needing to even reboot, it took about a minute to install the kernel module which loaded automatically as soon as I ran a program that used FUSE) it's that manufacturers simply don't write them for Linux at all.
It would be nice to be able to use Linux on any random piece of hardware - but the fault that it can't is down to the manufacturers, not the Linux developers who have made a sterling effort to support most common hardware with absolutely no support from hardware manufacturers. Microsoft on the other hand doesn't even lift a finger to do hardware support itself - it just lets the manufacturers pay for it (then pay Microsoft a fee to certify the driver). There are of course some exceptions - I'm sure Hewlett-Packard contributed expertise and source to make sure that Linux runs very well on their server hardware. But by and large, the usual response from hardware manufacturers is to not even release documentation let alone an actual driver.
The file format (Dolby AAC) is openly licensable - it's the DRM that's proprietary.
My 1.3GHz PowerBook can sleep in under a second, and resume from sleep in under a second. I think that's instant enough.
Or any injections at all. I host a modest number of people's domains (a dozen people). One user had PHPBB. When I told him what trouble his buggy, old version of PHPBB had caused, he swore he'd deleted it - all he'd actually done is removed the links to the board, but the code was still there.
A Romanian phishing gang found it, and tried to send over 2 million phishing emails by uploading a PHP script via the exploit. Fortunately, the way I have the email relay configured (the firewall blocks port 25 egress from the web server, so the system has no choice but to relay it through my relay), it shut down after only a handful of phishing emails went out and I could contain it (and had all the evidence to find out who did it). It's prompted me to make the egress filtering tighter though - I had allowed port 80 outbound because it was convenient, now I've told all the users they have to tell me what addresses they need because the rule is now default deny.
Yes, this is probably pedantic.
"Could care less" implies he cares a lot (and could care a smaller amount).
I think the phrase you want is "Couldn't care less"
Vim *is* a mouse based text editor. You can put a noob in front of vim on a GUI, and they can use it almost like notepad - complete with pull down menus and a scuzzy little toolbar with icons on it.
Lutefisk is fish. Or at least, it once was fish. Try it at your own risk.
Now the real acid (or really, alkali) test on fish-vs-pot: would you rather eat LUTEFISK than use pot?
Nah, not Cheetos, those little bags of pizza bites.
I know (well, I hope) you're just joking - but in all seriousness, this new beachfront property will not be very nice. Evidence of prior warming periods of the Earth have shown very rapid sea level rises (several metres in one decade). Most new 'beach' will resemble a shipwreck - ruined buildings, dead trees, all the decades of grime and oily pollution washed around etc. It's not the kind of beachfront property you'd really want to have.
Argh. Stop posting Dvorak articles! The man is an idiot who doesn't check his facts. He has actually gone out and complained in a column about the System Idle Process taking up 98% of cpu on his Windows machine and making the box thrash.
His ignorant rantings are not in the least insightful.
There is good evidence that prior warming periods of the planet have resulted in very rapid (several meters in one decade) sudden sea level rises. Imagine the economic damage of having to abandon London or New York in one decade. Imagine you live in London or New York and own your home - now unsaleable. You will essentially be unable to afford a new home because you can't sell the old one first.
This is the reason I made sure my house was at least 30 metres above sea level - at least I'm not likely to be driven out of it *when* the sea level does its sudden rise.
The names like Breezy Badger are just code names (like Longhorn and Whistler were). In the corporate environment, it could just be called Ubuntu 5.10.