On a long drive from LA to Portland I was the driver and I was bored, so I wrote a simple moon lander game (modeled from one I'd seen written in BASIC) for my new HP-25 programmable calculator by dictating instructions to the guy riding in the shotgun seat. The display showed your altitude on one side of the decimal place, velocity on the other side (and with the +/- sign) and remaining fuel in the exponent. After each iteration you entered how much fuel to burn on the next step and pushed R/S (Run/Stop) to continue. If you got down to zero altitude (or below) with a velocity less than some maximum value then you had made a successful landing. Otherwise you crashed.
Writing a good bug report is not easy, and users should not be expected to know what information the developer will need to find and fix the bug. They only want to report that there is a problem, and that they'd like it fixed.
That said, you can guide them to give more useful information. I found that making a form to fill out with all the details broken out into separate pieces gave us more useful information. Want to know how to reproduce the bug? Make that an individual question on the report. Which component where you using, or what web page were you on? Make that a specific question. A real person can follow up if necessary to get other information, and then they can file the "official" bug report in the form that the developer can understand and use.
If the asteroid has any rotational motion then the crater created by the first impactor will have moved out of the way of the second.
I tried this in Safari on Lion. Capital F required, but indeed just "File:/// " crashes it.
Then you get a pop-up asking if you want to report the problem to Apple? Sure.
But then that crashes with a pop-up reporting that crash reporter has crashed. Bonus!
Birds supposedly have UV vision, and some of their markings are for each other, and are more clearly distinguished by other birds that can see UV.
So you might consider observing birds and making sketches of their markings, much like the naturalists of 100 years ago, so that the rest of us can see what the birds can see of each other.
This is good. I take it to really mean that we'll see the end of PayPal by 2015.
I've run my own mail and web servers from my home for years, so I was worried about this when I was making the switch from Time-Warner cable (who didn't care, BTW) to Verizon Fios. One person I know reported that Verizon did indeed block port 25 (and port 80) inbound, while another told me his setup worked fine, once he replaced the free router they gave him with his own router.
And indeed, after making the switch, I still am able to get mail inbound on port 25. The modem/router they gave me does have controls to adjust security settings, which look a lot like Windows trusted -vs- untrusted controls. But I can't really tell if they do much. The key thing I found was to set up port forwarding to send port 25 to the machine in my internal network with the mail server. Same for port 80 to the web server.
Outbound I route through the ISP. Postfix makes that easy. I found a few years ago that certain domains I sent to, though not all of them, started bouncing mail even though I had an SPF record, just because my IP address was in a range listed as "dynamic" (i.e. "residential"). Clearly that's for spam control. Not everybody does this, and I could send direct to those who do not, but it was simpler to just send everything out via port 587 to the ISP.
How about a compromise? Keep the ethX names, but use the proposed scheme to have an unambiguous order in which the names are assigned.