Has anyone considered this is what iCloud's been using since before Apple bought them? From what I read here, this smells to me like "leaked" MS propaganda, but so what? I got an iCloud account before then; it's designed to emulate the Windows UI, but there's more to this service than the GUI, or the platform. Apple also bought them for the rights to the name/domain "iCloud" itself. This is still a new acquisition in my book, and with MS so desperate for *any* sence of capable public deployment I think the article is racing to get us to draw *lots* of conclusions that are too early to move-forward with.

As has been said, it identifies the phone, and not the user (though a majority of the time it'll be the phone's owner). Many apps use the UUID as a unique ID (ahem) to store state, e.g. viewed pages, favorites, etc. Yes, this is also done with a log in, or it could be done transparently via the UUID; not sure there's a best/worse here. I know -- it's the transparency that's the controversy, but I'm a bit pressed to think of anything that's revealed that couldn't also be revealed with (or without) "vendor collusion" (e.g. an App-to-UUID database to see which apps are on the same phone -- oh, wait, Apple knows that).

"The world's largest Internet market" -- perhaps geographically, but more-so for China because China isolates itself, and because most people still think of the world geo-politically. The internet's financial picture is mostly based on social demographics, such as age-markets, and if China were treated that way then it's citizens may make up the largest portion of each social demographic, but there'd be more that could be done independent of geographic politics. Sending "explain yourself" letters works between governments, but not as directly for businesses (e.g. Google sending the same letter essentially makes no difference), so the decision from a business perspective is keep doing business in that environment, or stop.

Well, as it's theorized the Milkyway has already swallowed others (reference missing), there should either be multiple black holes in our galaxy, or this provides a good estimation of how long it's been since that happened -- according to Einstein, of course.

http://www.att.com/ --> Wireless --> Shop/Cell Phones --> PDAs and Smartphones --> iPhone 3G. Opening the (last) iPhone link in another tab prompts me for my zip, followed by "not available in your area", *then* refreshing the list of phones in the previous tab *removes* iPhone from the listing.

You can go to the Apple store and buy one, but NOT (apparently) on AT&T's website, at least not after typing in a NYC zip code.

I'd hazard a guess that the heating method would be forced hot air, so some technology could be thrown and filtering the air, though I'm not sure where they're going to put all this heating and filtering equipment, since it basically means being able to filter however much air the dome holds every day. If they put in some amazing electric public transport, then they could generate the extra electricity themselves, venting it directly out of the dome, and their downwind neighbors would have to deal with it.

Firstly, the Mac has an incredibly rich simple character set. This is NOT coincidental, as Apple copied their editing capabilities from the publishing industry decades ago. E.g. in TextEdit type alt-b and you'll see a '' integral symbol (looks correct as I type it, hopefully the post wont change it). If you can learn these keyboard shortcuts (learning-curve arguments aside), you *may* be able to type these directly into your mac in class, BUT... If you take notes by hand, then transcribe them into your mac using these short cuts, or simply via the Mac's Font (e.g. TextEdit --> commant-T) and characters (e.g. via the gear drop-down in the Font) pane, you're doing yourself a much bigger favor.

So, this means they've clung to their dynamic library model to the point where they've invented a system to identify unique versions of these DLLs so each application can load multiple copies of the same DLL -- and *somehow* this is better than just using static linking? How, in practice (that is "in the real world) doesn't this completely marginalize the benefit of dynamic linking -- *especially* since they insist on using huge "dynamic" libraries? Fanatics, for sure.

One other system used more prevalently is the simple locking screen saver. The idea is only the user, and sysadmin have the password to unlock the screen, and access through the system is prohibited until the screen saver password is entered. I'm not a fan of this, as generally screen-saver passwords are more-often assigned by the users themselves, and so are easier to guess than the back-end passwords which on occasion are set by the site, or by the sysadmin in the case of accessing corporate systems via corporate-policy. Now a minor, but important distinction. This isn't "un-authentication" this is de-authorizing the computer from which you're logged in accessing the place you're logged in to. You want to "authenticate a de-authorization" that is verify that you are the person removing access privileges. If the system doesn't require authentication to de-authorize access, then a denial of service attack is made (somewhat) trivial, and if more thought process went into understanding the difference I think more places would realize how serious the solution needs to be.

An all-too-quick 40 minutes? At a user/usage level? There's a LOT to choose from, but as a great start, try RFC2504. http://www.ietf.org/rfc/rfc2504.txt?number=2504 Pick and choose as appropriate to your needs. We tried to make it very useful as a reference for the generic user. You can even hand out copies if you like. For a bit more detail, and as a good read in case you get asked some lower-level questions, try RFC 2196, more specifically targeted for IT folks, and "Middle Managers" who have to at least be exposed to the concepts. http://www.ietf.org/rfc/rfc2196.txt?number=2196 Cheers, Steve PS(don't let the fact that these are TEN years old fool you, most of these concerns are still quite current, most companies (read: those of popular OSes) don't exactly *want* people to understand the why's because they start to question the why-not (yet)s. If you found any of this useful, or not, just reply here, Most if not all those email addresses are defunct at this point -- we've moved onto and into other things).

Even before we get to the performance issue, there are at least two others that could run blocking. 1) I wonder if this is the sort of thing Apple would approve. Recent rants would seem to indicate if it allows any sort of a shell, no way. Otherwise, who knows? 2) Apple enforces it's look-and-feel rules religiously. Last I saw there was NOTHING .Net that looked at all Aqua. The stuff at unity3d.com looks cool, and would seem to *imply* Apple's OK with however their stuff looks, but I couldn't find a screen shot that showed me e.g. a typical config panel so I could compare it to iPhone's native bits.