Are you so sure about that? I live pretty much next door to JSC, and the house's foundation as at sea level. If you dig a hole, it fills with water. You don't go very far down.
However, that wouldn't be a problem at all if the P2P systems were a little more intelligent - preferring more local connections for more remote (why download a movie from someone in norway when you can get it from the guy down the block?). Someone help me write this program.
Most people are too stupid to understand a bandwidth agreement.
"Can ah get mah AOLS groups? what about that word wide web? I gots to have my webs. What's this about BUSTABLE bandwidth? You best not be busting my computer, or I'mm'a sue you!"
As I understand, firewire is a mastering bus (each peripherial can control the whole bus - compared to USB, a chained/star system where you need a central controller for everything). So, it seems that if you had a firewire CDROM, you could hook it up to a firewire ripper/player, and if you had a firewire CDRW (and appropriate firmware in the ripper), you could burn it back to CD. I see problems in getting an interface that's small enough to be useful for simple playback, but large enough to let you control burning well. Probably power issues too. But it can probably be done.
Of course, if there were a moderation system implemented-- rating the comments-- like on Slashdot, it could be interesting.
Mmmm, yes, not moderation, but a peer web of trust. I don't think it's feasable for this type of project with current technology, but it seems to work great (on paper) for the P2P IM client I'm working on. Basically you have a list of friends and their public keys. The software validates the message/presence of the other user by key alone. You can keep a local list of "friends" with levels of trust.
Not to mention being somewhat impossible in some locations like, say, my home town of Houston. The area where I live is about 20 feet above sea level. If you dig a hole, it fills with water.
Normal slashdot staff overreacting again. You can turn that ID off. Granted, they should make it default to off, and ask you before they go around putting out supercookies, but it's possible to fix the hole. Even in WMP6.x. This was going across bugtraq today. Apparently, if you have the ID backdoor disabled, it generates a random number each time the control is queried. Spare his page, though, I wrote this with no replies (first post, almost), and the page was already horribly slow.
Right to bear arms, baby, right to bear arms. I love living in Texas, too. Someone busts in my house (which conveniently completely surrounds my home office), *bang* they're dead. Now, of course I'm going to extend a courtesy to law officials, at least give them a chance to tell me they don't have a warrant before perforation ensues.
Sounds good to me. As I see it though, apple has had issues capturing the market because they want to make dumbed down computers for dumbed down yuppies. This may change with OSX, but I think they're already stuck with the image.
Heavens yes! I'm glad someone said it (otherwise I would have had to). x86 was great when it was invented, but it's horribly antiquitated now. Get me something modern, that doesn't have to be hacked to death to work with modern hardware and software. Forget backward compatibility, I don't like anything that's out right now any way!
What I want to know is why a government agency is pissing money into supporting crap like this. I'm assuming it's from some NORAD PR budget or something.
The problem is that with dynamic disk spanning, it fills the space sequentially: if you span a 20, a 40, and a 20 gb drive, winders fills the first 20 gb, then the 40 gb, before it starts on the final 20. Useful in some aspects I suppose, but I suppose the focus is on seamless extension, not speed or reliability (then again, if you want those, get a hardware RAID).
Um executing an executable is a flaw in your email client? You realize that you don't even have to have email for this worm to infect and damage your system, right?
Someone targeting the ten thousand employees at my company's parent. We're the only branch that uses Exchange, everyone else fell into the groupwise thing.
At work, we got it about 1100 EST. One user got it and ran it, and it cascaded. Our servers groaned for about 30 seconds, by that time, the mail admin had run into the server room and yanked the network cable to them. Honestly, I don't think the fault rests on these kids at all. Sure, I guess they should face punishment if they broke the law, but that's their country's problem. I don't blame them.
If our users had listened to the rules, this wouldn't have been a problem. But within 30 seconds of the attachment entering our network, over 50 users had run it. Why can't someone hold the irresponsible user at fault? The instructions are easy - don't run attachments you weren't expecting. Instead of blaming some kids for playing around with code, why can't we find fault in the people that don't follow their instructions?
Yeah, I'm ranting, but to make something constructive out of my waste of bandwidth, how can we get the users to listen? Anyone have effective tools? Yeah, I'm all for firing the ones that can't observe policy, but that would mean firing my boss too. And she's actually pretty decent, as far as managers go.
Tried that. The lag is hell. Get a cheap cell instead. With most cell plans you get free long distance too. That's what I had when it was up, a cell and ricochet, and it was great. I can't wait for them to get it back up. Oh, and does anyone else think Emilie Kelly (marketing vp) is cute?
Judges do not have the luxury of ignoring the law, or just saying "oh well" when people fail to follow their lawful orders.
Bullshit. Constitutional review is a power delegated to the judicial branch. When they come across a "wrong" law (an unconstitutional law), they can declare it void. Now, I don't remember the specifics of the situation (if it was a state law, probably constitutional, or a federal law, pretty much unconsititutional), so I'm not saying anything about this case, but I have to play slashdot-whore and argue with the basis of your argument.:)
Manual transmissions have a neutral safety switch, which requires the clutch pedal to be depressed in order to start. Bypassing that switch on some vehicles can cause problems with the computer, cruise control, etc.
Not true. On most cars it's a simple pedal-top switch. You can easily and safely wire a relay in if you need to, or just bypass it alltogether. Where do you get this bunk?
I just got through telling both of my primary users (I work closely with two out of about a hundred). Just this morning we'd talked about not running attachments we weren't expecting. Not six hours later, Luser X spews on my server, I send off emails, then get a flood of virii in my inbox, and I notice attachment-laden emails from my two main users just as my server teeters on the brink, then dies hard. This is in a matter of thirty seconds. Users are stupid. Plain and simple.
Remember, computers do exactly what you tell them to. If a computer makes a mistake, it's because somewhere, a user told it to.
I read some of the documentation, but I can't find details on a couple of questions. Do the servers authenticate with each other? It was implied, but how deep is it? Are the SHA signatures signed to the originating server (or client/trollbox) too? I think this kind of model is great, but if you don't have some nifty authentication/accountability, it can be wide open for abuse. I'm sure anyone reading slashdot can imagine a vengeful spammer flooding the network with bogus or malicious hashes.
. . . i know from personal experience of starting a CD label that they are not "as [ir]relevant as buggy whip manufacturers".
Only because they already control all channels of publicity (radio slots, major store shelf space, commercial slots). Otherwise, it would simply be an exercise of borrowing money, just like any other business.
Slashdot Mirror
Are you so sure about that? I live pretty much next door to JSC, and the house's foundation as at sea level. If you dig a hole, it fills with water. You don't go very far down.
However, that wouldn't be a problem at all if the P2P systems were a little more intelligent - preferring more local connections for more remote (why download a movie from someone in norway when you can get it from the guy down the block?). Someone help me write this program.
No, bad idea.
As I understand, firewire is a mastering bus (each peripherial can control the whole bus - compared to USB, a chained/star system where you need a central controller for everything). So, it seems that if you had a firewire CDROM, you could hook it up to a firewire ripper/player, and if you had a firewire CDRW (and appropriate firmware in the ripper), you could burn it back to CD. I see problems in getting an interface that's small enough to be useful for simple playback, but large enough to let you control burning well. Probably power issues too. But it can probably be done.
Mmmm, yes, not moderation, but a peer web of trust. I don't think it's feasable for this type of project with current technology, but it seems to work great (on paper) for the P2P IM client I'm working on. Basically you have a list of friends and their public keys. The software validates the message/presence of the other user by key alone. You can keep a local list of "friends" with levels of trust.
dodeculation?
Not to mention being somewhat impossible in some locations like, say, my home town of Houston. The area where I live is about 20 feet above sea level. If you dig a hole, it fills with water.
Normal slashdot staff overreacting again. You can turn that ID off. Granted, they should make it default to off, and ask you before they go around putting out supercookies, but it's possible to fix the hole. Even in WMP6.x. This was going across bugtraq today. Apparently, if you have the ID backdoor disabled, it generates a random number each time the control is queried. Spare his page, though, I wrote this with no replies (first post, almost), and the page was already horribly slow.
Right to bear arms, baby, right to bear arms. I love living in Texas, too. Someone busts in my house (which conveniently completely surrounds my home office), *bang* they're dead. Now, of course I'm going to extend a courtesy to law officials, at least give them a chance to tell me they don't have a warrant before perforation ensues.
Sounds good to me. As I see it though, apple has had issues capturing the market because they want to make dumbed down computers for dumbed down yuppies. This may change with OSX, but I think they're already stuck with the image.
Heavens yes! I'm glad someone said it (otherwise I would have had to). x86 was great when it was invented, but it's horribly antiquitated now. Get me something modern, that doesn't have to be hacked to death to work with modern hardware and software. Forget backward compatibility, I don't like anything that's out right now any way!
Sounds absolutely great for everything but the NIC drivers . . .
Why not make something PDA-sized, and use a wired (or bluetooth) headset? It would be doubly nice if you could use it for voice recognition input.
What I want to know is why a government agency is pissing money into supporting crap like this. I'm assuming it's from some NORAD PR budget or something.
The problem is that with dynamic disk spanning, it fills the space sequentially: if you span a 20, a 40, and a 20 gb drive, winders fills the first 20 gb, then the 40 gb, before it starts on the final 20. Useful in some aspects I suppose, but I suppose the focus is on seamless extension, not speed or reliability (then again, if you want those, get a hardware RAID).
Um executing an executable is a flaw in your email client? You realize that you don't even have to have email for this worm to infect and damage your system, right?
Someone targeting the ten thousand employees at my company's parent. We're the only branch that uses Exchange, everyone else fell into the groupwise thing.
At work, we got it about 1100 EST. One user got it and ran it, and it cascaded. Our servers groaned for about 30 seconds, by that time, the mail admin had run into the server room and yanked the network cable to them. Honestly, I don't think the fault rests on these kids at all. Sure, I guess they should face punishment if they broke the law, but that's their country's problem. I don't blame them.
If our users had listened to the rules, this wouldn't have been a problem. But within 30 seconds of the attachment entering our network, over 50 users had run it. Why can't someone hold the irresponsible user at fault? The instructions are easy - don't run attachments you weren't expecting. Instead of blaming some kids for playing around with code, why can't we find fault in the people that don't follow their instructions?
Yeah, I'm ranting, but to make something constructive out of my waste of bandwidth, how can we get the users to listen? Anyone have effective tools? Yeah, I'm all for firing the ones that can't observe policy, but that would mean firing my boss too. And she's actually pretty decent, as far as managers go.
Tried that. The lag is hell. Get a cheap cell instead. With most cell plans you get free long distance too. That's what I had when it was up, a cell and ricochet, and it was great. I can't wait for them to get it back up. Oh, and does anyone else think Emilie Kelly (marketing vp) is cute?
Bullshit. Constitutional review is a power delegated to the judicial branch. When they come across a "wrong" law (an unconstitutional law), they can declare it void. Now, I don't remember the specifics of the situation (if it was a state law, probably constitutional, or a federal law, pretty much unconsititutional), so I'm not saying anything about this case, but I have to play slashdot-whore and argue with the basis of your argument.
Thankfully it's a del sol, a bit smaller than even a civic. Just enough space to react (AKA slam on the brake and curse like a sailor).
Not true. On most cars it's a simple pedal-top switch. You can easily and safely wire a relay in if you need to, or just bypass it alltogether. Where do you get this bunk?
I just got through telling both of my primary users (I work closely with two out of about a hundred). Just this morning we'd talked about not running attachments we weren't expecting. Not six hours later, Luser X spews on my server, I send off emails, then get a flood of virii in my inbox, and I notice attachment-laden emails from my two main users just as my server teeters on the brink, then dies hard. This is in a matter of thirty seconds. Users are stupid. Plain and simple.
Remember, computers do exactly what you tell them to. If a computer makes a mistake, it's because somewhere, a user told it to.
I read some of the documentation, but I can't find details on a couple of questions. Do the servers authenticate with each other? It was implied, but how deep is it? Are the SHA signatures signed to the originating server (or client/trollbox) too? I think this kind of model is great, but if you don't have some nifty authentication/accountability, it can be wide open for abuse. I'm sure anyone reading slashdot can imagine a vengeful spammer flooding the network with bogus or malicious hashes.
Only because they already control all channels of publicity (radio slots, major store shelf space, commercial slots). Otherwise, it would simply be an exercise of borrowing money, just like any other business.