As far as I'm concerned, saying that I can't decode the satellite signals being beamed into my house (especially since I live in Canada, where you *can't buy* the service) is like saying that if I happen to walk past a venue that a band is playing, and I can hear the music, I owe them the price of a ticket.
Exactly. This is intended to allow you to protect *your* docuements; not to force you to use MS stuff.
Or is using an encrypted filesystem suddenly a ploy to 'lock you in' to using that OS? No, of course not. You want to move your data, you save it somewhere else.
Well, guess what. Want to use your docs in another program? You save them to RTF or CSV or whatever the hell is appropriate.
But, of course, it's Microsoft, so there MUST BE an eeeeeevil ulterior motive.
Though, on an unrelated note, no Disney female villains have ever been killed. Cruella DeVille survives, mostly unharmed, a car wreck that would normally kill a person. Likewise with the villain from the original "The Rescuers".
Incorrect.
Snow White: The Wicked Queen falls down a cliff and dies.
Little Mermaid: Ursula is pierced through the heart with a large sailing ship. Aside: in the Little Mermaid Two, Morgana, Ursula's sister, refers to this. "Now why couldn't dear Ursula attend? Oh, yes, I remember, it's because YOU ALL SISH-KEBOBED HER!' Morgana, at the end of the story, is imprisioned in a block of ice.
Disney's Atlantis: Helga Sinclair dies, after being betrayed and thrown off of an airship, and she tries to take said airship, and it's crew, with her. Note that we also see such wonderful things as the beating death of a king. One of the better Disney movies, with a concious effort not to include any cute anthropomorphic animal sidekicks.
Those are some that I can think of off the top of my head, at least.
Working with good tech writers is a dream (Zvi and Tamsin, I'm talking to you!) and working with bad tech writers is a nightmare.
Remember, having the best product in the world is useless unless you have the docs to back it up. And you know your tech docs are good when your support people are referring to them on a regular basis.
Yes, if you want contiguous denials of service. But you know what? Five minutes here, ten minutes there, works a hell of a lot better than blam, it's down.
Yeah, because there's no way in HELL that anybody who could design this sort of system could POSSIBLY think to, gosh, some sort of, I don't know, maybe.... randomize the times they attack? Or even build, oh, I don't know, some sort of DISTRIBUTED smurf-like system so that the bitty little attacks are coming from RANDOM hosts at RANDOM times.
Ticketing system. Let me say it again, ticketing system.
I've read Sys Admin bibles where it says, in the FOREWARD, "If you don't have a ticketing system, put down this book, and implement one. Then, come back and read some more."
Ticketing system. With time/date stamps, and use it RELIGIOUSLY.
If you liked the animation in FF: TSW, check out 'Last Flight of the Osiris' on the Animatrix DVD; they've really improved their skills. The opening sword fight is masterfully animated.
I always chose to interpret the midichlorians in the other direction; the Force causes midichlorians to accumulate. The little buggers are drawn to it; the better you are with the Force, and the more powerful your natural abilities with it, the more midichlorians you have. Therefore, it's a useful 'benchmark' for raw power. Still, though, an average powered master is probably going to whup a uber-powered novice, simply due to experience, control, and knowing all the little tricks.
Then, I saw Episode Two, and two Jedi Masters engaged in Force combat by, yes, dropping things on each other. And Yoda, very logically I thought, put a lot of effort into catching a big heavy prop, rather than using just a little bit to deflect it, or better yet, move the two unconcious bodies that were under it.
In many computer systems designed for orbit, that use, say, 486s, they'll put in three of them. Any given calc gets run through all three. Which ever answer is most popular between all three, that's the answer used.
Why? Because 1+1 = 2, unless a stray bit of radiation or cosmic energy has flipped a bit in your processor.
My understanding was that he was hand animated based on motion capture/actors doing things.
Let me, however, re-phrase my point. If you consider the two main methods of animating a model to be 'pre-defined motions' and 'dynamically generated,' then mocap, by definition, is type one. And it shows.
You can get type 1.5 by key-frames and interpolation, but type 2 is where I'd like to see things wind up.
With Rainbox Six, for example, they took a man, punched him *really hard* in various spots with a pole, and recorded him falling down. That simulates being shot.
The problem with this, or course, you see in games like Splinter Cell; Sam's running, or jumping, or rolling, or shooting. But he can't really run into a jump, miss, land, roll into a shooting stance and start peeling off rounds.
But nowadays, with tons of processor, and a good physics model, it can be just as good to build your models properly, and let the engine figure it out. Terra Nova: Strike Force Centauri, Die By The Sword (I believe) and Oni, for example, played with this early on; Unreal Tournement 2003 seems to be the current champ.
Myself, for video games, I'd avocate using mocap to more accurately build your models and tweak your physics engine, then let the engine actually do things. When my model's running up a hill, I want to see him leaning forward to place his center of gravity. When he gets shot, I want to see him fall back, then down, then start rolling down the hill. When he's lying on the ground, I want to see his arm tracking where I'm aiming; I want to see him use his other arm to lift himself up off the ground.
Sure, the same could happen with Linux. But there it is a web of trust in force, official CRCs to check against. Nothing like that exists for closed source products, because the company itself is distributing it, noone else. Naturally, such trojaned versions be very bad for the parent company.
Unless, say, your FTP server gets rooted, you don't notice for MONTHS, and nobody ever notices.
I seriously doubt that having the code open does anything, in real and actual terms, to improve security or prevent trojans. If anything, all it serves to do is let you track things down after the fact. But I doubt that any appreciable number of OSS users give a serious audit to any code they download.
I think it's Australia, especially the rural/outback areas, where if, in a bar, you empty your glass, turn it over, and thunk it down on the bar/your table, that's *exactly* what you're saying.
Entrapment is a Law Enforcment Officer walking up to you and saying 'Hey, man, you want to buy some crack?' then, not taking no for an answer, convincing you to buy it, and busting you.
Legitimate undercover work is said LEO walking up to you, saying 'Hey, man, you want to buy some crack?' and you saying 'yeah, man, I'm jonsing for a fix real bad.' Or, better, you walking up and saying 'Hey, got any crack?' and buying it.
And one of the reasons it, or it's netblock, as most of the RBLs don't seem particularly fine grained, is often that users on their own connections are running mail servers.
Well, if 'cleaning up' involves reformatting from known good media, restoring from known good backups, or recovering as much data as safely possible from not-so-good backups, patching and securing against future attacks, that could easily run up to several hundred bucks.
If it's running fixsobig.bat and walking away, sure.
He's the guy who thinks playing Doom will turn us into a generation of killers. But the rest of the book is an excellent study into the psychology of killing. Very insightful, in places.
An interesting article from the School of Common Sense shows that your public actions are being monitored by everybody who sees them!
"The privacy implications of this are staggering," says some guy who gets inflammed by things. "People could figure out all sorts of patterns about your life. Why, if they observe you going to the pet store, they could actually figure out that you likely own a pet! Next thing you know, you'll be getting subscription offers for pet magazines. Nobody needs that."
People who fear this massive intrusion of privacy have several options open to them. First, the use of full face masks, and body costumes, can confuse potential observers. Make sure to change masks and costumes frequently. Visiting stores and locations that you wouldn't normally visit can 'sour' their tracking data as well.
"If you have children, drop them off at a school that they don't attend," says Imflammatory Boy, "and tell them to walk to their real school."
For the unaware, you take a trusted third party, and hand them the item. They confirm to the buyer that they have it, in good condition, who then hands them the money. They confirm that they have a valid payment, then give the payment to the seller, and the item to the buyer.
Slashdot Mirror
As far as I'm concerned, saying that I can't decode the satellite signals being beamed into my house (especially since I live in Canada, where you *can't buy* the service) is like saying that if I happen to walk past a venue that a band is playing, and I can hear the music, I owe them the price of a ticket.
Exactly. This is intended to allow you to protect *your* docuements; not to force you to use MS stuff.
Or is using an encrypted filesystem suddenly a ploy to 'lock you in' to using that OS? No, of course not. You want to move your data, you save it somewhere else.
Well, guess what. Want to use your docs in another program? You save them to RTF or CSV or whatever the hell is appropriate.
But, of course, it's Microsoft, so there MUST BE an eeeeeevil ulterior motive.
Ah, but that's the debate. Was she covering her own ass, or was she throwing herself upon the sword, to save NASA?
Lemonade lives on.
Incorrect.
Snow White: The Wicked Queen falls down a cliff and dies.
Little Mermaid: Ursula is pierced through the heart with a large sailing ship. Aside: in the Little Mermaid Two, Morgana, Ursula's sister, refers to this. "Now why couldn't dear Ursula attend? Oh, yes, I remember, it's because YOU ALL SISH-KEBOBED HER!' Morgana, at the end of the story, is imprisioned in a block of ice.
Disney's Atlantis: Helga Sinclair dies, after being betrayed and thrown off of an airship, and she tries to take said airship, and it's crew, with her. Note that we also see such wonderful things as the beating death of a king. One of the better Disney movies, with a concious effort not to include any cute anthropomorphic animal sidekicks.
Those are some that I can think of off the top of my head, at least.
Working with good tech writers is a dream (Zvi and Tamsin, I'm talking to you!) and working with bad tech writers is a nightmare.
Remember, having the best product in the world is useless unless you have the docs to back it up. And you know your tech docs are good when your support people are referring to them on a regular basis.
Yes, if you want contiguous denials of service. But you know what? Five minutes here, ten minutes there, works a hell of a lot better than blam, it's down.
See 'the death of a thousand cuts.'
Yeah, because there's no way in HELL that anybody who could design this sort of system could POSSIBLY think to, gosh, some sort of, I don't know, maybe.... randomize the times they attack? Or even build, oh, I don't know, some sort of DISTRIBUTED smurf-like system so that the bitty little attacks are coming from RANDOM hosts at RANDOM times.
Good thing, too.
Ticketing system. Let me say it again, ticketing system.
I've read Sys Admin bibles where it says, in the FOREWARD, "If you don't have a ticketing system, put down this book, and implement one. Then, come back and read some more."
Ticketing system. With time/date stamps, and use it RELIGIOUSLY.
The Morris worm.
Back in the day when you could telnet into sendmail, ask it for root, and have it cheerfully comply.
Back in the day when you could overflow lpr and, guess what, get root.
Folks, UNIX isn't any more secure than NT, it's just been around longer, and had more bandaids put onto it.
If you liked the animation in FF: TSW, check out 'Last Flight of the Osiris' on the Animatrix DVD; they've really improved their skills. The opening sword fight is masterfully animated.
"Do not look into laser with remaining eye."
A wonderful book for this sort of thing is 'The Science of Superheroes.'
I always chose to interpret the midichlorians in the other direction; the Force causes midichlorians to accumulate. The little buggers are drawn to it; the better you are with the Force, and the more powerful your natural abilities with it, the more midichlorians you have. Therefore, it's a useful 'benchmark' for raw power. Still, though, an average powered master is probably going to whup a uber-powered novice, simply due to experience, control, and knowing all the little tricks.
Then, I saw Episode Two, and two Jedi Masters engaged in Force combat by, yes, dropping things on each other. And Yoda, very logically I thought, put a lot of effort into catching a big heavy prop, rather than using just a little bit to deflect it, or better yet, move the two unconcious bodies that were under it.
Oh well.
In many computer systems designed for orbit, that use, say, 486s, they'll put in three of them. Any given calc gets run through all three. Which ever answer is most popular between all three, that's the answer used.
Why? Because 1+1 = 2, unless a stray bit of radiation or cosmic energy has flipped a bit in your processor.
My understanding was that he was hand animated based on motion capture/actors doing things.
Let me, however, re-phrase my point. If you consider the two main methods of animating a model to be 'pre-defined motions' and 'dynamically generated,' then mocap, by definition, is type one. And it shows.
You can get type 1.5 by key-frames and interpolation, but type 2 is where I'd like to see things wind up.
Depends on what you're doing, actually.
With Rainbox Six, for example, they took a man, punched him *really hard* in various spots with a pole, and recorded him falling down. That simulates being shot.
The problem with this, or course, you see in games like Splinter Cell; Sam's running, or jumping, or rolling, or shooting. But he can't really run into a jump, miss, land, roll into a shooting stance and start peeling off rounds.
But nowadays, with tons of processor, and a good physics model, it can be just as good to build your models properly, and let the engine figure it out. Terra Nova: Strike Force Centauri, Die By The Sword (I believe) and Oni, for example, played with this early on; Unreal Tournement 2003 seems to be the current champ.
Myself, for video games, I'd avocate using mocap to more accurately build your models and tweak your physics engine, then let the engine actually do things. When my model's running up a hill, I want to see him leaning forward to place his center of gravity. When he gets shot, I want to see him fall back, then down, then start rolling down the hill. When he's lying on the ground, I want to see his arm tracking where I'm aiming; I want to see him use his other arm to lift himself up off the ground.
Unless, say, your FTP server gets rooted, you don't notice for MONTHS, and nobody ever notices.
I seriously doubt that having the code open does anything, in real and actual terms, to improve security or prevent trojans. If anything, all it serves to do is let you track things down after the fact. But I doubt that any appreciable number of OSS users give a serious audit to any code they download.
I think it's Australia, especially the rural/outback areas, where if, in a bar, you empty your glass, turn it over, and thunk it down on the bar/your table, that's *exactly* what you're saying.
Entrapment is a Law Enforcment Officer walking up to you and saying 'Hey, man, you want to buy some crack?' then, not taking no for an answer, convincing you to buy it, and busting you.
Legitimate undercover work is said LEO walking up to you, saying 'Hey, man, you want to buy some crack?' and you saying 'yeah, man, I'm jonsing for a fix real bad.' Or, better, you walking up and saying 'Hey, got any crack?' and buying it.
And one of the reasons it, or it's netblock, as most of the RBLs don't seem particularly fine grained, is often that users on their own connections are running mail servers.
Well, if 'cleaning up' involves reformatting from known good media, restoring from known good backups, or recovering as much data as safely possible from not-so-good backups, patching and securing against future attacks, that could easily run up to several hundred bucks.
If it's running fixsobig.bat and walking away, sure.
Go find On Killing, by Lt. Col. Grossman.
He's the guy who thinks playing Doom will turn us into a generation of killers. But the rest of the book is an excellent study into the psychology of killing. Very insightful, in places.
An interesting article from the School of Common Sense shows that your public actions are being monitored by everybody who sees them!
"The privacy implications of this are staggering," says some guy who gets inflammed by things. "People could figure out all sorts of patterns about your life. Why, if they observe you going to the pet store, they could actually figure out that you likely own a pet! Next thing you know, you'll be getting subscription offers for pet magazines. Nobody needs that."
People who fear this massive intrusion of privacy have several options open to them. First, the use of full face masks, and body costumes, can confuse potential observers. Make sure to change masks and costumes frequently. Visiting stores and locations that you wouldn't normally visit can 'sour' their tracking data as well.
"If you have children, drop them off at a school that they don't attend," says Imflammatory Boy, "and tell them to walk to their real school."
It's called 'escrow.' Very useful.
For the unaware, you take a trusted third party, and hand them the item. They confirm to the buyer that they have it, in good condition, who then hands them the money. They confirm that they have a valid payment, then give the payment to the seller, and the item to the buyer.