Fnuliny egonuh, yuo cna get aawy wtih ptrtey mcuh any oerdr as lnog as the fsirt and lsat lteetr are in the smae pacle as the oigrinal wrod, bsead on how the bairn wkros. Except that theory has been debunked. It can be proven false by finding two or more words that occupy the same function in language (verb, noun, adjective) that are anagrams of each other yet having the same first and last letter, then constructing a sentence that would have different meanings depending on which word you descrambled.
Even easier, one can coin such a word from another:
arganam -- n. a word which is an anagram of another word sharing the same first and last letter and the same linguistic function ("Arganam is an arganam of anagram.").
I've also tried reading "The War of the Wordls", and even with having a familiarity with the original text, there were places where I could not discern what was written without consulting a normal copy.
If they do litigate against anyone for this patent, someone should respond by throwing a trash-can through the glass door of their corporate headquarters. Somehow, "People who live in glass offices shouldn't apply for trivial patents," doesn't have the same ring to it.
If we do get to a stage where only Hotmail users can talk to other Hotmail users, or only Comcast customers can see Comcastnet, or whatever, it will be just like the bad old days of AOL, Prodigy, CompuServe, even local BBSes. While the "internet" or whatever we call the "internet" today may turn into a walled garden Basically taking the "Inter-" out of "Internet".
("Internet" being from "inter-network", or "network of networks".)
and Linux distros might realistically be blocked (Linux distros because of all the ISOs involved) ISP's excuse: We don't support Linux, so there's no reason for enabling you to download it.
You know, you can just leave your ballot blank. I believe that's called an undervote, and may result in either your entire ballot being uncounted or manually counted by someone who may just decide to count/mark it themselves for whomever they want to win.
Re:USA Not So Different...
on
eBay The Vote
·
· Score: 1
Because traditionally voters vote for one of the candidates they are most familiar with. "Vote for Jeff Johnson, The Name You Know."
Don't worry, it'll stop shooting as soon as it runs out of ammunition. It was an auto-reloading cannon.
[Red vs. Blue: Episode 6 "Giga-Whats"] [Church and Tucker are pinned down by the Warthog's gunfire] Church: Well, we'll just wait here. That thing's gotta run out of bullets sometime.
[Red vs. Blue: Episode 7 "Check out the threads on that tank"] [Church and Tucker are still pinned down by the Warthog's gunfire] Church: My God, doesn't that thing ever run out of bullets?
Acme products were never at fault. All mishaps were always traced to coyote error. And usually a failure to completely read the instructions, including the line, "Not effective against roadrunners."
From "Mostly Harmless" by Douglas N. Adams, Chapter 12:
(It was, of course, as a result of the Great Ventilation and Telephone Riots of SrDt 3454, that all mechanical or electrical or quantum-mechanical or hydraulic or even wind, steam or piston-driven devices, are now required to have a certain legend emblazoned on them somewhere. It doesn't matter how small the object is, the designers of the object have got to find a way of squeezing the legend in somewhere, because it is their attention which is being drawn to it rather than necessarily that of the user's.
The legend is this:
"The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.")
They sender would then know that the address works and will then sell it to other spammers, thus vastly increasing the amount of spam you receive. Real smart. I already get spam to 133 user accounts at my domain that have never responded to a spam, not including minor variations on some usernames with added or deleted characters, start with a digit, or contain more than two consecutive digits in the username. (The majority are now usernames a spammer used when sending mail forged as being from my domain.)
Sometimes I think that maybe if my domain didn't look like it was a catch-all and had instead bounced those first e-mails addressed to users like a1aaa1azzzz1zaaaaa, catchthismail, and thisisjusttestmessageatall at my domain maybe it would have been less of a target for forgery and spam today.
I prefer the phrase:
If your use of lose and loose is loose you lose. It makes for a nice mantra to chant in your head each time you find yourself using either word (emphasis on every other word starting with the first), helping to make you get it right.
I recall noticing that there was a song that had either "lose" or "loose" on the lyric sheet, but the singer actually sang the opposite (wrong) word, making me think there's some regional dialect that eliminates the distinction between how the words are pronounced. I had initially thought of a different phrase to emphasize the difference in how they are supposed to be pronounced using rhyme. Unfortunately, when put to text, it didn't quite work:
Lose rhymes with use. Loose rhymes with use. Adding "Lose does not rhyme with loose," doesn't quite work, but I guess has some appeal for those who like things that look like they say, "A == C, B == C, A != B".
I received one of these, except instead of a stock spam, it was some annoying woman repeating over and over, "What the fuck do you think you're doing?"
The current offering from Time Warner Cable of their "mystro" software prevents me from using all the features of the TiVo connected to it.
If I dare try to change the channel at precisely the time that guide data is updated on the channel I am leaving, the box may fail to change channels, change to the wrong channel, or even crash. Every recording I make has to be padded by at least one minute start and end to avoid this bug, even back-to-back recordings on the same channel. (Networks shifting start and end times by a minute is exacerbating the problem.)
This requires me to disable the TiVo's Suggestions feature as they cannot be padded.
I can't use TWC's cable box at all with the Series1 units as they lack the ability to trim their recordings in response to a neighboring-in-time padded recording: one or the other recording would not be recorded.
I've been subjected to these boxes for more than a year now (I'm in one of their beta-test cites) and the company has thumbed its nose at local officials demanding a resolution to and restitution for the problems.
The only thing that has alleviated the problem is getting a CableCARD-enabled TiVo, though it too has had difficulty with cards that lose the signal and will not reacquire it without a restart or (disliked by TWC) ejecting and re-inserting the offending card which I've had to do three times so far. And of course it's the card in CableCARD slot 1.
Tivo service is $17/month at its most expensive plan and less than $9/month at its cheapest monthly price in the 3year prepaid plan. Actually, TiVo service can be as low as $6.95 a month with an existing unit with service in the same home, even if that existing service is an old Series1 with Lifetime (no monthly fee) service.
Even better, there's the occasional offer to transfer existing lifetime service to the latest hardware, and a free year of service on the legacy unit, which can then be unsubscribed.
(Of my eight TiVos, two are lifetime, 5 are $6.95/mo, and one is a never-subscribed Series1 20hr unit. Two of the monthlies are also Series1 that I could let lapse and still be able to do manual recordings.)
Oh great! Now to terrorize Americans al Qaida can just cold-call random numbers in the US from a tapped foreign number to have random families hauled off to Guantánamo for association with a terrorist group. Checking the Caller-ID won't save you either.
I use SXC or ODS files, depending on what version of OOo I'm running. I only use it for my timesheet, checkbook, and gas mileage.
Unfortunately, when using ODS files, it can't seem to remember that I don't want my spreadsheet opened maximized on the Macintosh. I always have to unmaximize it, then manually resize it to something reasonable. The SXC file for my timesheet on Linux (Ooo 1.0.2) somehow manages to remember the window size.
I believe altering the body of a message while maintaining the same Message-ID would be a violation of RFC 1036. There is a technical reason: blanking out the body in the news spool while retaining the headers risks propagating the altered message to other servers. Deleting the message completely from the server could allow it to re-propagate to that server, making it look like the site failed to comply with the notice. A local administrative cancel won't propagate anything, so there's no altered message competing with the altered message in the flood, and a record remains to prevent it from re-propagating to the server with the same MID.
Also, blanking out a message body interferes with newsreaders that connect to multiple servers to retrieve messages that have expired on others (esp. binary completion). Two servers would retrieve different versions of the same article. This is badly wrong. Requiring the newsreader to fetch the article from multiple servers to find an unaltered version removes the benefits of using such a newsreader.
First, cancellation messages have a tortured history and generally aren't honored. Well as I said they only have to work on one server, and that's on the server that's issuing them, and if done in response to a DMCA notice, it would be the administrators of that server issuing them, so they can easily honor them. In fact, if their own administrative tools had no effect on their own server, that would be incompetence.
They have no responsibility to remove the content from any other servers, and the Distribution: local header would ensure that the cancel message doesn't leave their server ("local" being pretty much the only honored value for that header).
Second, the issue is with content on usenet.com's own servers. All they would need to do is to null out the body of each message and leave the header information (for administrative purposes, etc.). This is indeed what a number of providers actually do. I believe altering the body of a message while maintaining the same Message-ID would be a violation of RFC 1036. (I don't have the time to look it up right now. At least that was a complaint raised several times on the usefor mailing list trying to draft Son of 1036.) It isn't rare to have headers still exist and be retrievable in the XOVER data for a canceled or expired message. (Any attempts to put entire binary segments in headers would be stopped quickly as that would bloat XOVER data to unusability.)
Isn't a cancellation just a notice to expire immediately?
Now if you had quoted the part where I suggested the RIAA might try issuing their own, you'd be right, and I admitted to as much.
From "Dirk Gently's Holistic Detective Agency," by Douglas Adams, New York: Simon and Schuster, 1987.
"Well," he said, "it's to do with the project which first made the software incarnation of the company profitable. It was called Reason, and in its own way it was sensational."
"What was it?"
"Well, it was a kind of back-to-front program. It's funny how many of the best ideas are just an old idea back-to-front. You see, there have already been several programs written that help you make decisions by properly ordering and analysing all the relevant facts.... The drawback with these is that the decision which all the properly ordered and analyzed facts point to is not necessarily the one you want.
"... Gordon's great insight was to design a program which allowed you to specify in advance what decision you wished it to reach, and only then to give it all the facts. The program's task,... was simply to construct a plausible series of logical-sounding steps to connect the premises with the conclusion."....
"Heavens. And did the program sell very well?"
"No, we never sold a single copy.... The entire project was bought up, lock, stock, and barrel, by the Pentagon. The deal put WayForward on a very sound financial foundation. Its moral foundation, on the other hand, is not something I would want to trust my weight to. I've recently been analyzing a lot of the arguments put forward in favor of the Star Wars project, and if you know what you're looking for, the pattern of the algorithms is very clear.
"So much so, in fact, that looking at Pentagon policies over the last couple of years I think I can be fairly sure that the US Navy is using version 2.00 of the program, while the Air Force for some reason only has the beta-test version of 1.5. Odd, that."
Slashdot Mirror
Even easier, one can coin such a word from another:
I've also tried reading "The War of the Wordls", and even with having a familiarity with the original text, there were places where I could not discern what was written without consulting a normal copy.
Fine. Too many operating systems on a PC to qualify? I have another platform for you.
It's called meatspace.
Card-battle game? Sell cards.
Strategy game? Print it on cardboard and sell plastic or metal game pieces.
Puzzle game? Sell puzzle pieces.
Want a first-person shooter? Sell guns. (Respawning limited by player's faith.)
Third-person shooter? Add VR goggles and a tethered floating camera to follow you.
("Internet" being from "inter-network", or "network of networks".)
[Red vs. Blue: Episode 6 "Giga-Whats"]
[Church and Tucker are pinned down by the Warthog's gunfire]
Church: Well, we'll just wait here. That thing's gotta run out of bullets sometime.
[Red vs. Blue: Episode 7 "Check out the threads on that tank"]
[Church and Tucker are still pinned down by the Warthog's gunfire]
Church: My God, doesn't that thing ever run out of bullets?
Sometimes I think that maybe if my domain didn't look like it was a catch-all and had instead bounced those first e-mails addressed to users like a1aaa1azzzz1zaaaaa, catchthismail, and thisisjusttestmessageatall at my domain maybe it would have been less of a target for forgery and spam today.
I've also heard people make statements with a questioning inflection.
I recall noticing that there was a song that had either "lose" or "loose" on the lyric sheet, but the singer actually sang the opposite (wrong) word, making me think there's some regional dialect that eliminates the distinction between how the words are pronounced. I had initially thought of a different phrase to emphasize the difference in how they are supposed to be pronounced using rhyme. Unfortunately, when put to text, it didn't quite work: Lose rhymes with use. Loose rhymes with use. Adding "Lose does not rhyme with loose," doesn't quite work, but I guess has some appeal for those who like things that look like they say, "A == C, B == C, A != B".
I received one of these, except instead of a stock spam, it was some annoying woman repeating over and over, "What the fuck do you think you're doing?"
The current offering from Time Warner Cable of their "mystro" software prevents me from using all the features of the TiVo connected to it.
If I dare try to change the channel at precisely the time that guide data is updated on the channel I am leaving, the box may fail to change channels, change to the wrong channel, or even crash. Every recording I make has to be padded by at least one minute start and end to avoid this bug, even back-to-back recordings on the same channel. (Networks shifting start and end times by a minute is exacerbating the problem.)
This requires me to disable the TiVo's Suggestions feature as they cannot be padded.
I can't use TWC's cable box at all with the Series1 units as they lack the ability to trim their recordings in response to a neighboring-in-time padded recording: one or the other recording would not be recorded.
I've been subjected to these boxes for more than a year now (I'm in one of their beta-test cites) and the company has thumbed its nose at local officials demanding a resolution to and restitution for the problems.
The only thing that has alleviated the problem is getting a CableCARD-enabled TiVo, though it too has had difficulty with cards that lose the signal and will not reacquire it without a restart or (disliked by TWC) ejecting and re-inserting the offending card which I've had to do three times so far. And of course it's the card in CableCARD slot 1.
Even better, there's the occasional offer to transfer existing lifetime service to the latest hardware, and a free year of service on the legacy unit, which can then be unsubscribed.
(Of my eight TiVos, two are lifetime, 5 are $6.95/mo, and one is a never-subscribed Series1 20hr unit. Two of the monthlies are also Series1 that I could let lapse and still be able to do manual recordings.)
Oh great! Now to terrorize Americans al Qaida can just cold-call random numbers in the US from a tapped foreign number to have random families hauled off to Guantánamo for association with a terrorist group. Checking the Caller-ID won't save you either.
I use SXC or ODS files, depending on what version of OOo I'm running. I only use it for my timesheet, checkbook, and gas mileage.
Unfortunately, when using ODS files, it can't seem to remember that I don't want my spreadsheet opened maximized on the Macintosh. I always have to unmaximize it, then manually resize it to something reasonable. The SXC file for my timesheet on Linux (Ooo 1.0.2) somehow manages to remember the window size.
Also, blanking out a message body interferes with newsreaders that connect to multiple servers to retrieve messages that have expired on others (esp. binary completion). Two servers would retrieve different versions of the same article. This is badly wrong. Requiring the newsreader to fetch the article from multiple servers to find an unaltered version removes the benefits of using such a newsreader.
They have no responsibility to remove the content from any other servers, and the Distribution: local header would ensure that the cancel message doesn't leave their server ("local" being pretty much the only honored value for that header). Second, the issue is with content on usenet.com's own servers. All they would need to do is to null out the body of each message and leave the header information (for administrative purposes, etc.). This is indeed what a number of providers actually do. I believe altering the body of a message while maintaining the same Message-ID would be a violation of RFC 1036. (I don't have the time to look it up right now. At least that was a complaint raised several times on the usefor mailing list trying to draft Son of 1036.) It isn't rare to have headers still exist and be retrievable in the XOVER data for a canceled or expired message. (Any attempts to put entire binary segments in headers would be stopped quickly as that would bloat XOVER data to unusability.)
Isn't a cancellation just a notice to expire immediately?
Now if you had quoted the part where I suggested the RIAA might try issuing their own, you'd be right, and I admitted to as much.
New York: Simon and Schuster, 1987.