That's like saying Helloween was the best thing to come out of the 80s.
(OTOH, Kataklysm, Dying Fetus, Cephalic Carnage, Yakuza, The Red Chord, and a lot of others are releasing consistently good material for us metalheads, so we should really be thankful)
Cage's work is fairly well known, and has quite a bit of commercial value. Well. A lot for the style of music he does; he's not Britney, but as far as twentieth century *composition* (as opposed to pop), he's probably the most famous.
On the other hand, I like obscure twencen experimental music, and I've never heard of Mike Batt, so...
Of course, the N1 never successfully flew. Energia was a good rocket, but only launched twice, and much like Saturn V, it no longer exists; they've all been broken down. The Russian circumlunar program was plagued with problems - they had 8 failures prior to a successful circumlunar (which occurred post-Apollo 8).
Don't get me wrong, the Russians have made some great hardware - the Soyuz is an amazing capsule. And their liquid-fuel engines are generally much, much better than ours (note that the EELV Atlas uses a Russian-built engine). But their experience with launches headed out of Earth's gravity well is no better, and arguably worse, than that of the US.
Really, in the end, a joint effort is the only thing that would make any sense, but with Bush in office, that is (to say the least) unlikely.
Who says the machine can't print out "You voted for A" and internally tally B? And if the margin of B over A is enough, but not too much, who'll ever go back and recount all those paper ballots?
The point is that if the internals of the machine aren't open to examination, we don't know. We need to approach this from all angles, not just put our trust in one facet of the problem solving the whole thing. Much like there are simple attacks against verified source (trapped compilers, substitution of unverified source, etc.), trusting that a paper printout is an accurate representation of your vote has simple attacks as well (print A, count B). The only way you can get around that attack is to use the printed ballots as the primary source, in which case - why not just use paper ballots and hand-count them?
Much like most engineers, engineers in the automotive industry really do make their best effort to make sure a car is as safe as they can make a 5000 lb block of steel traveling at 70 mph.
I hope I'm right too, because otherwise stories like yours will remain the minority amongst far too many others.
I'm actually moving into Chicago, further away from work (if you know where 53 hits Lake Cook Rd, I work way, way, way out there) just so I can take Metra to work. It'll probably add 30-40 minutes to my commute, but it will be *worth* it not to have to deal with the psycop^H^H^H^H^H^Hother drivers on the roads here.
*California* is hardly a standard to compare to. How long has it been since there was a new power plant in Cali?
I live in a state with significantly worse conditions (icestorms, wind, higher electrical load due to higher summer temperatures than NoCal, frigid temperatures, etc.) and we had no outages at all this winter. One brownout in the summer. No blackouts at all.
Comparing California to the rest of the country is like comparing, I don't know... the rest of the country's emissions laws to California's.
The paper trail is worthless if the machine is rigged to produce results that are close enough not to trigger recounts, but crooked enough to throw a race.
Both paper and electronics need to be secure and proper to be usable.
The entire process needs to be public; the hardware, the software, the procedures. And then we need a backup, a human-verifiable trace. That's the only way it's even worth doing.
Thus, I feel that transparent source offers value.
I'm saying that ABS is interlocked; unless your foot is on the brake (or the same factors that cause your brakes to engage without your foot on the brake are in play) it can't engage. If A is required for B to happen, the probability of B cannot be greater than the probability of A.
I.E. p(!brake) is X. p(ABS) is also X, because ABS implies !brake.
You tell the usher where you're going to sit, of course. This works a lot better in theater than movies, to tell the truth, but with the exception of crowded opening night theaters, its usually not too hard to pick your seat.
And I have, in fact, asked ushers to do this for me, when I was on call for something.
The reminder works great for people who don't need to take calls; the ushers work for those who do.
LEAVE IT WITH THE HOUSE MANAGER AND/OR USHER, WITH INSTRUCTIONS TO GET YOU IF IT RINGS.
Exactly the same way that on-call doctors worked prior to the advent of pagers and cellphones; they let the hospital know "I will be at the theater from 9 to midnight" and if the call was for them, the house manager would (quietly) find them and tell them.
Don't see why not. The idea isn't to adjust to sudden changes in speed, the idea is to keep you from being closer to the guy in front of you than your stopping distance allows; having worked with this kind of system, its quite possible.
As to the curve thing; phased-array steered beams that track your turning angle, more or less.
Good on the statie, though; I once had a guy damn near take the nose off my car as he made a sudden left across my lane of traffic (I was left lane, he was center). The irony is; he was turning into a police station parking lot. A cop was walking out to his cruiser, watched the guy do this, and promptly pulled him out of his car and arrested him. Cuffs and all. Marched him inside, asked me to park the guys car. I went up to that cop and shook his hand.
The mechanism for ensuring that bug fixes are rolled back in is that, presumably, they will continue to keep their source open; when they hit their next release, they will open it, and the community can verify bug fixes.
We are better off. As I said, not much better off, since my major concerns with e-voting are much more in verifiability (paper voter-verifiable receipts would help here, as well as 3rd-party maintainence of the voting machines to avoid problems like Diebold's patching with untrusted/checked versions). But still better.
It isn't the wrong road. Its just one of several right roads. Publicly visible source to the software (even if not OSI-style open source, at least publicly verifiable), with voter-verifiable receipts, a clear chain of custody for all votes, common security precautions, and a write-only archival media for ALL changes/edits made, are all needed. There are probably other things I've forgotten, but these would be a good start. And this is a step down one of those roads.
Check kismac and ettercap; both run on OS X, and kismac is much, much more useful than Macstumbler (although I kept them both around, as Macstumbler has some advantages too).
Never used Macsniffer, but ettercap is a pretty useful thing.
Canada's the 51st state anyway, so you guys were included when he said the US.;)
Actually, I'm curious as to where you live that you have weekly outages; I haven't seen one in almost a year, and I live in a major city (Chicago). When I lived in a smaller metro area (Ann Arbor), power went out maybe twice a year, tops, and nearly always due to a major icestorm. The grids in the US are pretty good, for the most part.
No, it really isn't unfair. My interest 'level' is exactly the same as that held by anyone who's been thrown into vi, or emacs, or e, without any desire to use it, by a distro's badly configured default editor, by a typo on the command line (e is particularly bad here), or for any other reason. I don't research it because my only 'need' for vi is for it to EXIT, which it doesn't provide an easy method of for the unaware (beyond suspend-kill). I have no need for an advanced text-mode editor, and only rarely have a need for much more than pico provides. Why exactly should I do ANY research beyond "This is how to exit?"
Unless the default configuration provides for the ability to obtain help and/or exit without prior knowledge, I don't care about what it can be configured to support. Configurability doesn't count for shit when the user vows in disgust to never use the editor again after a minute spent fighting trying to figure out how to exit the program.
And you are very, very unlikely to ever work with me, if you contribute code to editors - I'm not a programmer, for one thing.
Slashdot Mirror
Blind Guardian?
I mean... Opeth, yeah. Dream Theater.... I guess.
But Blind Guardian?
That's like saying Helloween was the best thing to come out of the 80s.
(OTOH, Kataklysm, Dying Fetus, Cephalic Carnage, Yakuza, The Red Chord, and a lot of others are releasing consistently good material for us metalheads, so we should really be thankful)
Cage's work is fairly well known, and has quite a bit of commercial value. Well. A lot for the style of music he does; he's not Britney, but as far as twentieth century *composition* (as opposed to pop), he's probably the most famous.
On the other hand, I like obscure twencen experimental music, and I've never heard of Mike Batt, so...
Resurrecting Energia (the booster people are throwing around) would probably consume their entire budget.
Of course, the N1 never successfully flew. Energia was a good rocket, but only launched twice, and much like Saturn V, it no longer exists; they've all been broken down. The Russian circumlunar program was plagued with problems - they had 8 failures prior to a successful circumlunar (which occurred post-Apollo 8).
Don't get me wrong, the Russians have made some great hardware - the Soyuz is an amazing capsule. And their liquid-fuel engines are generally much, much better than ours (note that the EELV Atlas uses a Russian-built engine). But their experience with launches headed out of Earth's gravity well is no better, and arguably worse, than that of the US.
Really, in the end, a joint effort is the only thing that would make any sense, but with Bush in office, that is (to say the least) unlikely.
Remember that NZ is essentially the same environment as many other places on Earth.
Mars is not.
On the bright side, I've heard the new NERD album sucks, and the songs I've heard have done nothing to convince me otherwise.
Tell me (roughly) where you live, and if I know of a good college/freeform station near you, I'll tell you what it is.
If not:
WCBN
WFMU
WXOU
KTRU (might have been bought out, I forget)
KBOO
WSUM
WORT
Most, if not all, of those stream online. Give 'em a listen.
(obligatory note: I worked for CBN for a while, but no longer have any affiliation with them.)
Who says the machine can't print out "You voted for A" and internally tally B? And if the margin of B over A is enough, but not too much, who'll ever go back and recount all those paper ballots?
The point is that if the internals of the machine aren't open to examination, we don't know. We need to approach this from all angles, not just put our trust in one facet of the problem solving the whole thing. Much like there are simple attacks against verified source (trapped compilers, substitution of unverified source, etc.), trusting that a paper printout is an accurate representation of your vote has simple attacks as well (print A, count B). The only way you can get around that attack is to use the printed ballots as the primary source, in which case - why not just use paper ballots and hand-count them?
Much like most engineers, engineers in the automotive industry really do make their best effort to make sure a car is as safe as they can make a 5000 lb block of steel traveling at 70 mph.
I hope I'm right too, because otherwise stories like yours will remain the minority amongst far too many others.
I'm actually moving into Chicago, further away from work (if you know where 53 hits Lake Cook Rd, I work way, way, way out there) just so I can take Metra to work. It'll probably add 30-40 minutes to my commute, but it will be *worth* it not to have to deal with the psycop^H^H^H^H^H^Hother drivers on the roads here.
*California* is hardly a standard to compare to. How long has it been since there was a new power plant in Cali?
I live in a state with significantly worse conditions (icestorms, wind, higher electrical load due to higher summer temperatures than NoCal, frigid temperatures, etc.) and we had no outages at all this winter. One brownout in the summer. No blackouts at all.
Comparing California to the rest of the country is like comparing, I don't know... the rest of the country's emissions laws to California's.
The paper trail is worthless if the machine is rigged to produce results that are close enough not to trigger recounts, but crooked enough to throw a race.
Both paper and electronics need to be secure and proper to be usable.
The entire process needs to be public; the hardware, the software, the procedures. And then we need a backup, a human-verifiable trace. That's the only way it's even worth doing.
Thus, I feel that transparent source offers value.
No.
I'm saying that ABS is interlocked; unless your foot is on the brake (or the same factors that cause your brakes to engage without your foot on the brake are in play) it can't engage. If A is required for B to happen, the probability of B cannot be greater than the probability of A.
I.E. p(!brake) is X. p(ABS) is also X, because ABS implies !brake.
You tell the usher where you're going to sit, of course. This works a lot better in theater than movies, to tell the truth, but with the exception of crowded opening night theaters, its usually not too hard to pick your seat.
And I have, in fact, asked ushers to do this for me, when I was on call for something.
The reminder works great for people who don't need to take calls; the ushers work for those who do.
LEAVE IT WITH THE HOUSE MANAGER AND/OR USHER, WITH INSTRUCTIONS TO GET YOU IF IT RINGS.
Exactly the same way that on-call doctors worked prior to the advent of pagers and cellphones; they let the hospital know "I will be at the theater from 9 to midnight" and if the call was for them, the house manager would (quietly) find them and tell them.
Sorry to shout, but isn't it bleedingly obvious?
Or leave the phone with the house manager/usher, with instructions to get you if it rings.
You know. Like doctors used to do, when they were polite.
99% of the time its better to hit than rollover.
So 99% of the time the system is better than no system.
ABS will engage without your foot on the brake roughly as often as your BRAKE will engage without your foot on the brake.
Don't see why not. The idea isn't to adjust to sudden changes in speed, the idea is to keep you from being closer to the guy in front of you than your stopping distance allows; having worked with this kind of system, its quite possible.
As to the curve thing; phased-array steered beams that track your turning angle, more or less.
Good on the statie, though; I once had a guy damn near take the nose off my car as he made a sudden left across my lane of traffic (I was left lane, he was center). The irony is; he was turning into a police station parking lot. A cop was walking out to his cruiser, watched the guy do this, and promptly pulled him out of his car and arrested him. Cuffs and all. Marched him inside, asked me to park the guys car. I went up to that cop and shook his hand.
The mechanism for ensuring that bug fixes are rolled back in is that, presumably, they will continue to keep their source open; when they hit their next release, they will open it, and the community can verify bug fixes.
We are better off. As I said, not much better off, since my major concerns with e-voting are much more in verifiability (paper voter-verifiable receipts would help here, as well as 3rd-party maintainence of the voting machines to avoid problems like Diebold's patching with untrusted/checked versions). But still better.
It isn't the wrong road. Its just one of several right roads. Publicly visible source to the software (even if not OSI-style open source, at least publicly verifiable), with voter-verifiable receipts, a clear chain of custody for all votes, common security precautions, and a write-only archival media for ALL changes/edits made, are all needed. There are probably other things I've forgotten, but these would be a good start. And this is a step down one of those roads.
Check kismac and ettercap; both run on OS X, and kismac is much, much more useful than Macstumbler (although I kept them both around, as Macstumbler has some advantages too).
Never used Macsniffer, but ettercap is a pretty useful thing.
Canada's the 51st state anyway, so you guys were included when he said the US. ;)
Actually, I'm curious as to where you live that you have weekly outages; I haven't seen one in almost a year, and I live in a major city (Chicago). When I lived in a smaller metro area (Ann Arbor), power went out maybe twice a year, tops, and nearly always due to a major icestorm. The grids in the US are pretty good, for the most part.
Does practicing surgery make video gamers better?
THIS is the question the top Quake players are on the edge of their seats waiting to hear about...
Right now, all those problems exist.
Except that right now, we can't even verify that they've caught the obvious bugs.
It *is* a step in the right direction. Maybe not a big one, maybe not even an important one, but we are better off now than we were before.
No, it really isn't unfair. My interest 'level' is exactly the same as that held by anyone who's been thrown into vi, or emacs, or e, without any desire to use it, by a distro's badly configured default editor, by a typo on the command line (e is particularly bad here), or for any other reason. I don't research it because my only 'need' for vi is for it to EXIT, which it doesn't provide an easy method of for the unaware (beyond suspend-kill). I have no need for an advanced text-mode editor, and only rarely have a need for much more than pico provides. Why exactly should I do ANY research beyond "This is how to exit?"
Unless the default configuration provides for the ability to obtain help and/or exit without prior knowledge, I don't care about what it can be configured to support. Configurability doesn't count for shit when the user vows in disgust to never use the editor again after a minute spent fighting trying to figure out how to exit the program.
And you are very, very unlikely to ever work with me, if you contribute code to editors - I'm not a programmer, for one thing.