Ibrahim Ulukaya from YouTube:
If you’re still using the Data API v2, today we’ll start showing a video at the top of your users’ video feeds that will notify them of how they might be affected. Apart from that, your apps will work as usual.
In early May, Data API v2 video calls will start returning only the warning video introduced on April 20. Users will not be able to view other videos on apps that use the v2 API video calls. See youtube.com/devicesupport for affected devices.
By late May, v2 API calls except for comments and captions will receive 410 Gone HTTP responses. You can test your application’s reaction to this response by pointing the application at eol.gdata.youtube.com instead of gdata.youtube.com. While you should migrate your app as soon as possible, these features will work in the Data API v2 until the end of July 2015 to avoid any outages.
Basically, if you aren’t running iOS 7, the Apple-produced YouTube app will eventually not work. On the second-generation Apple TV, you’ll have to AirPlay YouTube content from some other device. Although it completely makes sense to depreciate old tools, I suspect most of this is centered around showing ads at the beginning of clips.
Wink sent out an email to some affected customers:
To cut to the chase: We need your Wink Hub back. We’ll update it and get it back to you within a few days. We’ve done all we can to make the process as simple as possible — Just click here.
We’re terribly embarrassed by this whole situation. This outage was completely preventable and caused by a security measure that was put in place to protect you and your family. Unfortunately we failed to make an update to a security measure that was expiring, and therefore locked down your Hub’s access to the server.
It’s unfortunate that this happened, especially since the Wink platform has been slowly, but surely getting more bug-free, but it’s nice that the company owned up to the issue right away and offered $50 towards more products for anyone affected. I still wish there was a local mode that allows your phone to directly control your devices, but for now, the fix worked.
Kevin Fox found something interesting in his archives:
I’m a digital pack-rat, and I’ve been on the Internet a long time. I remember a very different, more playful Apple.com homepage. I remembered a page that was more Fractal Design Painter and less grids and columns. I remember taking a screenshot of that page because I liked the look of it. But where would it be today?
Casey Liss adds his two cents on John Siracusa’s “retirement” from OS X reviews:
I mourn, in a way, for the loss of this incredible resource. While I know that John will be talking to Marco and me about the new OS X at length on our podcast, I will still deeply miss his reviews. The time and care that John put into his reviews is beyond measure. Marco and I know, perhaps better than most, how carefully considered every word in his reviews are. How much joy he gets from sprinkling in pop culture references, and how much pain he goes through taking the same batch of screenshots with each new beta.
Selfishly, and for the community, I’m really sad to know that we’ve reached the end. I am also deeply grateful for all the time and effort John has put in. These reviews are a tremendous resource, and are truly a gift to the community.
I couldn’t have said it better myself.
Nearly 15 years ago, I wrote my first review of Mac OS X for a nascent “PC enthusiast’s” website called Ars Technica. Nearly 15 years later, I wrote my last. Though Apple will presumably announce the next major version of OS X at WWDC this coming June, I won’t be reviewing it for Ars Technica or any other publication, including the website you’re reading now.
I always enjoyed John’s reviews, even if they were a bit more detailed than most people would need. It’ll be a bit weird with the inevitable next version of OS X and not going through the new features with a lengthy review handy. With Apple moving to yearly release cycles a few years ago, writing a large review for each release is just untenable. Thanks, John, and enjoy having a bit more free time this summer!
Not only has Apple acknowledged an issue that’s been going on for awhile, but they included steps to remove most issues:
Ad-injection software is advertising-supported software that can come from third-party download sites. Software that you download from such sites may have been customized to install both the software you want and the ad-injection software. If your Mac has ad-injection software installed, you might see pop-up windows, ads, and graphics while surfing the web, even if “Block pop-up windows” is selected in Safari preferences. Ad-injection software might also change your homepage and preferred search engine.
Until they have a more automatic way to prevent and uninstall adware, I still recommend AdwareMedic by Thomas Reed. Still, this is a good first-step for something that has started happening a lot more over the past few months.
As pointed out by ‘tmiw’ on the MacRumors Forums:
Apparently if you have one of your Apple Pay cards open in Passbook and put your thumb on the Home button, the iPhone will start reading your thumbprint and then show “Hold Near Reader To Pay”. This seems to happen even when the phone isn’t anywhere near an NFC reader. I don’t remember this being in previous versions of iOS (though I could be wrong).
In any case this should save significant time at checkout as the Touch ID verification can be done while the clerk’s still ringing you up.
I haven’t used this yet, but I have tried it by opening Passbook. This could be good if the NFC reader is in an odd place, as it seems to hold this for about a minute before requiring a new fingerprint. Unfortunately, this may also encourage merchants to be lazy about reader placement and people wanting to take your phone.
Although I’m the weirdo with a USB drive with bootable OS X Yosemite and Mavericks installers on it, Thomas Reed found an issue where you might end up with a flashing question mark icon if you try to fix your Mac and it has a Firmware password and FileVault enabled. Fortunately, Apple has a simple solution:
- Start up your Mac and press Command-R after you hear the startup sound to start your Mac from OS X Recovery.
- Enter your firmware password when prompted.
- After the Recovery window appears, choose Startup Disk from the Apple menu.
- Select your normal startup disk (like "Macintosh HD") in the Startup Disk window.
- Because the startup disk is encrypted with FileVault, you need to unlock it to select it for startup. Click the Unlock button in the lower right corner of the Startup Disk window .
- Enter a user account password to unlock the drive. You can use any user account password that normally logs into this Mac at startup.
- The Unlock button then changes to say Restart. Click this Restart button.
- A prompt will appear asking “Are you sure you want to restart…” . When the prompt appears, click the Restart button that appears in this prompt.
- After your Mac restarts, log in when prompted.
You shouldn't need to repeat these steps every time you start your Mac. After performing these steps once, you should be prompted at startup for a login password when your Mac has FileVault enabled or a firmware password set.