He probably works in OH&S (Occupational Health and Safety - or your local equivalent) or at an employer who has been burned in the past and now requires every possible risk to be itemised and managed (even if it makes a project cost 300% more).

I'd guess the potential killers have higher moral standards than the execs, and don't want to inflict the mental pain / sorrow on the not-guilty family members. Sadly this means the morally bankrupt studio execs can't be expunged from the gene pool.

That and there's a huge line of contenders to replace the execs anyway, all with moral compasses permanently set to "screw everyone except me".

Think of it more like a reminder and a chance to begin the education of those who were suckered in by their friends/colleagues (and who aren't/weren't privacy-conscious to start with).

I don't have a Facebook account now because of privacy concerns. But I didn't get one originally (04-05 I guess?) because frankly I'm a bit of a loner and I couldn't think of a group of people I'd rather avoid than those with whom I went to school. Yes, I've missed out on staying connected to people with whom I'd want to continue to associate (Uni friends), but I'm not sacrificing my privacy for it now. I'd rather be detached and a little boring. It's a choice - but I hope an informed one.

True also for Dell, Intel and HP. And the KVM switch vendors (e.g. Avocent). Problem is that while they'll pay for certs for the newer stuff, they're not going to release any new firmware for the older "not supported anymore" stuff. So all those console switches in your datacentre? Worthless, unless you stick with old Java. Same for managed PDUs hosting a little Java applet. Possibly even some rather large web-managed UPS. Same for thousands upon thousands of other supporting appliances of God-knows how many types. Heck, there are companies still rocking servers that are 4, 5 years old; those aren't getting updates to sign the Java applet either, let alone the 10 year old stuff that still hosts the NT4 app that no-one knows how to replace or migrate.

So basically this is going to force companies to replace perfectly good infrastructure or deal with losing remote access to things, as well as screw with hobbyists who have older stuff in their basement/garage/closet/bedroom.

The GP included a direct link to the paper, and you blindly state that it's not out!? I know it's fashionable to comment fast and defend the almighty Apple, but you might try more reading comprehension first.

The quote from the paper is on page 566 (remember this paper forms part of a greater work, and therefore the page numbers are a little strange) just above Figure 9. (I do note that the quote above is missing a space between "our" and "app", but that's no excuse for not finding it).

Oh sure, that'll be the same build that finally figures out that some organisations have web servers with names that don't end in .com.

It's woefully consistent - type a server name that is a "recognised external" URL (so something ending in .com, .co.uk, .fr, etc) and it'll go straight to the site. Type an internal server name (either a plain server name or an internal DNS name) and it will insist on searching Google, because quite obviously the user DIDN'T want localsite or site.network.internal after all. No if you want an internal server, you'll need to get the users to type in the full URL including protocol (because then the same keystrokes that were obviously wrong are suddenly obviously right).

Couple that with the new "requirement" for Chrome if you want to download the Google Talk [wait no it's Hangouts now] on the desktop (they can pry the desktop Talk client from my cold dead fingers) and the continual forcing of Google+ to view an image in a chat, it's clear Google has already turned into Microsoft V2 and is working on digging in deeper. (Hangouts? Seriously? No, it's not a "hangout" when I send an IM to my son to put the damn garbage out!)

Not sure about your local sort of "overly flexible mental gymnasts" but around here, you won't NEED to have that green power because everyone else will give up something and we'll all use less power overall. You know, greenhouse effect and global warming and save the planet. That kind of thing. Because we'll totally reverse the last two hundred year trend of increasing electricity consumption the moment the power isn't available any more. Note that the bozos won't have to give up anything because they're already using less power, so it's only everyone else who should (has to?) change in order to comply with their world view.

As I post this, minus 4.5 hours. The local (AEST) 6am broadcast was heralding 20 years of the Internet (then clarifying to be the Web, which everyone knows is the same thing ). But I was thinking - I'm sure I was seeing http URLs (not that we as students necessarily recognised them as much as we do now) in early 1993, and they weren't for CERN but for an early online, full-colour comic whose name escapes me.

Yeah yeah I know, feed the troll.

Even when you do - the available information is out of date or just plain wrong. For example - the day I made an offer on a place I knew the current resident had a stable ADSL2 connection, and that the RIM at the end of the street had spare ports. The day the contracts were exchanged there were no ports and a waiting list for Internet access.

Fact is the telcos have an active disincentive to invest in Australian broadband (with the NBN coming, or not, or maybe, or halfway, or God only knows what - frankly I suspect even (s)he has given up trying to work it out). My new place might get it within 3 years if the plan doesn't change. Or I might never get it. When I apply for a connection, I get to join a hidden waiting list with no ETA for service. Oh, and I WORK for the telco who would have to do something about the problem and I still can't get information.

Ah, so that's why I can never figure out where all my money goes!

With 1.5T of horses, .8T of trailer and 2T of tow vehicle, you're talking about making that vehicle a rolling roadblock at ~10mph in a 30 zone or 15mph in a 50 zone. That's possibly one of the stupidest things I've heard. Not that I should expect any less from an AC.

Probably because it really does happen to some people - my own gmail address is signed up with a period, and someone else, presumably in the UK, signed up without. I still get Dell UK newsletters for him (and I'm in AU, so if I used my gmail address with Dell, I expect he would receive some Dell AU newsletters). Just because it's publicly stated that dots are dropped does not mean there wasn't a period where either the rule did not exist, or the code to enforce the rule was broken.

I've also sent mail to the version of my GMail account without the dot, and it neither bounced nor arrived in my inbox. I therefore deduce that it was delivered somewhere else.

Who will it be? Maintenance? Boeing?

OK, so how will you solve the GP's problem then? Or to put it another way, here are two future meeting dates. Which one has been updated to reflect the new timezone, and which one has not:

• Jan 27, 2013 03:00:00 UTC
• Jul 15, 2013 16:00:00 UTC

I'm not saying that the GP's solution is perfect, but you've completely ignored the problem in making your comment. Unfortunately we live in a time where politicians and lobby groups think time is pretty flexible (sorry about the pun). So you probably need to store in UTC with an associated original timezone, original timezone offset, and a last updated time. For some apps that could be overkill. For others, it might be necessary.

You need the timezone information so that you record the creator's intent - I set this to 10 am Thursday in my timezone because I want it to be at 10am. You need the last updated date/time so that you know what the timezone configuration was when it was updated (i.e. "it was created/changed in daylight saving time, so even though we're now NOT in DST, I need to do some extra correcting of the display").

TL:DR; time is harder than it seems.

In this case, the tutorial appears the first time any new user logs in (be that domain or local). Need to find out how to kill it, actually, via GPO, or it'll drive me batty.