This is a good list of some new iOS 7 settings that you probably did not know about, or likely never would have accidentally run across.
I will be a little bummed if updated Apple TV hardware is not announced, slightly less so if there is no “iWatch” released.
Although it will be interesting to see what Apple has to say, it will be far more fascinating watching the tech analysts dissect Apple, likely stipulating that they are no longer innovating and on a decline, even though Apple continues to make the best products the tech industry has to offer.
Here is a very interesting theory on the potential for a Docomo-based iPhone to be the catalyst for SIM unlocking of all mobile phones in Japan
If NTT Docomo does indeed carry the iPhone, and if they continue with their tradition of unlocking all their devices, then this would create a large feature disparity between Japanese iPhone carriers. Any discrepancy in value is amplified by the fact that, once you wade through all the fuzzy math to arrive at the out-of-pocket cost of hardware and service, the total cost is almost always the same for similar devices across competing networks.
Recall that previous iPhone feature disparity, with respect to tethering and data caps, left Softbank on the brink of a customer revolt. This was narrowly averted by a yarimasho (aka executive order) from CEO Son. Softbank had no choice but to offer free tethering and ease data caps to match the value offered by KDDI. (Microsoft should have seen a similar reaction coming with the Xbox One versus the PS4.)
Unlocking phones is a slippery slope for carriers. I believe that NTT Docomo will, after making such a stink about unlocking and vowing to unlock all their phones, have no choice but to unlock any iPhone they may sell, just as they currently do for all Android device. If this creates a strong enough feature disparity, Softbank will be forced to follow, and they would lose any justification for keeping their Android devices locked.
This post is part of the thread: Japan – an ongoing story on this site. View the thread timeline for more context on this post.
SFGate quoting President Obama regarding a potential course of action for capturing Edward Snowden, the ex-Booze Allen Hamilton contractor for the NSA turned whistleblower:
“No, I’m not going to be scrambling jets to get a 29-year-old hacker,” he told a news conference in Dakar, a note of disdain in his voice. Snowden turned 30 last week.
Snowden is no hacker, especially in the vernacular Obama is attempting to leverage for that emotional reaction. It is doubtful Snowden had to “hack” any systems to gain access to the documents he turned over to The Guardian.
Snowden worked as a System Administrator, and therefore by nature of his position most likely had escalated privileges for the performance of his duties. As a result, I suspect he had access to entire file shares of classified documents, and could probably access them at will. System Administrators require elevated privileges to access server-based objects, although accessing objects not directly authorized to access – in this case, possibly classified documents in private, restricted areas of the file server – is generally considered an ethics violation, ostensible whistle-blowing notwithstanding.
This is not out of the ordinary; a combination of role-based access control using discretionary access control, and mandatory access control is generally employed throughout DoD networks, although the latter is primarily only used on multi-level systems and not for user or administrative accounts. In any case, the fact that Snowden had access to these documents is not unprecedented – it is standard operating procedure.
So if he is not a hacker then what is he?
Snowden is the classic insider threat. From Wikipedia:
Insiders may have accounts giving them legitimate access to computer systems, with this access originally having been given to them to serve in the performance of their duties; these permissions could be abused to harm the organization. Insiders are often familiar with the organization’s data and intellectual property as well as the methods that are in place to protect them. This makes it easier for the insider to circumvent any security controls of which they are aware. Physical proximity to data means that the insider does not need to hack into the organizational network through the outer perimeter by traversing firewalls; rather they are in the building already, often with direct access to the organization’s internal network. Insider threats are harder to defend against than attacks from outsiders, since the insider already has legitimate access to the organization’s information and assets.
An insider may attempt to steal property or information for personal gain, or to benefit another organization or country.
Is does no good to incorrectly label Snowden as a hacker; it is obvious what label should be used: insider threat. Snowden had elevated, privileged network access, and abused that access, quite possibly for what he considers to be for the good of the United States.
tldr; Snowden is not a hacker; he is a classic case of insider threat because of his previous position within the NSA.
This post is part of the thread: Security – an ongoing story on this site. View the thread timeline for more context on this post.
As soon as Mailbox was unleashed, like so many other people, I quickly downloaded the app and got in the 150,000+ access queue. I had already signed-up via the web, but for whatever reason that reservation did not follow me, and I had to start over. After a couple weeks of waiting, I was finally offered entry into the system I eagerly awaited.
Hopefully some of my trials and tribulations will help other folks better understand how Mailbox functions sincer there is not a lot of information available right now. The good folks behind the Mailbox twitter account are great at responding to people, but sometimes people need more in-depth answers than what happens inside of 140 characters.
Before I continue I must confess: I am an email client junkie. I do not know why but I really enjoy testing and playing around with new email clients. I am forever in search of email client utopia. Although I have come close a couple times, in the end I always end up returning to my old [bad] habits.
The built-in Mail.app, while decent, does not have the same polish I would like, nor does it natively support Gmail’s labeling system. It was for those reasons that I snatched up Sparrow as soon as it became available on iOS. Unfortunately, like with so many other services, Google bought Sparrow and promptly dismantled what was probably the best third-party iOS email client.
Although the Gmail iOS app is decent, it is not a fully native app, opting for a Web View-based app instead. This makes it a bit slow and clunky, and it feels uncomfortable. Plus, even though it supports multiple accounts, it fails to offer a unified inbox view, which is almost a necessity these days.
So Mailbox was released and I was jazzed about yet-another-iOS-email-app to try, along with the idea of turning email into a task management system. I started playing around with Mailbox and was pleased with the clean user interface. The unified inbox, snoozing, and archiving system the Mailbox team has built is very exciting.
But I ran into an adoption problem: existing Gmail labels are inaccessible from within Mailbox.
For me, this is a deal killer as I have a number of filters designed to apply labels and skip the inbox. Although that appears to violate the spirit of Mailbox, it is the way I use email. I need access to those labels; luckily there is an easy solution.
Upon initial launch, existing Gmail labels are not accessible but there is a simple way to make those labels viewable. Simply go into Gmail->Settings->Labels and move all labels so they are nested underneath the [Mailbox] label. This turns them into Lists in Mailbox parlance. The app will automagically see the new labels and create new Lists.
If your existing Gmail label setup is something like this:
Merely move all those labels so they nest underneath the [Mailbox] label as so:
Now all those labels are accessible as Lists from within Mailbox. It may be necessary to force-close Mailbox after moving the labels, because this appears to force the app to rescan for new Lists. Jump on over to Mailbox->Settings->Lists to reorder Lists into a desirable order. Personally, I go for alphabetizing my Lists since it makes it easy to locate the List I need.
Here are some additional notes about List use within Mailbox:
- If two separate Gmail accounts both share the same label, Mailbox will treat them as a single List. Mail from both accounts will be intertwined within the List. It may be necessary to open an email to determine which account it was sent to, so this could cause a bit of confusion if not properly managed.
- Similarly, because Mailbox only presents a single collection of Lists, it is not possible to determine which account a List – ergo, a Gmail label – belongs to. This could be confusing if you are not aware of exactly how Mailbox employs List use. It is easy to “inadvertently” put an email on a List previously defined from another account, leading to unexpected filing when using Gmail on the web.
- If you have Gmail filters apply labels, and use Mailbox to file the email on a List, the previously applied labels will be removed.
- Similarly, if you have Gmail filters apply labels, and use Mailbox to archive email, the previously applied labels will be removed. In Mailbox, when an email is archived, all labels are removed, and it can only be found in the All Mail Gmail label.
- If you have Gmail filters apply labels and “Skip the Inbox”, the applied Gmail labels will remain intact, and the email will be found on the appropriate Mailbox List [assuming the labels are nested as previously discussed].
- Adding a new Gmail label will automagically add a new Mailbox List. As previously mentioned, it may be necessary to force-close Mailbox before the changes can be seen.
- Similarly, removing a label in Gmail does not automatically remove the label from Mailbox. The app appears to cache certain data, and there is no method for forcing Mailbox to rescan for label changes. At some point, the deleted label will be removed from the Lists side-panel, but still show up in the Lists configuration. At this point it is safe to delete the Mailbox List without fear of any unintended consequences.
- Mailbox’s List message totals do not appears to match those in Gmail. Even if taking into account multiple email accounts sharing the same List, the totals are orders of magnitude off. Not all email on those Lists appear to be accessible.
I did perform a number of fairly exhaustive tests but under limited circumstances and with only a finite set of Gmail accounts. I hope this information I found helps some folks better understand Mailbox, and how it manages Lists and Gmail labels. As I find more quirks, I will update this post to reflect the new information.
Mailbox is a truly revolutionary yet simple app. I am sold on the email-as-task premise and plan to stick with Mailbox for the foreseeable future, especially since DropBox acquired the app. I anxiously await an iPad and OS X app sometime in the near future!
This post is part of the thread: Email – an ongoing story on this site. View the thread timeline for more context on this post.
Jim Tanous of The Mac Observer on Japan’s NTT DoCoMo showing interest in offering the iPhone:
President Katoru Katō reportedly said that his company was eager to add the iPhone to its lineup, but that concerns over alleged sales quotas imposed by Apple had been a previous point of contention. Mr. Katō now says that DoCoMo could meet those quotas as long as the iPhone accounted for 20 to 30 percent of its overall smartphone sales.
NTT DoCoMo is Japan’s largest mobile telecom network by far. Overall, it has the best coverage throughout the entire country, often times offering service in areas where KDDI and SoftBank have very limited, or no, service. It would be a big win for Japanese consumers if DoCoMo were finally to get off its high horse and start offering the worlds most wanted smartphone on its network.
This post is part of the thread: Japan – an ongoing story on this site. View the thread timeline for more context on this post.
Nick Bilton of the New York Times on the “real” hazards of electronic devices used on airplanes:
When I asked why I can read a printed book but not a digital one, the agency changed its reasoning. I was told by another F.A.A. representative that it was because an iPad or Kindle could put out enough electromagnetic emissions to disrupt the flight. Yet a few weeks later, the F.A.A. proudly announced that pilots could now use iPads in the cockpit instead of paper flight manuals.
The F.A.A. then told me that “two iPads are very different than 200.” But experts at EMT Labs, an independent testing facility in Mountain View, Calif., say there is no difference in radio output between two iPads and 200. “Electromagnetic energy doesn’t add up like that,” said Kevin Bothmann, the EMT Labs testing manager.
When you have a federal agency using junk science to “backup” its junk claims, you end up with junk policy. The FAA needs to get with modern times and shift to a more pragmatic policy. Either that or be transparent, and articulate exactly why the ostensibly pointless ban remains in-effect.
Either way, get used to the current policy because it is doubtful the FAA is interested in rapid change.
MG Siegler on TechCrunch, writing about the 13″ MacBook Pro with Retina Display:
I’m more than happy to take on the extra half-pound of weight in exchange for this screen (as well as other, slightly better specs). Some will disagree, but I think plenty of people will agree. No, it’s not technically a retina MacBook Air, but again, it’s close.
In terms of thickness, this new Pro and the 13-inch Air are actually very close (0.75 inches versus 0.68 inches). Of course, the air tapers off into almost nothing (0.11 inches) at the end point while the Pro is a uniform thickness. Oddly, the 13-inch Pro is actually slightly less wide than the 13-inch Air.
Sounds like a tough decision if you’re looking for portability versus bleeding-edge features. I’m not entirely sure the price difference is worth it yet.
If you have ever used Instagram and wondered why photo uploads appear to be so incredibly fast then look no further than this Quora thread. The answer is a lot more obvious than most people would think. Consider what Instagram has done a bit of sleight-of-hand.