- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
re: lost package
I don't think it's really a coincidence. It's common to assume DC as a default location when actual mapping fails, for reasons from a database gap to a remote request failure, or when the coordinates aren't entered at all. I found Microsoft Weather doing that.
Admin
Caleb's post reminds me of an old SNL fake commercial about a company similar to UPS or FedEx that would back-date a package you forgot to send, and then take the blame with the recipient for why it showed up late. Maybe Outlook won't actually deliver it late, but make it look like you sent an email on time and it just got hung up in their service for awhile before delivery so that you can claim innocence....
Edit Admin
The Outlook issue looks like time zones. If 18 Oct 09:00 is "in 6 hrs", then it's likely around 03:00 local time; and to schedule something to arrive at 17 Oct 23:00 in the recipient's time zone, that would only require that the recipient is at least 4 hours behind the sender, which is quite plausible.
It's still confusing as hell, but not necessarily a WTF.