...no doubt the same techniques used in their excellent spam filter setup on gmail. You know, the one that will repeatedly mark incoming mail as spam even though you have already marked it over and over as "not spam". Or the classic: Google marks as spam incoming mail with a sent-from address that matches an already verified alias in your own account.
Yeah, I know, there's no way I can be right in light of the thousands of PhD's employed by Google. The collective brainpower is staggering, so Google will always be right in everything they do.
Whether or not some kid on an off-road course injured himself is of little importance.
Which is why this "kid" sticks to off-road biking. Only a fool rides a bike on a major roadway and expects motorists to be patient and accommodating.
And I wouldn't brag about "only" having hip and collarbone fractures over a 4-decade cycling habit. I've driven cars for about that long and have never broken a bone. So no thanks, you can have your broken hips and collarbones....I'll stick with my car for transportation, and my off-road bike for exercise.
Oh, and and don't worry. I'll always yield to bikers on the roadway. We all have to stick together don't we?
So it wasn't hacked, and Google fucked up...
on
PHP.net Compromised
·
· Score: 1
From php.net:
It turned out that by combing through the access logs for static.php.net it was periodically serving up userprefs.js with the wrong content length and then reverting back to the right size after a few minutes. This is due to an rsync cron job. So the file was being modified locally and reverted. Google's crawler caught one of these small windows where the wrong file was being served, but of course, when we looked at it manually it looked fine. So more confusion.
I'm idly curious if Google even bothers to offer an apology.
I've seen the shuttle in person (piggybacked on a 747). It is fucking huge. I've not seen the ISS up close, but I understand the solar arrays are massive. Given that, was it just me or was the size scale off on the shuttle/ISS renderings in this movie? Especially when they were working near the bay of the shuttle just as the swarm of debris approached, as well as when they were in front of the ship peering in at the destruction and the dead crew. It all just seemed so small to me.
I'm thinking maybe this was a device used by the director in order to provide some sort of balance on-screen: Had actual scale been used, all you'd ever see was shuttle or ISS, with no space in the background.
So did I, and I rejected the Nest for the same reason you did. Instead, I purchased two of the CT-30s. Cloud is optional; I set up some perl scripts that do all the controlling via REST, as well as some cool logging that graphs my usage.
My flight instructor (F-86 combat pilot in Korea) taught me very well: My training led to a successful dead-stick landing after my C172 sucked up a rivet from the carb heat door and wedged itself in a valve. Among the many things I learned from that crusty ex-USAF jet jockey was this one:
When the shit hits the fan, FLY THE AIRPLANE. You FLY THE AIRPLANE until it's no longer moving. Never stop FLYING THE AIRPLANE or you'll surely die.
Panic has no place in the cockpit when the shit is hitting the fan. He drilled this into me with endless engine-out drills, stalls, windows opening in flight, simulated flap jams, and even a spin recovery. He assured me that if I FLY THE AIRPLANE when things start to go downhill, there's a very good chance I'll survive.
Indeed he was right. I was his last student before he passed away from cancer. RIP, Red...
Actually, the *old* police state, just catching up with technology. I can't imagine a more awful place to live, where your every move is subject to surveillance and unlawful searches. What's worse is that New Yorkers actually vote these fascists in office.
Guess you get to lie in the bed you make after all. No sympathies here.
Watch this video of DARPA's Big Dog. Pay attention around the 0:33 mark where the guy walks over and kicks the hell out of the robot, which makes a nice recovery.
Raise your hand if, for an instant, you thought to yourself "Damn, that was fucked up, kicking it like that."
...but isn't man's disruption of the natural processes that keep the population in check a direct contributor to the world overpopulation problem? From a strictly scientific point of view, drastically altering the mortality rate of the world's population by decreasing it (and increasing the birth/death ration) can't be a good thing. Many of these people have lived generations in their current environment, so why does a first world country believe they have the right to disrupt nature in such a drastic way?
So a first world country solves the woodstove problem, thereby decreasing mortality rates. Are they prepared to then step in and deal with inadequate water supplies, increases in loss of arable lands, higher rates of infant mortality, and other side effects of overpopulation?
IANAL, but I believe this is the Supreme Court decision that later case law was established upon that basically permits any LEO to lie (not in court though). So basically case law carves out an exemption specifically for law enforcement.
Also, this article demonstrates how easy it is to get ensnared by the feds on a lying charge. Scary stuff.
On the other hand the US Supreme Court has ruled that the government is not constitutionally required to tell the truth.
Right on! This is why dealing with the feds is so dangerous: They can lie to you with impunity, and your answers to their lies are still admissible in court.
Actually, 18 USC section 1001 does, in fact, make lying to a federal official a crime. Feds often use this law to convict people in lieu of having any evidence that a crime was committed. If you're questioned about an alleged crime, and it later turns out that you didn't commit the crime but you earlier statements don't sync up with later statements, there's a good chance you'll see jail time.
Bruce Schneier himself advises avoiding elliptic-curve, as being intellectually tainted by the spooks. [theguardian.com]
I didn't see any such recommendation in the linked article. However, there is a comment in this article in which he does make such a statement. Schneier seems to have reversed himself on advocating the use of elliptic-curve ciphers.
...from behind a car stopped in traffic. I never saw him, and and he never looked my way. I was traveling about 30 mph, and later reconstruction of the incident by the county sheriff's office (used in my defense during the civil court case) showed that there was probably less than 2 seconds between when he stepped out and when I hit him. I seriously doubt this app would have helped him or anyone else in a similar situation.
BTW, he was issued a ticket in the hospital for "failure to yield right of way to motor vehicle." Never knew there was such a law, and it certainly helped in my defense. (Needless to say, the insurance company paid anyway because it was cheaper than going to court.)
I apologize for the personal attack. Not sure why I did that. Guess I let my emotions get the better of me.
Still, fuck RBLs. Sadly, many who should know better do not weight RBLs, and instead outright reject any mail that scores a hit. These operators are slowly destroying the email infrastructure by not only fragmenting and marginalizing the smaller email providers (including individuals who choose to responsibly run their own SMTP service), but by implicitly forcing individuals to seek mail services through corporate providers (think "do no evil"). I have gotten to the point where I simply tell subscribers to the lists I admin that they will have to use another ISP if they want to subscribe because their email provider blindly defers to one or more RBLs, most of which are dodgy to begin with (think pay to play, or let's ban entire subnets because we aren't technologically adept enough to filter on just one IP address).
At this point he can then run the mail through a series of weighted RBLs.
Fuck you and your RBLs. RBLs are a draconian solution that do immeasurable damage to those of us who (1) aren't spammers, and (2) choose to run our own mailservers on business-class IPs. I can't tell you how many times various IPs I use for outbound mail (I run several mailing lists) end up on an RBL for absolutely no fucking reason.
Oh, because someone in the same/24 block sent spam? Really? That's a good reason to block an entire/24 subnet?
RBLs are a solution in search of a problem. Some of them are nothing more than moneymakers for the people that run them: In order to get off their list, they blackmail you into paying money.
Want to do the world a favor? Don't use RBLs. You'll just end up finding yourself blacklisted at some point anyway.
Don't follow this advice. SA has become so slow that it's almost useless. On a VM with 1GB RAM, it takes anywhere from 15-60 seconds to process a single e-mail, and is an incredible resource hog. I've been running SA for years, run the latest stuff, and have pretty much done every tweak imaginable. And the default rules are about useless now as well: The scores are set so low that you have to set a low threshold, increasing your false positive rate. About 50% of the mail on my mail server (personal use, maybe 200-300 inbound messages a day, 90% spam) just gets passed due to spamd timing out.
Unfortunately, there appear to be no decent alternatives out there. Greylisting is nice, but spammers are wising up to it, and simply resend spam. There was a time about 3-4 years ago that zero spam came through (same inbound volume)...now, it's more like 5-10 a day. Not that I'm complaining. My point being that switching over to SA will not solve any of the submitter's resource woes with procmail.
Slashdot Mirror
then of course that fruit company
Adafruit? What the hell are you talking about?
Not always.
or we could have a rational discussion about gun control...Nah
Looks like gun control in CA, one of the most anti-2A states in the union, is working great. Bring the discussion on.
...no doubt the same techniques used in their excellent spam filter setup on gmail. You know, the one that will repeatedly mark incoming mail as spam even though you have already marked it over and over as "not spam". Or the classic: Google marks as spam incoming mail with a sent-from address that matches an already verified alias in your own account.
Yeah, I know, there's no way I can be right in light of the thousands of PhD's employed by Google. The collective brainpower is staggering, so Google will always be right in everything they do.
Whether or not some kid on an off-road course injured himself is of little importance.
Which is why this "kid" sticks to off-road biking. Only a fool rides a bike on a major roadway and expects motorists to be patient and accommodating.
And I wouldn't brag about "only" having hip and collarbone fractures over a 4-decade cycling habit. I've driven cars for about that long and have never broken a bone. So no thanks, you can have your broken hips and collarbones....I'll stick with my car for transportation, and my off-road bike for exercise.
Oh, and and don't worry. I'll always yield to bikers on the roadway. We all have to stick together don't we?
From php.net:
It turned out that by combing through the access logs for static.php.net it was periodically serving up userprefs.js with the wrong content length and then reverting back to the right size after a few minutes. This is due to an rsync cron job. So the file was being modified locally and reverted. Google's crawler caught one of these small windows where the wrong file was being served, but of course, when we looked at it manually it looked fine. So more confusion.
I'm idly curious if Google even bothers to offer an apology.
[CAUTION: POSSIBLE SPOILERS]
I've seen the shuttle in person (piggybacked on a 747). It is fucking huge. I've not seen the ISS up close, but I understand the solar arrays are massive. Given that, was it just me or was the size scale off on the shuttle/ISS renderings in this movie? Especially when they were working near the bay of the shuttle just as the swarm of debris approached, as well as when they were in front of the ship peering in at the destruction and the dead crew. It all just seemed so small to me.
I'm thinking maybe this was a device used by the director in order to provide some sort of balance on-screen: Had actual scale been used, all you'd ever see was shuttle or ISS, with no space in the background.
So did I, and I rejected the Nest for the same reason you did. Instead, I purchased two of the CT-30s. Cloud is optional; I set up some perl scripts that do all the controlling via REST, as well as some cool logging that graphs my usage.
My flight instructor (F-86 combat pilot in Korea) taught me very well: My training led to a successful dead-stick landing after my C172 sucked up a rivet from the carb heat door and wedged itself in a valve. Among the many things I learned from that crusty ex-USAF jet jockey was this one:
When the shit hits the fan, FLY THE AIRPLANE. You FLY THE AIRPLANE until it's no longer moving. Never stop FLYING THE AIRPLANE or you'll surely die.
Panic has no place in the cockpit when the shit is hitting the fan. He drilled this into me with endless engine-out drills, stalls, windows opening in flight, simulated flap jams, and even a spin recovery. He assured me that if I FLY THE AIRPLANE when things start to go downhill, there's a very good chance I'll survive.
Indeed he was right. I was his last student before he passed away from cancer. RIP, Red...
Actually, the *old* police state, just catching up with technology. I can't imagine a more awful place to live, where your every move is subject to surveillance and unlawful searches. What's worse is that New Yorkers actually vote these fascists in office.
Guess you get to lie in the bed you make after all. No sympathies here.
No explosions. No strippers. No guns.
Not that I don't like my GTA fix. But I also thoroughly enjoyed the Myst series as well. Just making an observation.
Watch this video of DARPA's Big Dog. Pay attention around the 0:33 mark where the guy walks over and kicks the hell out of the robot, which makes a nice recovery.
Raise your hand if, for an instant, you thought to yourself "Damn, that was fucked up, kicking it like that."
(Raises hand)
...but isn't man's disruption of the natural processes that keep the population in check a direct contributor to the world overpopulation problem? From a strictly scientific point of view, drastically altering the mortality rate of the world's population by decreasing it (and increasing the birth/death ration) can't be a good thing. Many of these people have lived generations in their current environment, so why does a first world country believe they have the right to disrupt nature in such a drastic way?
So a first world country solves the woodstove problem, thereby decreasing mortality rates. Are they prepared to then step in and deal with inadequate water supplies, increases in loss of arable lands, higher rates of infant mortality, and other side effects of overpopulation?
That will set you back to the tune of about $223,500 (enter some fake info for the details). Or it looks like you can lease 30 tuners for about $5,000/month.
Think I'll be sticking with my Moxi.
It's my understanding that voting is compulsory in AU. When you vote, must you mark your ballot?
Given that not everyone is interested in voting, would it not make sense to simply mark the ballot the easiest way possible (i.e., from the top)?
IANAL, but I believe this is the Supreme Court decision that later case law was established upon that basically permits any LEO to lie (not in court though). So basically case law carves out an exemption specifically for law enforcement.
Also, this article demonstrates how easy it is to get ensnared by the feds on a lying charge. Scary stuff.
On the other hand the US Supreme Court has ruled that the government is not constitutionally required to tell the truth.
Right on! This is why dealing with the feds is so dangerous: They can lie to you with impunity, and your answers to their lies are still admissible in court.
Lying itself can't be a crime
Actually, 18 USC section 1001 does, in fact, make lying to a federal official a crime. Feds often use this law to convict people in lieu of having any evidence that a crime was committed. If you're questioned about an alleged crime, and it later turns out that you didn't commit the crime but you earlier statements don't sync up with later statements, there's a good chance you'll see jail time.
This is why you never talk to law enforcement officers without competent legal representation present. And especially the Feds.
Bruce Schneier himself advises avoiding elliptic-curve, as being intellectually tainted by the spooks. [theguardian.com]
I didn't see any such recommendation in the linked article. However, there is a comment in this article in which he does make such a statement. Schneier seems to have reversed himself on advocating the use of elliptic-curve ciphers.
Holy shit! That is just plain crazy. That must be some strong velcro holding the back of his suit together...
...from behind a car stopped in traffic. I never saw him, and and he never looked my way. I was traveling about 30 mph, and later reconstruction of the incident by the county sheriff's office (used in my defense during the civil court case) showed that there was probably less than 2 seconds between when he stepped out and when I hit him. I seriously doubt this app would have helped him or anyone else in a similar situation.
BTW, he was issued a ticket in the hospital for "failure to yield right of way to motor vehicle." Never knew there was such a law, and it certainly helped in my defense. (Needless to say, the insurance company paid anyway because it was cheaper than going to court.)
...and this is what I found:
http://stackoverflow.com/questions/5301896/what-are-the-differences-between-openid-and-myopenid
So my question: If myOpenID is "one of many providers," why does this rate an article of its own? Or am I missing the significance of the event?
I apologize for the personal attack. Not sure why I did that. Guess I let my emotions get the better of me.
Still, fuck RBLs. Sadly, many who should know better do not weight RBLs, and instead outright reject any mail that scores a hit. These operators are slowly destroying the email infrastructure by not only fragmenting and marginalizing the smaller email providers (including individuals who choose to responsibly run their own SMTP service), but by implicitly forcing individuals to seek mail services through corporate providers (think "do no evil"). I have gotten to the point where I simply tell subscribers to the lists I admin that they will have to use another ISP if they want to subscribe because their email provider blindly defers to one or more RBLs, most of which are dodgy to begin with (think pay to play, or let's ban entire subnets because we aren't technologically adept enough to filter on just one IP address).
At this point he can then run the mail through a series of weighted RBLs.
Fuck you and your RBLs. RBLs are a draconian solution that do immeasurable damage to those of us who (1) aren't spammers, and (2) choose to run our own mailservers on business-class IPs. I can't tell you how many times various IPs I use for outbound mail (I run several mailing lists) end up on an RBL for absolutely no fucking reason.
Oh, because someone in the same /24 block sent spam? Really? That's a good reason to block an entire /24 subnet?
RBLs are a solution in search of a problem. Some of them are nothing more than moneymakers for the people that run them: In order to get off their list, they blackmail you into paying money.
Want to do the world a favor? Don't use RBLs. You'll just end up finding yourself blacklisted at some point anyway.
have you tried spamassassin?
Don't follow this advice. SA has become so slow that it's almost useless. On a VM with 1GB RAM, it takes anywhere from 15-60 seconds to process a single e-mail, and is an incredible resource hog. I've been running SA for years, run the latest stuff, and have pretty much done every tweak imaginable. And the default rules are about useless now as well: The scores are set so low that you have to set a low threshold, increasing your false positive rate. About 50% of the mail on my mail server (personal use, maybe 200-300 inbound messages a day, 90% spam) just gets passed due to spamd timing out.
Unfortunately, there appear to be no decent alternatives out there. Greylisting is nice, but spammers are wising up to it, and simply resend spam. There was a time about 3-4 years ago that zero spam came through (same inbound volume)...now, it's more like 5-10 a day. Not that I'm complaining. My point being that switching over to SA will not solve any of the submitter's resource woes with procmail.