WebKit Blog on Safari Content Blocking Extensions→

I’ve been curious to know more about the reasoning behind content blocking extensions coming to iOS 9 and OS X El Capitan. The general assumption is that Apple wants to enable users to activate ad blockers on the iPhone and iPad, but I wanted to hear Apple’s public stance and details on the implementation.

The WebKit blog answers my questions with an in-depth post on content blocking extensions. First off, Apple engineers were unhappy with the current state of content blockers:

The reason we are unhappy about the JavaScript-based content blocking extensions is they have significant performance drawbacks. The current model uses a lot of energy, reducing battery life, and increases page load time by adding latency for each resource. Certain kinds of extensions also reduce the runtime performance of webpages. Sometimes, they can allocate tremendous amounts of memory, which goes against our efforts to reduce WebKit’s memory footprint.

It is an area were we want to do better. We are working on new tools to enable content blocking at a fraction of the cost.

​As for Apple’s motivation, they never mention “ads” in the post, but the focus on disabling trackers and making webpages faster by removing external scripts is fairly clear:

We have been building these features with a focus on providing better control over privacy. We wanted to enable better privacy filters, and that is what has been driving the feature set that exists today.

There is a whole universe of features that can take advantage of the content blocker API, around privacy or better user experience. We would love to hear your feedback about what works well, what needs improvement, and what is missing.

​Unsurprisingly, Apple built these new extensions differently than most content blockers for desktop browsers. Content blocking extensions won’t see the URLs of pages or resources being blocked:

A major benefit of the declarative content blocking extension model is that the extension does not see the URLs of pages and resources the user browsed to or had a page request.

​And:

WebKit itself does not keep track of what rules have been executed on which URLs; we do not track you by design.

User privacy is at the center of content blocking for both webpages and extensions. It’ll be interesting to see how many apps that just focus on blocking ads in Safari will be approved on the App Store (and how much they’ll leverage freemium models if so).

​

Permalink

Apple News and the Open Web→

Daniel Jalkut perfectly encapsulates my thoughts on why I want MacStories to show up in Apple News and take advantage of connecting with more people:

Whether it’s music, apps, podcasts, or, coming very soon, syndicated blog content, you’d have to be a fool not to try to get your work into their customer-facing channels. In the case of podcasts, and as it seems with “News,” doing so means providing a feed that points to content you own and which you store on your server.

As long as I don’t have to relinquish control of my RSS feed and the words I write, I’m all for experimenting with aggregators that can bring our articles to different audiences. I’m intrigued by Apple News.

Permalink

Apple News to Have Human Editors, Curation→

Jordan Kahn, writing for 9to5Mac on a job listing that indicated Apple News is going to have human editors in addition to algorithms:

Apple’s job listing notes that News editors will be responsible for gathering “the best in breaking national, global, and local news.” They will also be working firsthand with publications to “drive relationships with some of the world’s leading newsrooms, ensuring that important breaking news stories are surfaced quickly, and enterprise journalism is rewarded with high visibility.” And Apple won’t just be curating stories from the big players. It also mentions a focus on surfacing original content from “the largest to the smallest” publishers. News editors will also track social media for breaking stories, according to the job listing, and “recognize and communicate key content trends to senior management.”

And here’s Dan Moren for Six Colors:

But what fascinates me here is the bigger message: that the most profitable and arguably most powerful technology company in the world firmly believes that technology alone simply isn’t good enough for these sorts of determinations. I don’t think it’s necessarily a view you’d hear espoused at the highest levels of Google, for example.

First thought I had: I’m curious to see how they will curate the Technology section in Apple News.

Permalink

Inside iOS 9 Search: Apple’s Plan for More Connected Apps

At WWDC 2015, Apple announced app search, a new feature of iOS 9 that will help users find content inside apps. Beyond the user-facing aspects of a new search page on iOS and proactive suggestions from Siri, however, lies a commitment to fundamentally rethink iOS’ relationship with apps and the web, with deep implications for the future.

With iOS 9, Apple wants to reimagine how information from apps is exposed to users. For a long time, iOS apps have largely been treated as data silos – utilities that kept gaining design improvements and powerful functionalities as iOS grew, but ultimately unable to bring their data outside the confines of their sandbox. Following in the footsteps of iOS 8’s adoption of extensions, Apple’s plan to further open up iOS is deceptively simple: just let users search for what they need.

Behind the scenes, the reality of iOS 9 search is going to be a little more complex than that.

Read more

Igloo: An Intranet You’ll Actually Like [Sponsor]

Igloo is a social intranet. It’s built with easy-to-use apps, like shared calendars, task management, file sharing and more. It’s everything you need to work better together, in one very configurable cloud platform.

