Did you find an error or problem in an issue? This is the place to check it out: if it’s not mentioned here, please use the form below to report it. Reports will stay here for around 4 weeks before they roll off the bottom, so if you’re behind on reading you may not find an answer, but do check the next issue to see if it is mentioned.
For general comments or questions, please simply reply to the newsletter email or comment here.
|24 Sep 1528||The train hit a cement (powder), not concrete (slurry) truck.||None.|
|17 Sep 1527||None.||None.|
|10 Sep 1526||I understand some of you are seeing glitchiness, apparently due to an extra “p” (paragraph) tag in the Author’s Notes section. I didn’t see any problem when I sent a test to my gmail, but apparently some mailers aren’t as robust. Sorry for the hassle!||None.|
|3 Sep 1525||Bad link: the auction for The Apple script is here.||None.|
PLEASE Read This Before Using the Form:
- Please don’t submit an error already included above! (Obvious? Apparently not: I constantly get reports that are already listed. Please slow down so you don’t waste your time or mine!)
- Useful Reports: Actual errors in stories, URLs, or other things that actually matter to readers.
- Non-Useful Reports: Typos in reader letters or ads. Such are not my error!
- Honorary Unsubscribe errors are not listed here; its archive is kept up-to-date with any changes or corrections, so check the particular person’s page first. If you find something not already corrected there, feel free to use the form below to report it.
Sorry this all sounds really grumpy, but all I’m really trying to do is avoid literally hundreds of reports saying the same thing, and save your time. Thus: Thank You for your useful reports!
Submit an Error Report:
Thanks much for helping!