Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I tried, but after 30 seconds of looking at a blank white screen and "loading from didtheyreadit.com" (or whatever the name is), I (the human, not a program) timed out and hit the bak button. There's a limit to how much I'll do, even for science.
    • I discoverd the same thing. They are doing something tricky: they just keep sending data. They keep sending data to you do something else. This way they know for how long you read the message, which is about the same time their program ran.

      So, this is even more diabolical than I thought! They are also sucking bandwidth. Imagine a company deciding to use this (the intended market, I'm thinking), and that another company gets a lot of email from them. That is almost a denial-of-service attack! Lots o
      • I loaded the URL with wget.

        It is coming across at 1 B/s.

        [waiting...]

        Turned out to be 302 bytes large.
        • 302 bytes, eh?

          That would be about 5 minutes at 1 B/s, and they claim to measure times much longer than that. How long did it actually take? Did it get slower the longer it went on?
          • It was almost exactly 1 B/s the entire time.

            I'd almost bet that they eventually count bytes transferred as the method of doing the timing.

            We may actually be seeing wget, or some other part of the stack, giving up on the connection... the fact that it was almost exactly 5 minutes is suspect to me.