With Igloo’s responsive design, your intranet already handles a range of devices, it will even work on your iPhone 6 or 6 Plus right from the start. It’s customizable, responsive, and lets teams work better together. Sharing files, coordinating calendars, providing status updates, and managing projects — almost everything you can do on your desktop, you can do on your phone.

We all struggle with productivity. We are constantly pressured to accomplish more, and to do it quicker. There is no one definitive way to accomplish that, and we have all devised our own little method to make things work. At Igloo, we think your way is the best way, we just want to support you, and make your way better.

Try Igloo for free with up to ten of your favorite coworkers. Igloo, an intranet you’ll actually like.

Our thanks to Igloo for sponsoring MacStories this week.

Editorial 1.2 Brings Powerful New Text Editing Features, More iOS Automation

If I had to pick one iOS app I couldn’t live without, that would be Editorial.

Developed by Berlin-based Ole Zorn, Editorial was the app that reinvented text automation in 2013 and that pushed me to start working exclusively from my iPad. Editorial is a powerful Markdown text editor that combines visual Automator-like actions with a web browser, text snippets, Python scripts, and URL schemes to supercharge text editing on iOS with the power of automation. I spend most of my days writing and researching in Editorial, and my workflow depends on this app.

Editorial also has a slow release cycle. Zorn likes to take his time with updates that contain hundreds of changes: Editorial 1.1, released in May 2014, brought an iPhone version and custom interfaces, making Editorial feel like an entirely new app. The same is happening today with Editorial 1.2, which adds support for the latest iPhones, iOS 8 integration, custom templates, browser tabs, folding, and much more.

Editorial 1.2 with iOS 8 support is launching right after Apple’s announcement of iOS 9, but the wait has been worth it. The new version builds upon the excellent foundation of Editorial 1.1, and the enhancements it brings vastly improve the app for users who rely on its automation features and Python interpreter.

Rather than covering every single change, I’ll focus on the 10 new features that have most impacted the way I get work done with Editorial on a daily basis.

Read more

iOS 9 Picture in Picture→

Benjamin Mayo has a great summary of the benefits of Picture in Picture for iOS 9 on the iPad as compared to the Mac:

The thing about the iPad picture-in-picture implementation is that its actually better than how one would handle such a task on a Mac. On a Mac, trying to play a video in the corner whilst getting on with your work is difficult. Let’s take a video on YouTube playing in Safari. To play this in a corner of the screen on a Mac, you have to pull the window out into its own tab. Then, you have to manually drag the corners of the window to resize it and do your best to clip out all the unnecessary surrounding UI by hand. No doubt the window has a toolbar so you’ll probably have to do some awkward keyboard shortcut or hidden menu command to hide that as well.

Then you have to actually manage the window as you go on with your work. What do I mean by this? Well, with every other task you open you also have to make sure it doesn’t occlude the video playback window by dragging it out the way. The video can’t stay foremost so it’s actually really easy to lose the video amongst your other windows.

If you ever want to move the video from one corner to another, not only do you have to position the video on the screen, you also have to move all your other windows back over to the other side.

This mirrors my initial thoughts exactly. When I talk about the inherent complexities of desktop OSes, this is the type of issues I refer to. With an implementation built on years of distilling the experience to the simplest, iPad multitasking will make these differences even more obvious.

Permalink

Twitter Removing the 140 Character Limit from Direct Messages→

With a post on the Twitter Developers forum yesterday, Product Manager for Direct Messages Sachin Agarwal has announced that Twitter will be removing the limit of 140 characters from DMs this summer:

We’ve done a lot to improve Direct Messages over the past year and have much more exciting work on the horizon. One change coming in July that we want to make you aware of now (and first!) is the removal of the 140 character limit in Direct Messages. In order to make this change as seamless as possible for you we’ve included some recommendations below to ensure all your applications and services can handle these longer format messages before we flip the switch.

When I first read this, I felt skeptical. Much of Twitter’s appeal to me lies in the streamlined approach to short messages that fly by in the timeline. But, some of my most important conversations over the years have started from Twitter DMs. From this standpoint, it’s surprising that Twitter hasn’t put more thought in the DM product as a messaging platform, alienating users who were looking for a direct, nimble communication system – and pushing them to other services.

The strength of Twitter DMs is, for me, the existing graph between users (people I’m interested in), speed, and the lack of baggage from email. Lately, I’ve come to like the ability to easily share links and pictures in DMs as well. I don’t know if raising the character limit to 10k characters will by itself improve DMs, but Twitter is wasting an opportunity with DMs, so maybe their new CEO could use this as a starting point.

Permalink