If I had to guess (I do) Apple is recording information about cellphone towers and WIFI networks the device sees. This information is then at some point anonymized and submitted to Apple to populate/update their location database that all Mac OS X 10.6 and iOS users utilize to know their approximate location in absence of GPS.
If it is easy to access such as is suggested I agree Apple should evaluate a better way...
It is also possible that it isn't recording your location but storing tower/wifi location information for the general area you are currently in (or have visited recently) to allow quick location estimates in absence of GPS when you don't have active network access.
...clearly a temporary reality. Developers will update apps or release new apps utilizing these features (and the many others now available in iOS 4) over the coming months... or be faced with a competitor coming in with a better app. Several of the most popular apps that would benefit from multi-tasking are either already updated or in the approval process.
If your app plays audio (for whatever reason) it WILL run in the background. (audio background mode)
If your VoIP app needs to maintain a network connection with a backend system so it can be told of incoming calls it WILL run in the background but only when network traffic is incoming or at a time you designate so you can keep your network connection alive. (voip background mode)
If your app needs to track your location it WILL run in the background with the level of location accuracy you designate. (location background mode)
(you can combine any combination of the above modes)
If your app needs to finish an active task, one that is not easily paused, it WILL run in the background.
If your application needs to do things at predetermined time you can schedule it and your app WILL run in the background.
The original iPhone was announced in January 2007 but didn't get released until June 2007. The iPhone 3G and iPhone 3GS got announced/released in June/July time frame in 2008 and 2009 respectively.
So the trend is to refresh the iPhone every year mid-year.
I doubt any iPhone hardware update with be announced in January given this trend.
The are transferring a LOT of power over these links using direct current. The only way to do that without a high-level of line loss, huge heat issues and/or insanely high-voltages is by using super conducting material.
What really is needed is LONGER super conducting DC corridors across this country not shorter ones. Use these DC long haul corridors to interconnect various existing AC grids allowing a high level of power distribution/load sharing with lower power transmission losses.
Anyway ignore the 22 sq miles tag line... This is just three DC trunks going between three AC/DC conversion substations that are connected to each of three existing AC grids.
It would be perfect to have a small simple and single connection between a laptop, enhanced iPhone/iPod, or *cough* tablet *cough* and an external display (power would be the only other connection needed, unless the proposed connector contains power pins). The display would contain ports for hardwire networks, USB, firewire, speakers, "web" camera, microphone, eSATA, etc. (much like Apple's and others current display products).
This would be Apple's answer to docking stations that often have rather large fixed connector(s) in slots on the bottom side of a laptop. Having a USB like connector gives you more use case coverage then the docking connector solutions currently and could be used by many more form factors other then just laptops.
I am fairly sure this is Apple's main goal with a secondary goal being the following...
As time passed USB, firewire, etc. - assuming adoption - could be replaced by this technology so you would get displays/hubs for this technology... all working with a single connector/cable type (likely will need mini variants). Storage devices, video cameras, video devices, audio devices, and sync targets like MP3 players, etc. would be perfect candidates to switch to this (assuming power and cost budgets make sense).
By using an optical connector you can get longer distances and higher-data rates. Also many more options to improve throughput, etc. as optical transceiver/coding technologies improve without having to create new connector types.
If the communication technology used inherits and expands on FireWire... a single connector could mux several independent streams of data, including timing sensitive streams with low CPU overhead (later obviously would be needed at the data rates being talked about).
No most of those don't really help since most are well out-of-date with current iPhone OS and hardware....as of iPhone OS 3.0 and the 3GS going off the first article you find in your suggested search:
1. Multimedia Messaging Service (MMS) - SUPPORTED 2. Stereo Bluetooth / A2DP support - SUPPORTED 3. Selecting, copying, and pasting text - SUPPORTED 4. Horizontal keyboard for e-mail and notes - SUPPORTED 5. Improved predictive text (or the ability to turn it off) - UNSURE of improvements 6. Integrated IM application - 3rd party apps 7. Flash support - NOPE 8. A better camera and a camcorder - SUPPORTED 9. Unified e-mail inbox - NO but now have global search 10. Voice dialing and voice memos - SUPPORTED
...and another......cutting out 5 duplicates from above... 9. More storage, 32GB - YUP 10. Forward text messages - SUPPORTED
...and similar answers for many of the other pages that come up using your search.
It is backlog related to the iPhone 3.0 OS release. A lot of existing applications have been submitted with fixes/enhancements related to 3.0. Also Apple has a larger test suite to run against the application submitted, validating 3.0 and 2.x compatibility, etc.
As a guess... I give it another month or so for things to calm down.
Exactly what is the POINT of running a poll then, if they are going to pay no mind whatsoever to the results?
To see if a truly good name popped up that they didn't think about and that they happened to like as well....and obviously they did look at the results of the poll.
I too would have loved to see it named Serenity.
This is NASA giving the middle finger to Serenity fans, no other way to interpret it. Dumb, dumb, stupid, idiot move, NASA. Way to be pricks for no good reason.
Page rendering is rather fast on the iPhone when supplied by WiFi which easily exceeds 3G data rates in all but the rarest of situations. It isn't a CPU issue. Now it could be a 3G chip set issue... however I bet it is primarily latency that is killing fast rendering when using 3G. 3G latency is bad in general and given how "native" the Mobile Safari accesses websites it feels the full effects of this latency (unless a pre-fetching proxy, etc. is assisting the phone pipeline things... which is what BB does IIRC).
Apple even inked a deal back in early iTools and later.Mac days so that folks with such accounts could get a free copy of a 3rd party virus scanner (cannot recall which product it was). You basically could pull a copy down from your iDisk.
Of course that virus scanner dictionary contained a handful of Mac OS X specific malware (mostly trojans), tens of Mac OS (9 or earlier) era items, and the other 99.9% Windows items.
"I keep seeing "SQL injection", but injection into what?"...into anything that will then turn around and execute the tainted SQL query (dynamically generated).
Nope. PowerPC is not coming back on the desktop anytime soon for Apple. The P.A. Semi purchase is about SoC likely built around ARM for small devices (aka iPhone).
No I am pretty sure it is used during the visual effect of switching in and out of an application, for example when having to deal with a phone call while in another application or hitting the home button. It is just a temporary cache used to optimize that effect without having to involve the applications rendering at the time they are doing the affect.
I was under the impression that it did, and that it even used its predictive-text system with the pictogram-style input ?
Yeah as of iPhone OS 2.0 it has a rather robust input system. Apple wasn't targeting the international market before the 2.0 OS.
The AC that submitted this obviously doesn't know that the iPhone isn't limited to only QWERTY input and the referenced article makes no statement on that is why Samsung and Moto are currently more popular. Looks like a little bit of trolling going on...
Open Scripting Architecture CVE-ID: CVE-2008-2830 Available for: Mac OS X v10.4.11, Mac OS X Server v10.4.11, Mac OS X v10.5.4, Mac OS X Server v10.5.4 Impact: A local user may execute commands with elevated privileges Description: A design issue exists in the Open Scripting Architecture libraries when determining whether to load scripting addition plugins into applications running with elevated privileges. Sending scripting addition commands to a privileged application may allow the execution of arbitrary code with those privileges. This update addresses the issue by not loading scripting addition plugins into applications running with system privileges. The recently reported ARDAgent and SecurityAgent issues are addressed by this update. Credit to Charles Srstka for reporting this issue..
..also includes the patches to BIND...
BIND CVE-ID: CVE-2008-1447 Available for: Mac OS X v10.4.11, Mac OS X Server v10.4.11, Mac OS X v10.5.4, Mac OS X Server v10.5.4 Impact: BIND is susceptible to DNS cache poisoning and may return forged information Description: The Berkeley Internet Name Domain (BIND) server is distributed with Mac OS X, and is not enabled by default. When enabled, the BIND server provides translation between host names and IP addresses. A weakness in the DNS protocol may allow remote attackers to perform DNS cache poisoning attacks. As a result, systems that rely on the BIND server for DNS may receive forged information. This update addresses the issue by implementing source port randomization to improve resilience against cache poisoning attacks. For Mac OS X v10.4.11 systems, BIND is updated to version 9.3.5-P1. For Mac OS X v10.5.4 systems, BIND is updated to version 9.4.2-P1. Credit to Dan Kaminsky of IOActive for reporting this issue.
Resizing and Zooming Windows Your application determines the minimum and maximum window size. Base these sizes on the resolution of the display and on the constraints of your interface. For document windows, try to show as much of the content as possible, or a reasonable unit, such as a page.
Your application also sets the values for the initial size and position of a window, called the standard state. Don't assume that the standard state should be as large as possible; some monitors are much larger than the useful size for a window. Choose a standard state that is best suited for working on the type of document your application creates and that shows as much of the document's contents as possible.
The user can't change the standard size and location of a window, but your application can change the standard state when appropriate. For example, a word processor might define the standard size and location as wide enough to display a document whose width is specified in the Page Setup dialog.
The user changes a window's size by dragging the size control (in the lower-right corner). As a user drags, the amount of visible content in the window changes. The upper-left corner of the window remains in the same place. The actual window contents are displayed at all times.
If the user changes a window's size or location by at least 7 pixels, the new size and location is the user state.The user can toggle between the standard state and the user state by clicking the zoom button. When the user clicks the zoom button of a window in the user state, your application should first determine the appropriate size of the standard state. Move the window as little as possible to make it the standard size, and keep the entire window on the screen. The zoom button should not cause the window to fill the entire screen unless that was the last state the user set.
When a user with more than one monitor zooms a window, the standard state should be on the monitor containing the largest portion of the window, not necessarily the monitor with the menu bar. This means that if the user moves a window between monitors, the window's position in the standard state could be on different monitors at different times. The standard state for any window must always be fully contained on a single monitor.
When zooming a window, make sure it doesn't overlap with the Dock. For more information about the Dock, see "The Dock."
The simple fact is no single thing is the cause... Intel Macs, iPod, Apple applications (consumer and professional), Mac OS X, iTunes, expanded developer interest, Apple ads, Vista, iPhone, etc. have all fed into the Mac growth trend that has been taking place for a few years now (actually it has been happening for several years but other factors have hidden/offset the growth).
It is really about a brand mindshare and lowering the barriers.
Blizzard designs their games from the get-go to allow them to release a native Mac and native Windows version of the game on the same day. They have a long history of doing this.
In fact their Mac games sometimes leverage features of Mac OS X and the applications available to do interesting things beyond what you see on the Windows side.
Slashdot Mirror
http://images.apple.com/supplierresponsibility/pdf/Apple_SR_2011_Progress_Report.pdf
http://www.apple.com/supplierresponsibility/
If I had to guess (I do) Apple is recording information about cellphone towers and WIFI networks the device sees. This information is then at some point anonymized and submitted to Apple to populate/update their location database that all Mac OS X 10.6 and iOS users utilize to know their approximate location in absence of GPS.
If it is easy to access such as is suggested I agree Apple should evaluate a better way...
It is also possible that it isn't recording your location but storing tower/wifi location information for the general area you are currently in (or have visited recently) to allow quick location estimates in absence of GPS when you don't have active network access.
...clearly a temporary reality. Developers will update apps or release new apps utilizing these features (and the many others now available in iOS 4) over the coming months... or be faced with a competitor coming in with a better app. Several of the most popular apps that would benefit from multi-tasking are either already updated or in the approval process.
If your app plays audio (for whatever reason) it WILL run in the background. (audio background mode)
If your VoIP app needs to maintain a network connection with a backend system so it can be told of incoming calls it WILL run in the background but only when network traffic is incoming or at a time you designate so you can keep your network connection alive. (voip background mode)
If your app needs to track your location it WILL run in the background with the level of location accuracy you designate. (location background mode)
(you can combine any combination of the above modes)
If your app needs to finish an active task, one that is not easily paused, it WILL run in the background.
If your application needs to do things at predetermined time you can schedule it and your app WILL run in the background.
http://developer.apple.com/iphone/library/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html
The original iPhone was announced in January 2007 but didn't get released until June 2007. The iPhone 3G and iPhone 3GS got announced/released in June/July time frame in 2008 and 2009 respectively.
So the trend is to refresh the iPhone every year mid-year.
I doubt any iPhone hardware update with be announced in January given this trend.
The are transferring a LOT of power over these links using direct current. The only way to do that without a high-level of line loss, huge heat issues and/or insanely high-voltages is by using super conducting material.
What really is needed is LONGER super conducting DC corridors across this country not shorter ones. Use these DC long haul corridors to interconnect various existing AC grids allowing a high level of power distribution/load sharing with lower power transmission losses.
Anyway ignore the 22 sq miles tag line... This is just three DC trunks going between three AC/DC conversion substations that are connected to each of three existing AC grids.
It would be perfect to have a small simple and single connection between a laptop, enhanced iPhone/iPod, or *cough* tablet *cough* and an external display (power would be the only other connection needed, unless the proposed connector contains power pins). The display would contain ports for hardwire networks, USB, firewire, speakers, "web" camera, microphone, eSATA, etc. (much like Apple's and others current display products).
This would be Apple's answer to docking stations that often have rather large fixed connector(s) in slots on the bottom side of a laptop. Having a USB like connector gives you more use case coverage then the docking connector solutions currently and could be used by many more form factors other then just laptops.
I am fairly sure this is Apple's main goal with a secondary goal being the following...
As time passed USB, firewire, etc. - assuming adoption - could be replaced by this technology so you would get displays/hubs for this technology... all working with a single connector/cable type (likely will need mini variants). Storage devices, video cameras, video devices, audio devices, and sync targets like MP3 players, etc. would be perfect candidates to switch to this (assuming power and cost budgets make sense).
By using an optical connector you can get longer distances and higher-data rates. Also many more options to improve throughput, etc. as optical transceiver/coding technologies improve without having to create new connector types.
If the communication technology used inherits and expands on FireWire... a single connector could mux several independent streams of data, including timing sensitive streams with low CPU overhead (later obviously would be needed at the data rates being talked about).
No most of those don't really help since most are well out-of-date with current iPhone OS and hardware. ...as of iPhone OS 3.0 and the 3GS going off the first article you find in your suggested search:
1. Multimedia Messaging Service (MMS) - SUPPORTED
2. Stereo Bluetooth / A2DP support - SUPPORTED
3. Selecting, copying, and pasting text - SUPPORTED
4. Horizontal keyboard for e-mail and notes - SUPPORTED
5. Improved predictive text (or the ability to turn it off) - UNSURE of improvements
6. Integrated IM application - 3rd party apps
7. Flash support - NOPE
8. A better camera and a camcorder - SUPPORTED
9. Unified e-mail inbox - NO but now have global search
10. Voice dialing and voice memos - SUPPORTED
9. More storage, 32GB - YUP
10. Forward text messages - SUPPORTED
It is backlog related to the iPhone 3.0 OS release. A lot of existing applications have been submitted with fixes/enhancements related to 3.0. Also Apple has a larger test suite to run against the application submitted, validating 3.0 and 2.x compatibility, etc.
As a guess... I give it another month or so for things to calm down.
If I squint my eyes and try focus behind the image I think a see a tea pot... or maybe two whales humping? Cool 3D effect!
Exactly what is the POINT of running a poll then, if they are going to pay no mind whatsoever to the results?
To see if a truly good name popped up that they didn't think about and that they happened to like as well. ...and obviously they did look at the results of the poll.
I too would have loved to see it named Serenity.
This is NASA giving the middle finger to Serenity fans, no other way to interpret it. Dumb, dumb, stupid, idiot move, NASA. Way to be pricks for no good reason.
*rolls eyes*
Page rendering is rather fast on the iPhone when supplied by WiFi which easily exceeds 3G data rates in all but the rarest of situations. It isn't a CPU issue. Now it could be a 3G chip set issue... however I bet it is primarily latency that is killing fast rendering when using 3G. 3G latency is bad in general and given how "native" the Mobile Safari accesses websites it feels the full effects of this latency (unless a pre-fetching proxy, etc. is assisting the phone pipeline things... which is what BB does IIRC).
Apple even inked a deal back in early iTools and later .Mac days so that folks with such accounts could get a free copy of a 3rd party virus scanner (cannot recall which product it was). You basically could pull a copy down from your iDisk.
Of course that virus scanner dictionary contained a handful of Mac OS X specific malware (mostly trojans), tens of Mac OS (9 or earlier) era items, and the other 99.9% Windows items.
"I keep seeing "SQL injection", but injection into what?" ...into anything that will then turn around and execute the tainted SQL query (dynamically generated).
Nope. PowerPC is not coming back on the desktop anytime soon for Apple. The P.A. Semi purchase is about SoC likely built around ARM for small devices (aka iPhone).
No I am pretty sure it is used during the visual effect of switching in and out of an application, for example when having to deal with a phone call while in another application or hitting the home button. It is just a temporary cache used to optimize that effect without having to involve the applications rendering at the time they are doing the affect.
I was under the impression that it did, and that it even used its predictive-text system with the pictogram-style input ?
Yeah as of iPhone OS 2.0 it has a rather robust input system. Apple wasn't targeting the international market before the 2.0 OS.
The AC that submitted this obviously doesn't know that the iPhone isn't limited to only QWERTY input and the referenced article makes no statement on that is why Samsung and Moto are currently more popular. Looks like a little bit of trolling going on...
http://www.apple.com/iphone/features/keyboard.html
They're still busy developing a patch for the ARDAgent [slashdot.org] root exploit.
http://lists.apple.com/archives/Security-announce/2008/Jul/msg00003.html
Open Scripting Architecture .
CVE-ID: CVE-2008-2830
Available for: Mac OS X v10.4.11, Mac OS X Server v10.4.11,
Mac OS X v10.5.4, Mac OS X Server v10.5.4
Impact: A local user may execute commands with elevated privileges
Description: A design issue exists in the Open Scripting
Architecture libraries when determining whether to load scripting
addition plugins into applications running with elevated privileges.
Sending scripting addition commands to a privileged application may
allow the execution of arbitrary code with those privileges. This
update addresses the issue by not loading scripting addition plugins
into applications running with system privileges. The recently
reported ARDAgent and SecurityAgent issues are addressed by this
update. Credit to Charles Srstka for reporting this issue.
..also includes the patches to BIND...
BIND
CVE-ID: CVE-2008-1447
Available for: Mac OS X v10.4.11, Mac OS X Server v10.4.11,
Mac OS X v10.5.4, Mac OS X Server v10.5.4
Impact: BIND is susceptible to DNS cache poisoning and may return
forged information
Description: The Berkeley Internet Name Domain (BIND) server is
distributed with Mac OS X, and is not enabled by default. When
enabled, the BIND server provides translation between host names and
IP addresses. A weakness in the DNS protocol may allow remote
attackers to perform DNS cache poisoning attacks. As a result,
systems that rely on the BIND server for DNS may receive forged
information. This update addresses the issue by implementing source
port randomization to improve resilience against cache poisoning
attacks. For Mac OS X v10.4.11 systems, BIND is updated to version
9.3.5-P1. For Mac OS X v10.5.4 systems, BIND is updated to version
9.4.2-P1. Credit to Dan Kaminsky of IOActive for reporting this
issue.
The maximize button doesn't work properly
Resizing and Zooming Windows
Your application determines the minimum and maximum window size. Base these sizes on the resolution of the display and on the constraints of your interface. For document windows, try to show as much of the content as possible, or a reasonable unit, such as a page.
Your application also sets the values for the initial size and position of a window, called the standard state. Don't assume that the standard state should be as large as possible; some monitors are much larger than the useful size for a window. Choose a standard state that is best suited for working on the type of document your application creates and that shows as much of the document's contents as possible.
The user can't change the standard size and location of a window, but your application can change the standard state when appropriate. For example, a word processor might define the standard size and location as wide enough to display a document whose width is specified in the Page Setup dialog.
The user changes a window's size by dragging the size control (in the lower-right corner). As a user drags, the amount of visible content in the window changes. The upper-left corner of the window remains in the same place. The actual window contents are displayed at all times.
If the user changes a window's size or location by at least 7 pixels, the new size and location is the user state.The user can toggle between the standard state and the user state by clicking the zoom button. When the user clicks the zoom button of a window in the user state, your application should first determine the appropriate size of the standard state. Move the window as little as possible to make it the standard size, and keep the entire window on the screen. The zoom button should not cause the window to fill the entire screen unless that was the last state the user set.
When a user with more than one monitor zooms a window, the standard state should be on the monitor containing the largest portion of the window, not necessarily the monitor with the menu bar. This means that if the user moves a window between monitors, the window's position in the standard state could be on different monitors at different times. The standard state for any window must always be fully contained on a single monitor.
When zooming a window, make sure it doesn't overlap with the Dock. For more information about the Dock, see "The Dock."
-- HIG
The simple fact is no single thing is the cause... Intel Macs, iPod, Apple applications (consumer and professional), Mac OS X, iTunes, expanded developer interest, Apple ads, Vista, iPhone, etc. have all fed into the Mac growth trend that has been taking place for a few years now (actually it has been happening for several years but other factors have hidden/offset the growth).
It is really about a brand mindshare and lowering the barriers.
So far we every release of Mac OS X they are actually falling farther and farther behind the current Cocoa framework, etc.
The GNUstep folks aren't really trying provide a Cocoa replacement.
My point was that while Mac OS X is Unix certified and parts of it are BSD based the higher level frameworks are very much not unix related.
So a statement like...
One would think it would almost be easier to "not emulate" the OSX software, as it is mostly unix based.
...is ignoring a heck of a lot of what makes Mac OS X... Mac OS X.
CoreGraphics (Quartz), CoreFoundation, CoreXxxx ..., Cocoa, SystemConfiguration, etc.
Mac OS X is far from mostly unix based.
Blizzard designs their games from the get-go to allow them to release a native Mac and native Windows version of the game on the same day. They have a long history of doing this.
In fact their Mac games sometimes leverage features of Mac OS X and the applications available to do interesting things beyond what you see on the Windows side.