No, the data which is being blocked from transmission is not blocked because it's going to a computer program which would be exploited by it. At least I haven't seen any allegations of that. It's being blocked because the human that would receive the data might use it in a way deemed inappropriate (by clicking on it, say).
I'm gonna pass on those patches at least for now...
I posted this comment successfully... on Safari and Mac Firefox its text displays as "hgfedcba". On MSIE 6 the comment doesn't display at all, and on MSIE 7 it displays as "abcdefgh".
The reason is that the first character in the comment is the Unicode character for "right-to-left embedding." Some browsers respect it, some don't. We would strip it if we ever allowed unicode generally on Slashdot, because it causes too much confusion (you could literally write a comment that read one way on firefox and another way on MSIE, bringing chaos and confusion to moderation, aka, it makes trolling easier).
To make things worse, I was able to crash Solidot 100% repeatably by appending an "i" to that comment text. Not sure why.
There's all kinds of wacky characters in the unicode standard, and we hold to the belief that it's unacceptable to try to screen them out... maybe at some point we'll get around to figuring out some ranges we can allow but it's still not a high priority and, as is obvious, it's quite possible to do it wrong.
When I went back to an earlier page of submissions, I found that only about 2/3 of my selections appear to have been preserved.
Not sure what you mean... you mean when you went back and looked at a firehose item you had previously nodded or nixed, the nod/nix button did not show up with your choice?
Slashdot still logs every pageview (plus ajax). We drop them into MySQL and once a day run a data-massaging script on them then delete the oldest portion. We do have a pair of dedicated servers for this, but generally speaking the I/O is pretty low. It's very doable.
One of the main reasons is detecting abuse in real-time (done by more scripts that run more frequently). I wrote a journal entry about one of those scripts, a while back.
The part you quote is just the preamble and carries no legal weight.
The summary is mistaken, yes (though not dishonest). The actual situation is far worse than Slashdot's summary describes.
The actual language refers to persons who "have committed, or... pose a significant risk of committing, an act or acts of violence that have the purpose or effect of" undermining etc.
In other words, you do not have to do anything to be affected by this law. All the Secretary has to assert is that you were probably going to do something that had a bad effect.
Whether you had the intention to undermine Iraqi reconstruction is irrelevant. Whether you actually did anything is irrelevant.
This isn't just overturning the 5th Amendment, it's erasing it and replacing it with thoughtcrime.
I'll see your 'Scooter Libby on June 23', and I'll raise you a 'Richard Armitage on June 13'.
Yes, they both leaked the identity of a covert CIA operative. What's your point?
Do you think it becomes legal to leak the classified, secret identity of a covert CIA operative just because someone else privately leaked it earlier? I hope not, because that would be just silly.
What exactly was Libby convicted of again? Oh yeah, obstruction of justice. He had nothing to do with Richard Armitage leaking Valerie Plame's identity.
How does Richard Armitage leaking a covert CIA operative's identity to Robert Novak in July 2003 exculpate Scooter Libby from leaking the same operative's identity to Judith Miller on June 23, 2003?
<domain>::= <subdomain> | " "
<subdomain>::= <label> | <subdomain> "." <label>
<label>::= <letter> [ [ <ldh-str> ] <let-dig> ]
<ldh-str>::= <let-dig-hyp> | <let-dig-hyp> <ldh-str>
<let-dig-hyp>::= <let-dig> | "-"
<let-dig>::= <letter> | <digit>
<letter>::= any one of the 52 alphabetic characters A through Z in
upper case and a through z in lower case
<digit>::= any one of the ten digits 0 through 9
However, pretty much everyone allows underscores in machine names now, so I'm patching Slash to allow it.
This "heavenly way," the Rev. Sun Myung Moon explained, demands a 51-mile underwater highway spanning Alaska and Russia. Sitting in the front row: Neil Bush, the brother of the president of the United States.
Rev. Sun Myung Moon, the South Korean giant of the religious right who owns the Washington Times, is on a 100-city speaking tour to promote his $200 billion "Peace King Tunnel" dream. As he describes it, the tunnel would be both a monument to his magnificence, and a totem to his prophecy of a unified Planet Earth. In this vision, the United Nations would be reinvented as an instrument of God's plan, and democracy and sexual freedom would crumble in the face of this faith-based glory.
[...] Moon's lobbying campaign is "ambitious and diffuse," as the D.C. newspaper The Hill reported last year, and the sheer range of guests revealed just how many Pacific Rim political leaders the Times owner has won over, including Filipino and Taiwanese politicians. And the head of the Arizona GOP attended a recent stop in San Francisco. But perhaps the most surprising VIP to tag along is Neil Bush, George H.W. Bush's youngest and most wayward son, who made both the Philippines and Taiwan legs of the journey, according to reports in newspapers from those countries and statements from Moon's Family Federation.
The maps he shows are global. You didn't RTFA.
In fact, Media Matters has never received funding from progressive philanthropist George Soros.
See how easy that was?
You must be new here :)
No, the data which is being blocked from transmission is not blocked because it's going to a computer program which would be exploited by it. At least I haven't seen any allegations of that. It's being blocked because the human that would receive the data might use it in a way deemed inappropriate (by clicking on it, say).
I'm gonna pass on those patches at least for now...
I posted this comment successfully... on Safari and Mac Firefox its text displays as "hgfedcba". On MSIE 6 the comment doesn't display at all, and on MSIE 7 it displays as "abcdefgh".
The reason is that the first character in the comment is the Unicode character for "right-to-left embedding." Some browsers respect it, some don't. We would strip it if we ever allowed unicode generally on Slashdot, because it causes too much confusion (you could literally write a comment that read one way on firefox and another way on MSIE, bringing chaos and confusion to moderation, aka, it makes trolling easier).
To make things worse, I was able to crash Solidot 100% repeatably by appending an "i" to that comment text. Not sure why.
There's all kinds of wacky characters in the unicode standard, and we hold to the belief that it's unacceptable to try to screen them out... maybe at some point we'll get around to figuring out some ranges we can allow but it's still not a high priority and, as is obvious, it's quite possible to do it wrong.
Comments as well as stories...
We really, really do not want to copy Digg :)
Not sure what you mean... you mean when you went back and looked at a firehose item you had previously nodded or nixed, the nod/nix button did not show up with your choice?
If you can replicate this, please let us know...
Mode? Really? OK, that's a pretty nerdy putdown.
What's the next insult? "Your wiener has P < 0.1 and a big deviation"
Yeah it says the same for Slashdot's css files, which are indeed in the head. Guess that's a YSlow bug.
Hi Mandrake.
Slashdot still logs every pageview (plus ajax). We drop them into MySQL and once a day run a data-massaging script on them then delete the oldest portion. We do have a pair of dedicated servers for this, but generally speaking the I/O is pretty low. It's very doable.
One of the main reasons is detecting abuse in real-time (done by more scripts that run more frequently). I wrote a journal entry about one of those scripts, a while back.
The part you quote is just the preamble and carries no legal weight.
The summary is mistaken, yes (though not dishonest). The actual situation is far worse than Slashdot's summary describes.
The actual language refers to persons who "have committed, or... pose a significant risk of committing, an act or acts of violence that have the purpose or effect of" undermining etc.
In other words, you do not have to do anything to be affected by this law. All the Secretary has to assert is that you were probably going to do something that had a bad effect.
Whether you had the intention to undermine Iraqi reconstruction is irrelevant. Whether you actually did anything is irrelevant.
This isn't just overturning the 5th Amendment, it's erasing it and replacing it with thoughtcrime.
Yes, they both leaked the identity of a covert CIA operative. What's your point?
Do you think it becomes legal to leak the classified, secret identity of a covert CIA operative just because someone else privately leaked it earlier? I hope not, because that would be just silly.
How does Richard Armitage leaking a covert CIA operative's identity to Robert Novak in July 2003 exculpate Scooter Libby from leaking the same operative's identity to Judith Miller on June 23, 2003?
You rock!!
However, pretty much everyone allows underscores in machine names now, so I'm patching Slash to allow it.
Are you guys still spreading misinformation about the hockey stick?!
It's 2007...
Not a mother -- his mother.
There's a Bugs link on every page Slashdot serves. We'd need detailed information about the issue before we can solve it.
By "empty clips" the linked article meant "magazines," as of course you know. Technical quibbling about terminology is just trolling.
We didn't.
Digg is run on 100 servers.
It's not.
I still am too... but yeah, when RMS gives up it makes you feel pretty lonely...
You're right! Here's a story about it from Dec. 2005: Neil Bush Meets the Messiah: