That was his point. Any hash that maps a large (infinitely large, in most cases) space onto a finite ones will always have collisions, it's just a question of how easy they are to find. If you don't want to have have collisions, you have to send the whole file.
No DoS attack ever has more than a CHANCE of succeeding; Something can always go wrong. That doesn't change the fact that you tried to take down the service.
The goal of this program is to raise their operating costs prohibitively, so that they are forced to take their sites offline. That is most certainly a DoS attack, even if it's not a conventional SYN flood or other DDoS attack that cripples their server directly.
And cutting the power line to someone's server is most definitely a DoS attack.
If you don't understand at this point that the goal is to force these servers offline thereby denying any users service, nothing I can say will ever get through to you anyhow.
If you flood them with so much traffic that their bandwidth costs rise to the point where they have to shut down, and so in intentionally, remind me again how you're not denying anyone access to their site?
With airport metal detectors, if you ask me. You know most people are gonna forget to remove their *passport* before going through the scanner... after all, what the hell would be metal in there, and most people are uneasy about letting their passports out of their possession, even just for a trip through the metal detector.
You want to look at HyperTalk and AppleScript, both from our friends in Cupertino.
Virtually every single programmer I know of who has ever had to work with AppleScript hates it with a passion. The best any of us can say is that the functionality it provides is awesome for controlling other apps, but that we've never managed to write an AS script longer than 5 lines without resorting to modifying an existing example elsewhere.
For the record, Dijkstra also advocated formal provability as the sole criterion for demonstrating program correctness. A nice idea for a theorist, perhaps, but utterly unimplementable in the general case.
Just wanna point out Dijkstra's view on CS in general, not necessarily to discredit his argument, but to point out that his conception of computer science and programming differed radically from the realities of today.
Gaim doesn't need AOL, MSN, etc. It works just fine with Jabber, an open, standards-based, extensible, and otherwise buzzword and hippie-compliant instant messaging protocol. There's only one problem: No one actually uses it!
Gaim's user base, as a proportion of all IM users, is tiny, and is not likely to grow to the point where gaim by itself can make any significant difference in peoples' protocol of choice. As long as all your friends are on AIM, you're going to stay on AIM, even if means dropping gaim.
Forget new protocols, I'd really love for things like ftp:// and smb:// and WebDav to work reliably without forcing me to force-restart the Finder every time I try to use one of them...
Objective-C is awesome, but it's not appropriate for very high-performance systems; Its message-passing architecture entails significant overhead on method ("selector") calls, even compared to virtual methods in C++.
At least, so is my understanding. Correct me if I'm wrong.
I'm not actually familiar with the details of postcript at all, but it certainly seems a logical format to consider if printing things is your concern.
Well... I'm currently running one. Of course, in order to get grub back on there after Windows trashed the MBR with its bootloader, I had to boot into Knoppix live-CD, mount my Debian partition (with -o dev), chroot in and install grub, and then manually set up menu.lst...
Oh believe me, I would love to ditch my NAT. I have several Linux/OS X boxes running behind it I'd love to be able to access directly over ssh, ftp, or whatever from outside the network without screwing with port mapping, not to mention any kind of file transfer app, hosting multiplayer games.... the list goes on. But I'm just playing devil's advocate, because I think that until I can switch to IPv6 painlessly and thoughtlessly, while still keeping EVERYTHING that I'm used to (either through IPv6 versions, proxies, co-existent Ipv4 and v6, or whatever), it's not going to go anywhere. NATs are annoying, but not nearly as annoying as being restricted to accessing your server from all of the 20 IPv6 enabled boxes currently out there. (Sarcasm, but you get the point).
It is not the games that are at fault, but the mass influx of casual gamers during the PlayStation days.
Yeah! I agree! Fuck the casual gamers! If they're not willing to devote their entire lives to playing their games, they shouldn't be playing them at all!
I'm sorry. You raised some very good points, but that sentence just pissed me, an occasional and definitely casual gamer, off.
Can't answer all of those, but as for Why is "&&" different from "and"? Ditto for "||" and "or", etc. It's always been that way, at least for perl 5 (I have no earlier perl knowledge)
and and or have much lower precedence than && and ||, the idea being that the latter should be used for logical expression ($a || $b), and the former for a sort of concise control structure (using short circuit evaluation), i.e.
open(FIN,$file,"<") or die("Unable to to open $file: $!");
Since they have such low precedence, it's (practically?) guaranteed that you can safely use them for that, and they will be evaluated only after the entire first operand.
Can't speak for the others, but I've done some experimenting, and the ssh:// one at least is fixed. LaunchServices now passes the entire URL specified as the URL to connect to instead of letting it get parsed as ssh's command-line, so that exploit should be closed, unless someone a lot more cunning than I can figure out how to break it.
What GNUstep needs is a refactoring to make it 100% compatible with the modern Cocoa object APIs. Then and only then will it become possible to write to Cocoa and then recompile on Linux.
Unfortunately, that's not the only problem. The format for the.nib interface definition files generated by Interface Builder is closed, so cross-platform GNUStep/OS X apps have to maintain two sets of interface files, or else use one of the XML solutions that GNUStep is working on. The former is an obvious nuisance, and none of the cross-platform GNUStep solutions are nearly as nice as Interface Builder (I've never worked with GNUStep, but IB is nice enough I'm fairly confident of that. Someone do correct me if I'm wrong).
OS X developers are used to working with IB, and are not going to easily switch to an inferior environment just to make apps work on Linux.
Slashdot Mirror
That was his point.
Any hash that maps a large (infinitely large, in most cases) space onto a finite ones will always have collisions, it's just a question of how easy they are to find. If you don't want to have have collisions, you have to send the whole file.
No DoS attack ever has more than a CHANCE of succeeding; Something can always go wrong. That doesn't change the fact that you tried to take down the service.
The goal of this program is to raise their operating costs prohibitively, so that they are forced to take their sites offline. That is most certainly a DoS attack, even if it's not a conventional SYN flood or other DDoS attack that cripples their server directly.
And cutting the power line to someone's server is most definitely a DoS attack.
If you don't understand at this point that the goal is to force these servers offline thereby denying any users service, nothing I can say will ever get through to you anyhow.
If you flood them with so much traffic that their bandwidth costs rise to the point where they have to shut down, and so in intentionally, remind me again how you're not denying anyone access to their site?
With airport metal detectors, if you ask me. You know most people are gonna forget to remove their *passport* before going through the scanner ... after all, what the hell would be metal in there, and most people are uneasy about letting their passports out of their possession, even just for a trip through the metal detector.
Virtually every single programmer I know of who has ever had to work with AppleScript hates it with a passion. The best any of us can say is that the functionality it provides is awesome for controlling other apps, but that we've never managed to write an AS script longer than 5 lines without resorting to modifying an existing example elsewhere.
For the record, Dijkstra also advocated formal provability as the sole criterion for demonstrating program correctness. A nice idea for a theorist, perhaps, but utterly unimplementable in the general case.
Just wanna point out Dijkstra's view on CS in general, not necessarily to discredit his argument, but to point out that his conception of computer science and programming differed radically from the realities of today.
Gaim doesn't need AOL, MSN, etc. It works just fine with Jabber, an open, standards-based, extensible, and otherwise buzzword and hippie-compliant instant messaging protocol. There's only one problem: No one actually uses it!
Gaim's user base, as a proportion of all IM users, is tiny, and is not likely to grow to the point where gaim by itself can make any significant difference in peoples' protocol of choice. As long as all your friends are on AIM, you're going to stay on AIM, even if means dropping gaim.
If you want to do something meaningful, go vote and tell all your friends to vote.
Tell you what. Don't go vote. You have my personal guarantee that your not voting will not alter the outcome of the election in a noticeable manner.
No promise for all your friends, though.
Forget new protocols, I'd really love for things like ftp:// and smb:// and WebDav to work reliably without forcing me to force-restart the Finder every time I try to use one of them ...
Please, try not to sound so stupid...
...
An ironically apropos sig
Objective-C is awesome, but it's not appropriate for very high-performance systems; Its message-passing architecture entails significant overhead on method ("selector") calls, even compared to virtual methods in C++.
At least, so is my understanding. Correct me if I'm wrong.
Google releases Google Life Search
I'm not actually familiar with the details of postcript at all, but it certainly seems a logical format to consider if printing things is your concern.
Not a misconception: a fact. If the espresso isn't pepping me up, what is? The demi-mug?
Placebo effect?
Well
Of course, in order to get grub back on there after Windows trashed the MBR with its bootloader, I had to boot into Knoppix live-CD, mount my Debian partition (with -o dev), chroot in and install grub, and then manually set up menu.lst
But it can be done
Oh believe me, I would love to ditch my NAT. .... the list goes on.
I have several Linux/OS X boxes running behind it I'd love to be able to access directly over ssh, ftp, or whatever from outside the network without screwing with port mapping, not to mention any kind of file transfer app, hosting multiplayer games
But I'm just playing devil's advocate, because I think that until I can switch to IPv6 painlessly and thoughtlessly, while still keeping EVERYTHING that I'm used to (either through IPv6 versions, proxies, co-existent Ipv4 and v6, or whatever), it's not going to go anywhere.
NATs are annoying, but not nearly as annoying as being restricted to accessing your server from all of the 20 IPv6 enabled boxes currently out there. (Sarcasm, but you get the point).
Yes. The purpose of already working painlessly with the existing infrastructure without any significant thought on the part of the user.
It is not the games that are at fault, but the mass influx of casual gamers during the PlayStation days.
Yeah! I agree! Fuck the casual gamers! If they're not willing to devote their entire lives to playing their games, they shouldn't be playing them at all!
I'm sorry. You raised some very good points, but that sentence just pissed me, an occasional and definitely casual gamer, off.
Why is "&&" different from "and"? Ditto for "||" and "or", etc.
It's always been that way, at least for perl 5 (I have no earlier perl knowledge)
and and or have much lower precedence than && and ||, the idea being that the latter should be used for logical expression ($a || $b), and the former for a sort of concise control structure (using short circuit evaluation), i.e.Since they have such low precedence, it's (practically?) guaranteed that you can safely use them for that, and they will be evaluated only after the entire first operand.
Can't speak for the others, but I've done some experimenting, and the ssh:// one at least is fixed. LaunchServices now passes the entire URL specified as the URL to connect to instead of letting it get parsed as ssh's command-line, so that exploit should be closed, unless someone a lot more cunning than I can figure out how to break it.
Step 4: Play music at loud volume and cringe at distortion caused by music being re-encoded twice into a lossy format.
Don't know if BBSpot ever had "the" - I think The Onion has that one in the bag, but it was, and still is, the top for are.
How a Language can support the BitTorrent protocol.
Unfortunately, that's not the only problem.
The format for the
OS X developers are used to working with IB, and are not going to easily switch to an inferior environment just to make apps work on Linux.
I have a bad feeling you just signed your own death warrant...